Repository navigation
py-doc new FILE.md numbers an existing Markdown file; a guide page fo… - #135
Merged
Merged
Conversation
…r legacy files py-doc new FILE.md gives an existing Markdown file the next number and writes its legacy build file beside it, naming the file in entries; the Markdown is not changed. The title comes from its front matter, else its first heading, and the author, version, classification and description from its front matter, as defaults the options and the wizard can change. A file whose front matter has a document_number, or that a build file in the register already uses, is refused. The paths it prints are relative to the current folder, so the build command it suggests works as shown. docs/guide/10_legacy.md describes everything legacy in one place: the build file key by key (read, ignored or unsupported), build --legacy, new and its wizard, numbering an existing file, the register (number format, lists, the first register, --scan, --start, working on branches), the directives legacy documents use, and migrate. The reference page points to it, and it is in the user guide, the guide's index and the README. The reference no longer says the version in the file name and the status templates have no equivalent: migrate carries both over. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ket2UPXgz46XKSUqpuPixk
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.
…r legacy files
py-doc new FILE.md gives an existing Markdown file the next number and writes its legacy build file beside it, naming the file in entries; the Markdown is not changed. The title comes from its front matter, else its first heading, and the author, version, classification and description from its front matter, as defaults the options and the wizard can change. A file whose front matter has a document_number, or that a build file in the register already uses, is refused. The paths it prints are relative to the current folder, so the build command it suggests works as shown.
docs/guide/10_legacy.md describes everything legacy in one place: the build file key by key (read, ignored or unsupported), build --legacy, new and its wizard, numbering an existing file, the register (number format, lists, the first register, --scan, --start, working on branches), the directives legacy documents use, and migrate. The reference page points to it, and it is in the user guide, the guide's index and the README. The reference no longer says the version in the file name and the status templates have no equivalent: migrate carries both over.
Claude-Session: https://claude.ai/code/session_01Ket2UPXgz46XKSUqpuPixk