-
Notifications
You must be signed in to change notification settings - Fork 316
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
Documentation Reorganization #1194
Comments
Definitely. Texture, Sprites, SpriteList etc etc. They are closely linked so there can be other categories like "Drawing sprites best practices" etc. It will probably make things easier to explain. It can quickly become too much stuff at the same time unless separated properly. I also want an opengl sub-section explaining:
|
Ok, I updated it with this.
I'm not sure what this means? |
After explaining opengl concepts the hardest part is knowing what you can do with it. The idea was to make a "Techniques" section showing various use cases for tranforms, frag shader, geo shader, compute shader. There's a lot you can cover. This would be a way for more advanced users to get started with the lower level stuff. |
Improving installation doc is on my todo list. Is there a way to manually set where the next/prev buttons on the pages go? It would make installation instructions easier to follow for absolute beginners by avoiding linking to the start of instructions for another OS. |
One other area we should look into is curating links to resources on math topics, or find a good source that's already doing that. |
Reorganize the documentation into the following four sections.
The programming guide and the tutorials will be made into printable/downloadable PDFs.
Programming Guide
Tutorials
Example Code
API Docs
Certain items would remain outside these sections, but still appear on the homepage:
The text was updated successfully, but these errors were encountered: