Expose Markdown headings and migrate to native Moon CI - #1
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.
Markdown rendering now returns heading metadata alongside HTML, so consumers can build an accessible table of contents using the same IDs as the rendered article. IDs are unique within a document, preserve existing IDs, and handle duplicate, Unicode, and empty headings. Content collection loaders expose this metadata as well.
Replace Taskfile with reusable Moon tasks and a standalone workflow following Moon’s CI guide: full history, frozen dependencies, plain
moon ci, explicit inputs/outputs, and native reports. The samemoon.ymlworks inside Listenbox’s submodule graph. Publishing remains a manual task.Validation: standalone native Moon CI passed all six tasks from a fresh clone, including 37 unit tests, six browser tests, lint, and both TypeScript checks. Listenbox’s guide integration passed 53 marketing browser tests and a build starting with no compiled Solid Static package. Package lint uses its own configuration in both workspaces.