DOCSP-46362 - TOC reorganization #191
Conversation
✅ Deploy Preview for docs-pymongo ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Get Started on one page now
There was a problem hiding this comment.
LGTM
I added 'Aggregation` as an L1 with a comment in the TOC spreadsheet, and updated the title of 'Versioning' to 'Reference'
|
Hey @mongoKart & @rachel-mack! One of my general TOC principles is that a category has to have more than one subcategory. Here, we have Aggregation, with the only thing under it as Tutorials, and then Tutorials has a bunch of stuff. Is there a way we can take out a level, either by calling the L1 'Aggregation Tutorials' or adding in some other content at the L2 besides Tutorials, so it's not lonely? |
Sure--I moved the tutorials to be L2 subpages of Aggregation. FYI @stephmarie17 |
|
@mongoKart , the aggregation section looks great. Thank you! The other thing I wanted to mention was that you've got one section that goes five deep, and I wondered if there was a way to reduce it by one level. Guidance from the TOC working group is that they want writers to go no more than four levels deep, and since we're re-doing the Drivers TOCs, they thought it would be good to fix it at the start, if possible. This one is Connect > Specify Connection Options > Enable Authentication > Authentication > [authentication options] Could the 'Authentication' heading disappear so the authentication choices are under 'Enable Authentication'? Just an idea; I don't know all the differences on these. |
Hey @sarahemlin, sorry about that; I intended only to put TLS in that menu, but accidentally added the entire Auth section. Now fixed, but it raises a new question: is it okay to have the same page linked in different sections of the TOC, like we're doing with TLS here? |
|
Hey @mongoKart, alas! We can't link the same page in two places on the same TOC. |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v4.10 v4.10
# Navigate to the new working tree
cd .worktrees/backport-v4.10
# Create a new branch
git switch --create backport-191-to-v4.10
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9192e1475756a87154432746be0f619514e5e4fa
# Push it to GitHub
git push --set-upstream origin backport-191-to-v4.10
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v4.10Then, create a pull request where the |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v4.9 v4.9
# Navigate to the new working tree
cd .worktrees/backport-v4.9
# Create a new branch
git switch --create backport-191-to-v4.9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9192e1475756a87154432746be0f619514e5e4fa
# Push it to GitHub
git push --set-upstream origin backport-191-to-v4.9
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v4.9Then, create a pull request where the |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v4.8 v4.8
# Navigate to the new working tree
cd .worktrees/backport-v4.8
# Create a new branch
git switch --create backport-191-to-v4.8
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9192e1475756a87154432746be0f619514e5e4fa
# Push it to GitHub
git push --set-upstream origin backport-191-to-v4.8
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v4.8Then, create a pull request where the |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v4.7 v4.7
# Navigate to the new working tree
cd .worktrees/backport-v4.7
# Create a new branch
git switch --create backport-191-to-v4.7
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9192e1475756a87154432746be0f619514e5e4fa
# Push it to GitHub
git push --set-upstream origin backport-191-to-v4.7
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v4.7Then, create a pull request where the |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v4.11 v4.11
# Navigate to the new working tree
cd .worktrees/backport-v4.11
# Create a new branch
git switch --create backport-191-to-v4.11
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9192e1475756a87154432746be0f619514e5e4fa
# Push it to GitHub
git push --set-upstream origin backport-191-to-v4.11
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v4.11Then, create a pull request where the |
(cherry picked from commit 9192e14)
Pull Request Info
PR Reviewing Guidelines
JIRA - https://jira.mongodb.org/browse/DOCSP-46362
Staging Links
Self-Review Checklist