Repository navigation
feat(site): build named sites through depot product tasks - #96
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.
Build static sites through the shared product requests and depot tasks. Named catalogs retain unselected regional topics; immutable product dependencies, assets and indexes form a complete saved layout that can be restored into another directory. Player read sets cover requested variants and compare sampled plans with full simulations.
Publication writes assets and products before entry manifests and indexes, preserves the previous successful-run pointer on failure, and collects retired owned files after successful replacement. Command and architecture documentation describe the catalog, task and layout contracts.
Validation: full Python suite (1761 passed, 6 skipped), focused read-set/catalog/CLI regressions, Ruff, import contracts, strict documentation build, and product content validation. Synthetic tests cover partial updates, region aliases, failure recovery, remote restoration and collection reachability.