First-time tutorial

[ferndot]

Implement first-time tutorial to explain the app to new users.

Actions that should be covered (feel free to suggest more):

• Create a document.
• Edit a document in Raw and Design mode.
• Add a format to text (e.g. bold).
• Add a special element (e.g. link).
• Delete a document.
• Change settings.
• Connect a cloud storage account.

Implementation notes:

• We can use a "first.run" setting (set using https://github.com/codexa/firetext/blob/develop/scripts/settings.js#L168-L171) to tell if this is the first time that the user has launched the app.
• The tutorial should be dismissible
• The tutorial should be able to be launched from the Settings view.

[HR]

ok but later when we have the new enhanced workspace. We'll guide the user through an example.html template showing the features and how to use them

[HR]

http://usablica.github.io/intro.js/

[ferndot]

I tried that, but it does not work on mobile. Maybe it has something to do with the script causing CSP violations?

[asdf23]

Thanks for this link,, this change my own work project 2000% not sure useful here though. It takes a lot of real-estate

[jancborchardt]

As a quick fix for this, it might make sense to show the Menu on first run, when no documents exist yet.

[ferndot]

Other potential libraries:

• http://zurb.com/playground/jquery-joyride-feature-tour-plugin
• http://github.hubspot.com/shepherd/docs/welcome/

[twiss]

I feel like the most important thing on 1st start is to get the user to do something useful with the app. So on the desktop that could be

• Connect a cloud storage account
• Upload a document
• Create a new document

So we should make all of those options easy and obvious. However, if we're trying to convince the user to do something, we should make it simpler still; for example just one screen with: "[Connect a cloud storage account!!one]
[(or upload a document)]"

(we could even always show that below the file listing.)

• Add a format to text (e.g. bold).
• Add a special element (e.g. link).

You could show these the first time the user opens a document. I don't know if it's necessary though.

One more point: we should make it clear that files are autosaved. A tutorial isn't the only way to do that, though.