DOCSP-49937: Remove legacy build toolchain instructions - #192
Closed
emetozar wants to merge 1 commit into
Closed
Conversation
❌ Deploy Preview for mongodb-docs-meta failed. Why did it fail? →
|
🔄 Deploy Preview for mongodb-docs-meta processing
|
The legacy Giza/Sphinx toolchain docs have been archived, so remove the build tool install page, its steps file, the toctree entry, and the Install Build Tools step in the repo setup tutorial.
emetozar
force-pushed
the
DOCSP-49937-remove-legacy-build-tools
branch
from
July 29, 2026 15:28
abfebae to
23e201d
Compare
Author
|
Closing this — wrong repo. This repo is deprecated and content changes belong in the monorepo, under Redone as https://github.com/10gen/docs-mongodb-internal/pull/22485, which also picks up two things that don't exist here: the unified ToC entry and the legacy meta sidenav ToC (in both platform app copies), plus a redirect for the removed URL. For anyone who finds this later: the deploy preview failures on this PR were not caused by the change. The build died in |
mongodb-server-docs-sync-bot Bot
pushed a commit
to mongodb/docs
that referenced
this pull request
Jul 29, 2026
…a (#22485) ## DESCRIPTION All docs built off the legacy Giza/Sphinx toolchain have been archived, so the build tool install page is no longer relevant. This removes the page and everything that pointed at it. Content (`content/meta/`): - Delete `source/tutorials/install.txt` (Installing MongoDB Documentation Build Tools) - Delete `source/includes/steps-install.yaml`, the steps file it included; not referenced anywhere else - Remove `/tutorials/install` from the Tutorials toctree in `source/tutorials.txt` - Remove the "Install Build Tools" step from `source/includes/steps-repo.yaml`, which was the only remaining inbound `:doc:` reference - Add a redirect in `netlify.toml`: `/docs/meta/tutorials/install/` -> `/docs/meta/tutorials/` Unified ToC (per the `unified-toc` skill): - `content/table-of-contents/docset-data/meta.ts` — removed the entry - `platform/docs-site/.../legacy-docs/meta-main.ts` and `platform/docs-nextjs/.../legacy-docs/meta-main.ts` — removed the entry from both copies Worth a reviewer's eye: `meta` is listed in `legacyTocProjects` in `unified-toc-context.tsx`, so the meta sidenav renders from `legacy-docs/meta-main.ts` rather than from `docset-data/meta.ts`. Updating only docset-data would have left a dead link in the live sidenav, so both are updated. No `isExternal` symlinks to this page exist in the ToC. `pnpm tsc --noEmit` passes in `content/table-of-contents`. Out of scope, flagging rather than changing: - `./lint-docs.sh all` reports 2 errors + 2 warnings on `source/tutorials.txt` (short title, missing meta description, short H1, low content). All four pre-exist on `main` — verified by stashing and re-running. The only delta is the page word count, 13 -> 12, from removing one toctree line. - Several `content/manual/*/CONTRIBUTING.rst` and `content/ruby-driver/*/README.rst` files link to the old URL as an external link. The redirect above keeps those resolving. Some are EOL versions, so I left them alone. - The pre-commit hook regenerated 6 unrelated `offline-docs` files (atlas-architecture, ops-manager, development) from pre-existing docset-data drift on `main`. `meta` appears in zero offline-docs files, so none of it relates to this change and I dropped it from the commit. Someone may want to regenerate those separately. Supersedes mongodb/docs-meta#192, which I opened against the deprecated standalone repo before learning content changes belong here. ## STAGING Pending cloud build. ## JIRA https://jira.mongodb.org/browse/DOCSP-49937 ## SELF-REVIEW CHECKLIST - [ ] Does each file have 3-5 taxonomy facet tags? (n/a — deletion only, no new pages) - [x] Is this free of any warnings or errors in the RST? - [x] Is this free of spelling errors? - [x] Is this free of grammatical errors? - [ ] Is this free of staging / rendering issues? - [x] Are all the links working? - [ ] If this documents a server feature and is presented in any downstream product teams, have you reached out to writers on those teams? (n/a) - [ ] Is there a public preview/GA requirement for this content change? (n/a) - [ ] For features gated by server version, confirm a DRI has reviewed this text. (n/a) ## EXTERNAL REVIEW REQUIREMENTS [What's expected of an external reviewer?](https://wiki.corp.mongodb.com/display/DE/Reviewing+Guidelines+for+the+MongoDB+Server+Documentation)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jira
https://jira.mongodb.org/browse/DOCSP-49937
Summary
All docs built off the legacy Giza/Sphinx toolchain have been archived, so the build tool install page is no longer relevant.
source/tutorials/install.txt(Installing MongoDB Documentation Build Tools)source/includes/steps-install.yaml, the steps file it included/tutorials/installfrom the Tutorials toctreesteps-repo.yaml, which was the only remaining inbound:doc:referenceNo dangling references to the removed page remain.
Note
No redirect was added —
config/redirectscurrently has no entries and the page wasnoindex, nosnippet. Happy to add one if the team wants /docs/meta/tutorials/install pointed somewhere.