-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Update docs #3498
Update docs #3498
Conversation
The most relevant commits are: Note: the whole docs needs to be re-wrapped to 80 chars, for now I only did this for the files I touched. |
I'm generally -1 on breaking docs at 80 characters. I'd much prefer to have them broken on semantic meaning (eg. periods or commas). This has a bit more background here: http://rhodesmill.org/brandon/2012/one-sentence-per-line/, but I feel pretty strongly against just doing a straight "80 char" break. |
I'd also ask that we not refactor content when we also change it in the PR. It makes it almost impossible to see what actually changed, so almost impossible to review. |
In general I love docs changes though! Thanks for doing these, and I'll try and figure out what exactly is going on, so I can review it. |
Also, we should definitely have a doc style guide, to answer questions like these :) |
@stsewd Can you add the doc styleguide in this PR? It can probably go in the CONTRIBUTE doc on the website if it is small, at this point. |
We can probably steal a decent bit from here: https://github.com/writethedocs/www/blob/master/docs/style-guide.rst |
@RichardLitt I added some guidelines as suggested :). I feel like we need to improve a little more the section for contributing to the docs (and putted it a little closer to the Contributing to Read the Docs section), but probably another PR. @ericholscher you are right, breaking the lines at semantic meaning rather that 80 chars is a good idea, the explanation from the post is very clear. Should I revert the other commits then? |
docs/builds.rst
Outdated
@@ -37,8 +37,6 @@ We will look inside a ``doc`` or ``docs`` directory first, | |||
and then look within your entire project. | |||
|
|||
Then Sphinx will build any files with an ``.rst`` extension. | |||
If you have a ``README.rst``, | |||
it will be transformed into an ``index.rst`` automatically. | |||
|
|||
Mkdocs |
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.
Should be MkDocs? (uppercase D)
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.
Yeah, that's the correct way of writting it: http://www.mkdocs.org/
I reverted the noisy commits and applied the style guide as mentioned, this is ready for another review. |
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.
Nice! Thanks @stsewd. I left a couple of comments for you to take a look :)
docs/docs.rst
Outdated
@@ -10,4 +10,29 @@ You can build the docs by installing ``Sphinx`` and running:: | |||
# in the docs directory | |||
make html | |||
|
|||
Let us know if you have any questions or want to contribute to the documentation. | |||
Please follow these guidelines when updating our docs. | |||
Let us know if you have any questions or if something isn't clear. |
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.
Remove the if
from "if something"
docs/docs.rst
Outdated
------- | ||
|
||
* Do not break the content across multiple lines at 80 characters, | ||
but rather broken them on semantic meaning (e.g. periods or commas). |
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.
break them
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.
Also, I think it would be awesome to link the post that Eric shared with you. You said that was useful to understand this idea, so may be good to link it here.
@@ -57,7 +57,7 @@ environment, and will be set to ``True`` when building on RTD:: | |||
{% endif %} | |||
|
|||
I get import errors on libraries that depend on C modules | |||
---------------------------------------------------------- | |||
--------------------------------------------------------- |
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.
Did you remove this for some reason? Just curious :)
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.
@humitos the header is larger than the text p:
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.
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.
I use rstcheck for linting rst files :)
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.
Wow! I didn't know it and I'm a fan of @myint.
Considering that we are talking about the documentation style, I think it would be a good addition for travis checks and linting right? I mean, trigger a linting on the docs on travis checks.
Would you like to add an issue for this and take a look on what's needed and how to implement it?
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.
Sure, I opened a new issue #3622, I will implemented later :)
@humitos all the corrections were done, thanks! |
Nice! I'm asking Eric for review this since he is the "English guy". Although, it's good enough for me. |
Love doc updates :) 💯 |
@humitos Feel free to ask me for English updates, too. :) |
Probably closes:
This page does not exist yet
error AfterPassing
build #2472