-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Create docs folder #59
Comments
Not sure about README. The root of the project is a good place for README so that anybody can find and read it. |
If you are not sure, what do you suggest to remove the uncertainty? We can try it out. |
Sure we can try it out with GitHub. But it's hard to try it out with developers and users. We probably will never know if one will get some difficulties while searching for the README. So I'd leave README in the root as it do a lot of another developers (if not all of them). |
I did not mean to move the README.rst to the docs folder. There should be a new README.rst in the docs folder to give the overview over the different docs files in the docs folder. If you look at the docs folder from the github site, then you see the README in the folder and what docs are available. |
Oh, if so then it probably should be index.rst. This seems traditional for the rst documentation index file. Maybe I'm wrong, then correct me please. |
Sounds good. Changed it :) |
However, I'm not sure GitHub can render index.rst by default. I'm also not sure index.rst makes sense for GitHub because it will probably fail on rendering cross-links in the rst format, so we will have to use plain http links. Finally, if you want to make all the documentation accessible on GitHub then it is probably better to add direct links to those pages just in the README in the root folder. |
So be it. |
The documentation of the module should be in the docs folder.
The text was updated successfully, but these errors were encountered: