-
Notifications
You must be signed in to change notification settings - Fork 42
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
Cleanup Docs #705
Cleanup Docs #705
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Developing/Coding
sounds redundant and Developing/Contributing
sounds like it should be the other way around. What's the rationale for the new structure? What will eventually it look like?
Contributing is for non-coders (people like me who don't get deep into the Coding is then the opposite of Contributing. This is where the hacking guide, AI, FCDB, and other code related documents go. I can see that this directory will get a lot of documents as we expose more details to the code to the community. I think the more we are open about the code and how to contribute there is going to help a lot. |
I would see something like this…
|
Ok let me do another commit |
Collection of commits to clean up the
/docs
files after all the legacy files indoc
were converted. Also moved some files around to be ready for other documentation issues to be completed in the near future.