Skip to content

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

Merged

Conversation

benjaoming
Copy link
Contributor

@benjaoming benjaoming commented Jan 26, 2023

Changes:

  • New hosting feature overview, using short sentences and references to "read more"
  • Added additional features that may be understood as hosting
  • Added link to the general features overview
  • Organized Sphinx/MkDocs reference as tabs
  • Added instructions for custom 404s on MkDocs
  • New level "Built-in content" meant to reflect auto-generated contents that we host - robots.txt, 404s and sitemaps.

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 📚

@benjaoming benjaoming added Improvement Minor improvement to code Needed: documentation Documentation is required labels Jan 26, 2023
@benjaoming benjaoming requested a review from a team as a code owner January 26, 2023 16:05
@benjaoming benjaoming requested a review from agjohnson January 26, 2023 16:05
@benjaoming benjaoming changed the title Docs: Reorganize hosting features as reference (Diátaxis) Docs: Relabel and reorganize hosting features as reference (Diátaxis) Jan 26, 2023
@agjohnson agjohnson requested review from ericholscher and removed request for agjohnson January 30, 2023 17:52
@ericholscher
Copy link
Member

Dropped @agjohnson from Advocacy team reviews for now, so he doesn't get pinged on these.

Copy link
Member

@ericholscher ericholscher left a 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.

@benjaoming
Copy link
Contributor Author

benjaoming commented Feb 1, 2023

@ericholscher

Should I be doing a full second edit of this instead of a review? It would be good to clarify that in the PR.

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.

@ericholscher ericholscher self-requested a review February 1, 2023 23:54
@ericholscher
Copy link
Member

ericholscher commented Feb 2, 2023

@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.

@benjaoming
Copy link
Contributor Author

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 reference/features/ structure can hold many feature descriptions and I think that adding these pages individually there would be a welcome "content dumping" for the next step of putting together a good feature reference overview.

@ericholscher
Copy link
Member

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.
@ericholscher
Copy link
Member

Just pushed an initial refactor of features into dedicated pages.

Ended up writing a bunch of additional content here,
since these features were barely documented...

This will be a big win for our users.

@benjaoming
Copy link
Contributor Author

benjaoming commented Feb 10, 2023

@ericholscher I've added a bunch of suggestions but I'll hold off a bit.

If you recall #9983, there are some changes in diataxis/main waiting.

I think it's best if you merge and resolve conflicts firstly and then I'll continue reviewing 👍

Copy link
Contributor Author

@benjaoming benjaoming left a 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
Copy link
Contributor Author

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?

Copy link
Member

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.

@ericholscher
Copy link
Member

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.

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.

@benjaoming
Copy link
Contributor Author

Resolving conflicts...

@benjaoming
Copy link
Contributor Author

Rrrrrrrrrrrrrreeeeeee--solved!

image

@benjaoming
Copy link
Contributor Author

Continuing the review...

Copy link
Contributor Author

@benjaoming benjaoming left a 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 ``/``.
Copy link
Contributor Author

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]>
@ericholscher
Copy link
Member

@benjaoming Should be ready for a final 👍 if it looks good.

Copy link
Contributor Author

@benjaoming benjaoming left a 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!

@benjaoming benjaoming merged commit 739fd3b into readthedocs:diataxis/main Feb 14, 2023
@benjaoming benjaoming deleted the diataxis/split-hosting-features branch February 14, 2023 15:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Improvement Minor improvement to code Needed: documentation Documentation is required
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants