docs: lowercase org name in URLs (credit @danlessa)#9
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
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.
Summary
Cherry-picks three case-only changes from @danlessa's closed PR #7 to lowercase
DynamicalSystemsGroup→dynamicalsystemsgroupin GitHub URLs across docs and mkdocs config. Preserves the originalblockscience/...lowercase convention the repo started with.Commits are authored by @danlessa so contribution attribution is preserved.
Files
docs/index.md— 2 example tree-link URLsdocs/ontology.md— 2 ARCHITECTURE.md link URLsmkdocs.yml—repo_urlandrepo_nameThe README and the
site_urlwere already lowercase after #8 and weren't touched.Context
PR #7 (#7) duplicated the BlockScience → DynamicalSystemsGroup rebrand done in #8 and was closed without merging because it would have reintroduced an unrelated
mtg-kcURL regression. The cosmetic casing changes from that PR are worth keeping on their own, hence this follow-up.Test plan
docs.ymlredeploys; site continues to return 200🤖 Generated with Claude Code