-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Docs: Relabel and reorganize hosting features as reference (Diátaxis) #9952
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
Docs: Relabel and reorganize hosting features as reference (Diátaxis) #9952
Conversation
…rganizing content
Dropped @agjohnson from Advocacy team reviews for now, so he doesn't get pinged on these. |
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.
@benjaoming I started a review here, but this document feels half baked. There's a bunch of broken links, and lots of ways the language could be improved with some simple edits.
Should I be doing a full second edit of this instead of a review? It would be good to clarify that in the PR.
…g into diataxis/split-hosting-features
Co-authored-by: Eric Holscher <[email protected]>
The PR had a lot of restructuring, so I didn't feel comfortable sitting with it for so long without having another pair of eyes. It would be super-nice if you want to go over it for a second edit and just change anything you come across 👍 I wouldn't mind postponing further improvements to later. I can't help but feel that there is something weird about describing Sitemaps and CDN in the same page. But it's possibly better saved for another iteration. |
@benjaoming I started to do a second edit of this content, but the structuring feels weird to me. I think the hosting feature overview is definitely a sales/marketing type page. I don't think it makes sense at the top of a feature page for the actual hosting features. Perhaps it just doesn't have a good home in this new layout, and the marketing pages are doing the job it was meant to do, and we can just delete it? It seems to me like each of these major hosting features should probably be it's own feature page (CDN, Custom 404, Sitemaps, robots.txt), and we should remove the marketing copy at the top. I can do that refactor tomorrow if you agree that is a reasonable path forward. |
Sorry, was taking a long time to digest this!! I agree. The "hosting" umbrella wasn't very good, and each of these features go beyond what hosting means. The |
Great! I will try to knock that out this week. 👍 |
Ended up writing a bunch of additional content here, since these features were barely documented... This will be a big win for our users.
Just pushed an initial refactor of features into dedicated pages. Ended up writing a bunch of additional content here, This will be a big win for our users. |
@ericholscher I've added a bunch of suggestions but I'll hold off a bit. If you recall #9983, there are some changes in I think it's best if you merge and resolve conflicts firstly and then I'll continue reviewing 👍 |
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.
This is looking great 👍
I stopped the review midway... My goal was to add EVERYTHING as a suggestion :) I succeeded so far.. but am a bit worried about the merge conflicts that are coming up.
docs/Makefile
Outdated
@@ -7,7 +7,7 @@ | |||
# (except for '--keep-going', failing fast is prefered on local builds) | |||
# We also remove '-E' to reduce the time of rebuilding reference indexes | |||
# on each build. | |||
SPHINXOPTS = -T -j auto -W | |||
SPHINXOPTS = -T -W |
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.
Pretty sure that -j auto
is the default in our Sphinx builder?
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.
Oh yea, I was getting errors on this locally, but I just needed to update my depednencies.
Yea, I saw those. Shouldn't be too bad to resolve, since I'm mostly just adding new pages. I assume it'll be just using the existing TOCTree, add the 4 files, and the content up top. |
Resolving conflicts... |
…g into diataxis/split-hosting-features
…nx DirHTML builder.
Continuing the 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.
Alright, here comes another round of suggestions!
I hope I didn't mess up and write comments that weren't directly phrased as suggestions :)
integrated nicely into the URL of your documentation. | ||
This is served at ``/en/latest/`` by default. | ||
If you only have 1 version and translation, | ||
we also support :doc:`single version projects </single_version>` served at ``/``. |
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.
This is a really nice purposeful use of the introduction, clarifying a basic misconception that somehow multiple versions are required 👍
Co-authored-by: Benjamin Balder Bach <[email protected]>
@benjaoming Should be ready for a final 👍 if it looks good. |
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.
Now builds and looks good!! Thanks, this was a big one!
Changes:
TBD: There's some leftovers of explanation and instructions, but those are all so short that they make very little sense in their own how-to guides.
💡 if we have a lot of small things for either Sphinx or MkDocs, we could consider writing how-tos like "The most popular tweaks for Sphinx projects" where we just mention these in a way that can be referenced.
Refs: #9746
📚 Documentation previews 📚
docs
): https://docs--9952.org.readthedocs.build/en/9952/dev
): https://dev--9952.org.readthedocs.build/en/9952/