feat: publish material chapters as standard.site documents#6
Merged
Conversation
Generalize the publisher from blog-only to any content type. It now takes a
list of DocumentSource ({ contentType, entries }) and publishes one
site.standard.document per non-hidden entry across all sources, using
/<contentType>/<slug> as the path. Prune spans the union of all live slugs.
build.ts passes both blog and material sources. Sites without a material folder
(e.g. angular.schule) get an empty material source, so their output is
unchanged.
This was referenced Jul 22, 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
1 participant
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.
Generalizes the standard.site publisher from blog-only to any content type, so sites with material chapters (angular-buch.com) publish those too.
Changes
publish.ts:publishStandardSite(sources: DocumentSource[])whereDocumentSource = { contentType, entries }. Publishes onesite.standard.documentper non-hidden entry across all sources with path/<contentType>/<slug>; prune spans the union of all live slugs. Guards against a duplicate rkey across content types.build.ts:buildMaterial()now returns its entries; bothblogandmaterialsources are passed to the publisher.Backward compatibility
Sites without a
materialfolder (angular.schule) get an empty material source → identical output (blog-only), same rkeys, no record churn.Verification
npm run typecheckclean./blog/…or/material/…path. No writes.