Repository navigation
Conversation
The examples page was one entry inside "G-code Programming", easy to miss for readers who already know G-code. Give it its own section in the HTML index and its own part in the PDF, placed right after "G-code Programming", and keep docs.xml's prev/next order in step. No page content or anchors change. Closes LinuxCNC#2085
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.
Closes #2085
The G-code examples page was one entry inside "G-code Programming", which is easy to miss for readers who already know G-code. This gives it its own heading, as discussed in the issue (master, per @BsAtHome):
docs/src/index.tmpl: a new "G-code Examples"<details>section right after "G-code Programming"; the existingexamples/gcode.htmllink moves into it.docs/src/Master_Documentation.adoc: a new= G-code Examplespart after "G-code Programming" that includesexamples/gcode.adoc(leveloffset 2, like its neighbours), so the PDF matches.docs/src/docs.xml:examples_gcodemoved aftergui_image-to-gcode, so the prev/next buttons follow the index order (perdocs/README.adoc).No page content or anchors change, so existing links keep working. Not built locally (no asciidoc toolchain on this machine); relying on the htmldocs check.