Repository navigation
Organize wiki into topic CMS collections while preserving URLs - #52
Merged
Merged
Conversation
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
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.
Changes
Replace the single large Pages CMS collection with 12 topic groups and 54 alphabetic leaf collections for 1,150 articles. Keep every existing
/wiki/pages/<Filename>URL, cross-link, tag, alias and legacy redirect. GitHub edit/create links target the physical source folders. Add reader breadcrumbs, topic listings, production canonical URLs and non-indexable previews without duplicate hierarchical article URLs.Enable Markdown WYSIWYG editing with an Editor/Source switch and update contributor instructions. Use Source mode for spoilers, includes, HTML, scripts and components. Article content is unchanged apart from include-path adjustments and the contributor-guide update.
Optimize autolinking with precomputed URL-to-term lookups and one lowercase conversion per text node. One comparison with the same Docker/Node CPU-profiler settings measured 156.04 → 78.69 seconds (49.6% faster); runtime varies.
Validation
/wiki/,/, and/wiki/pr-99/.noindex, nofollow.Remaining live checks
Pages CMS cold loading/reloading, trusted-editor saves/new-page creation, special-Markdown WYSIWYG round trips and deployment remain unverified. Check all leaf collections, including the oversized Shaman Guide and empty Classes collection, and record results in this PR.