DOCS: [GitBook] Refactor structure to match URL paths and fix missing page links#3613
Merged
tlimoncelli merged 6 commits intoStackExchange:mainfrom Jun 11, 2025
Merged
Conversation
cafferata
force-pushed
the
docs/gitbook-summary
branch
from
071c6f8 to
b83d0aa
Compare
cafferata
changed the title
tlimoncelli
approved these changes
Jun 11, 2025
Contributor
|
sweet!! |
AsifNawaz-cnic
pushed a commit
to centralnicgroup-opensource/rtldev-middleware-dnscontrol
that referenced
this pull request
Jan 19, 2026
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.
This PR addresses a structural issue in the Gitbook documentation that prevented the pages
Concurrency VerifiedandDual Hostfrom being properly linked and discoverable.To make the structure more transparent for newcomers and better aligned with the Gitbook-generated URLs, I've started by moving all Markdown files into their respective directories. This aligns our repository structure with the published documentation and should reduce confusion going forward.
Special thanks to @chicks-net for identifying the issue.
refs: #3608 #3607
The result can be seen in the following screenshot and live preview:
➡️ View rendered output on Gitbook