Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: welcome/upgrade page #140

Draft
wants to merge 6 commits into
base: develop
Choose a base branch
from

Conversation

AdrieanKhisbe
Copy link
Member

@AdrieanKhisbe AdrieanKhisbe commented Mar 20, 2019

With the new extension release, we need to find a way to reach our userbase to make them switch to the new publisher extension.

One way to do it, would be to publish a version that open a page explaining the user that he need to replace the extension to have latest features.
I start to dig how to implement that, (as bookmark, or gitlens do), and end up on vscode extensions samples.
So far, the current version will open the Upgrade page at start.
This is still beta and prototypal, focused on the mecanism rather than the message

Once working this would need to be backport on original extension, and a release with the original publisher should be made

We'll could later use that mecanism to publicize new features.

Feedback are more than welcome!!, I wanna know what you think about this :)

🦄

Capture d'écran 2019-03-20 22 23 25

@AdrieanKhisbe AdrieanKhisbe added the WIP Work In Progress label Mar 20, 2019
@AdrieanKhisbe AdrieanKhisbe self-assigned this Mar 20, 2019
@sipi
Copy link
Member

sipi commented Apr 2, 2019

Sorry, @AdrieanKhisbe I did not already had the time to have a look to this PR :(
I will try to do it at the beginning of the next week.

Copy link
Member

@sipi sipi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @AdrieanKhisbe,
thanks for this PR, I think it's the good way to reach users of the "tootone version".
Everything seems fine to me, I only made two comments to better understand some of the parts.

So, now we have to edit the message! But, I suggest we keep it simple as :

Hello Org-mode users,

please note that tootone/org-mode has become vscode-org-mode/org-mode. 
This version will probably no longer receive any update, to continue receiving 
org-mode updates please uninstall tootone/org-mode and install 
vscode-org-mode/org-mode instead.

Thank you.

We can possibly take the opportunity to add : 

We take this opportunity to remind you that org-mode is built and maintained 
by volunteers and that any help is welcome. If you like this extension and 
 have some time to devote to it, please visit the Github
repository: https://github.com/vscode-org-mode/vscode-org-mode

package.json Outdated Show resolved Hide resolved
src/ui/panels.ts Show resolved Hide resolved
@AdrieanKhisbe
Copy link
Member Author

Everything seems fine to me, I only made two comments to better understand some of the parts.

@sipi since it's good for you, I'll find some time to pursue this works, and incorporate your wordings :)

@sipi
Copy link
Member

sipi commented Apr 9, 2019

@AdrieanKhisbe feel free to reword my wording ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
WIP Work In Progress
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants