-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
README.md not found #1615
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
Comments
Workaround: I moved the contents all of |
I've just noticed similar behaviour. Contrary to what is stated in https://read-the-docs.readthedocs.org/en/latest/builds.html
What it actually does is create a directory called README with an index.html file inside it. This is not the behaviour required. It should create the index.html at the level the README.md was and not README/index.html |
Is this what's breaking all our docs? We now have to access the docs at http://sr-build-tools.readthedocs.org/en/latest/README/ instead of simply http://sr-build-tools.readthedocs.org Cheers, Ugo |
Me too: the top page, https://installation-images.readthedocs.org, does not work but https://installation-images.readthedocs.org/en/latest/README/ does. |
While I would prefer RTFD to automatically display the README.md files similarly to what GitHub does, it would be also fine to specify it in |
Hi all!, I think this feature (renaming README files to index files) was removed. The docs needs to be updated (#3498 ) |
Docs updated on d907524 (merged). |
I see this is still an open issue, and I believe I have seen several issues in regards to the Specifically, I am very much interested to know if there is a way to configure ReadTheDocs to simply use README.md as the index file - as is the practice on GitHub itself and GitHub Pages. this will make it fully compatible across three platforms. |
Thanks a lot. I see the PR is open and I am unsure of the vibe there: Is it a feature that will make it (back?) in? Or is the plan to leave it as "index is the only index"? |
I think is just index the only index. The PR is more to always have an index to serve, so the user doesn't think that their docs are broken or something. |
I see. I wish it was different - I really like cross-platform compatibility, and was hoping I can use the same repo for both GitHub pages and RTD. |
I think this needs a design decision, otherwise the issue is solved as we don't serve README files as index |
Well, as it seems this issue is one comment away from being closed, I leave you with food for thought: There is only something to gain, and probably nothing to lose, by having a logic that shows |
Well, I kind of think this should be a sphinx/mkdocs option. But I also discovered this mkdocs/mkdocs#321, as some users were depending on the rename step. What about just creating a symbolic link? I also believe that the original issue was because rtd was renaming the README file at that time. Also the recommended layout is this https://www.mkdocs.org/user-guide/writing-your-docs/#file-layout For the sphinx side, you can use the include directive too https://stackoverflow.com/questions/46278683/include-my-markdown-readme-into-sphinx/46286751#46286751 |
Just commenting that mkdocs already handles this https://www.mkdocs.org/user-guide/writing-your-docs/#index-pages, README files are converted to index files. For sphinx, the include directive is still valid, or use this method for md files inside rst sphinx-doc/sphinx#2840 (comment) @DannyBen let me know if that solves your problem or if there is something else to consider here. |
Hi and thanks for the readthedocs.org project,
I'm using readthedocs.org and mkdocs for the following project:
https://github.com/Orange-OpenSource/fiware-cepheus/
All docs are in 'doc' and only have README.md files (as github displays them by default), and using the following mkdocs.yml with explicit pages:
mkdocs is working fine localy (mkdocs 0.14.0, pip pip 7.1.2, python 2.7) to generate the doc but fails during build on readthedocs.org:
I expected not to be forced to use index.md if all pages are explicitly listed in the
mkdocs.yml
.Am I wrong ?
The text was updated successfully, but these errors were encountered: