-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Single file vs Multiple Files vs GitHub Pages #15
Comments
Completely unrelated side note: it'd be cool if you guys used a service like ReadTheDocs to render and host the markdown. It looks really cool! |
Reading, referring back and searching through the document is so much easier using a single page for all of it. I hope it is kept this way. |
OTOH, editing a single document is far from convenient. It's not easy to locate the place where you want to make edits, and (at least on my system) GitHub is unable to show changes preview for such a huge file. |
For the time being we are preferring the status quo. Thank you for the suggestion! |
Please reconsider. In-browser diff is just too convenient, especially as this keeps being a work in progress. |
Having the contents of the guidelines in a single Markdown file seems an odd decision. Why not split each section into a separate Markdown file? By doing so, you'd make the merging of pull requests much easier.
Also, has the Foundation considered trying to use GitHub Pages for presenting the material?
The text was updated successfully, but these errors were encountered: