Volto onboarding

[tisto]

Our current newbie onboarding sucks. @ksuess @wkbkhard @steffenri and I discussed this at the Plone Tagung in Dresden.

We should set up instructions (either on the README and/or on a separate website:voltocms.com) with basic instructions on:

• how to set up Volto as a user (node, python, create-volto-app)
• how to set up Volto for production use (point to our docs and fix the docs)
• how to get help if needed (point to slack/gitter/mailinglist/community)
• where to find a demo instance
• how to report bugs (link to github, we should set up an issue template to make this easier)
• how to get involved in the community (sprints/conferences/etc.)

We should put some effort into making sure all of the above is high quality and tested regularly for each new Volto release. If we frustrate people on that level, we will not be able to reach the critical mass as a community.

@ksuess would you be willing to champion this? I will try to help as much as possible. Maybe others want to help as well. This could be the most important issue we need to solve in Volto right now.

[tisto]

@sneridagh could you ask @albertcasado if he has the Sketch files for the Pastanaga UI website? We could use that one as a base for voltocms.com.

[wkbkhard]

I just instructed my coworkers to tell me every problem they run into with our new projects, so I can collect those points and may be, we can use them to clearfy some parts of the documentation

[ksuess]

OK, yes, how could I resist.

You already prepared multiple essential tasks in #1278 (comment) I will pick up the thread.

[ksuess]

@wkbkhard That's great, collecting feedback. I think opening issues for documentation feedback is fine with a label "documentation"

@timo @sneridagh I suggest creating a label "documentation" near label "UX" Would you think about a numbering/order, please?

[sneridagh]

@ksuess I'm +1 for creating the label too. I suck at naming, any suggestion?
After we decide on it, we should ask @jensens to follow the best practices on label namings.

[jensens]

I suggest creating a label "documentation" near label "UX"

the 33 needs: docs is meant for this.

[update] Here is the spreadsheet with the labels explained: https://docs.google.com/spreadsheets/d/1IQ73bSQ10b0pwoUFn0u8SE4epDdvwjhTiYTDyPAhx7A

[sneridagh]

@tisto BTW, https://app.zeplin.io/project/58458c669705b3b95c6ed36f/screen/59ecbc802de9cb85adefc107

is all we have, Albert has searched for it with no success. We have the pastanaga.io Gatsby repo we can use as a template for the new site.

[tisto]

@sneridagh too bad. I was hoping we could mess around a bit in Sketch to outline how a voltocms.com site could look like...

[tisto]

@ksuess awesome!!!

[ksuess]

Just for the records

https://community.plone.org/t/about-the-volto-category/10515 category Volto is updated to a short description.

The training Mastering Plone 6 is on a good way. It's beside the upcoming voltocms.com Website, the precious Volto documentation https://docs.voltocms.com/design-principles/ and inspiring talks https://github.com/plone/volto/#talks one more step for developers to enjoy and work with Volto. Janina, Philipp, me and more are continuing to make the training a pleasant discovery of Plone with Volto and same a valuable source of information while working with.
We are happy to get feedback to Mastering Plone 6 https://training.starzel.de/mastering-plone/volto_components_sponsors.html and are coming back to it next week at Beethoven Sprint https://plone.org/events/sprints/beethoven-sprint-2020-kitconcept.

The upcoming Website voltocms.com is also one of the topics next week while sprinting. Feel free to have a look at the draft text and don't be shy to comment: https://docs.google.com/document/d/1GLbbcDo_yfWTer6eKoI61aJBLvBxVAyne2_khCkhE3o/edit

[mauritsvanrees]

I think this can be closed. We have https://6.dev-docs.plone.org/volto/. This can be improved, but those are details that are better handled in separate issues.

I close this blocker (I am going through issues marked as blocker). Feel free to reopen, or create separate issues for remaining points.