Repository navigation
RFC-0042 / ADR-0044: Collections stage 3 (accepted) - #102
Merged
Merged
Conversation
JSON-LD presets (Event, JobPosting, Product, Recipe) mapped from fields, expiry as a render-time gate (unlist or hide), listings filtered and sorted by field with one shared evaluator, listing pages and per-collection feeds; references and repeaters left for stage 4. The schema diff was checked with pnpm gen (TypeScript and Rust) and reverted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Madraka <8898640+Madraka@users.noreply.github.com>
Halil accepted RFC-0042 with every open question decided as recommended. ADR-0044 records the decision. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Madraka <8898640+Madraka@users.noreply.github.com>
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.
Stage 3 of #71, after RFC-0040 (collections) and RFC-0041 (typed fields). Status: Draft; nothing is implemented.
Key decisions
listFields(≤ 4 keys),expiry({field, action: unlist|hide, afterMinutes?}) andstructuredData({type, properties}).contentListsections gainwhere(≤ 4 conditions) andorderBy. Which properties each type accepts, and with which field types, is a closed table in code. NoschemaVersionbump.withStructuredData()replaces the genericBlogPosting.entryHeadis unchanged, so old themes keep today's output.jsonLdText, capped at 32 KB.min(availability.until, field date + grace).unlist(default): the page stays live but leaves listings, feeds, the sitemap and search.hide: 404.schedule_unpublish.nowis the only relative value. One evaluator is shared by themes,ContentList, the API, MCP and Studio. No indexes in stage 3 (nodesis shared across sites); a side table follows only if a 10,000-entry benchmark needs it. Studio list columns come fromlistFields.contentList.<prefix>/rss.xmlthrough a middleware, only where the theme answers 404.Schema check:
pnpm gen(TS + Rust), the core-contracts tests (492) andcargo test -p cloudhal-schemapass. cargo-typify merged two inlinepropertyenums into one type, so they moved into named$defs; the RFC records this.The 11 open questions, with recommended defaults, are at the end of the RFC.
🤖 Generated with Claude Code