First off: I’m really happy to see Xenko upgrade documentation’s status by making pull-requests possible. Combined with the complete API references, the sample GitHub repository, the Q&A Questions site and this forum, the community has all the tools it needs to grow.
That said, I was a little lost in the signal to noise ratio of the Getting Started section in the manual. It felt like most pages couldn’t decide if they were about getting the user started as fast as possible or be an exhaustive help reference.
I personally expected this section this section to show me the absolute basics and to motivate me to invest time and effort in learning a new (my first?) engine.
- Getting Started main page should make the visitor feel welcome, tell them what this section is about and help him/her going
- Point users that are looking for topics not covered here to the correct pages or the search
- Only keep the bare necessities (move the extra content to a new section)
- End with call to action and the first step to take if you want to learn more
I felt these are the necessary pages for a Getting Started section:
- Getting Started (get started fast)
- Install Xenko
- Create new project
- Setup basic scene
What are your thoughts about this?
I started writing the Getting Started page itself, but in order to have a helpful pull request I figured it would make sense to first consult the authors and anybody else with ideas.