Add gist ontology layer and improve template documentation#1
Merged
snapsynapse merged 1 commit intomainfrom Apr 19, 2026
Merged
Add gist ontology layer and improve template documentation#1snapsynapse merged 1 commit intomainfrom
snapsynapse merged 1 commit intomainfrom
Conversation
Owner
snapsynapse
commented
Apr 19, 2026
- Add optional gist semantic layer (enabled by default): @type annotations on JSON API items, context.jsonld at api/v1/, and ontology attribution block in index.json; disable with ontology.enabled: false in project.yml
- Fix schema and data bugs: document source_file field, correct source_file paths in mapping/index.yml (container/ -> frameworks/), fix title: -> name: in CONTRIBUTING.md and VERIFICATION.md frontmatter examples
- Clarify secondary entity role in project.yml (inline/mapping-defined, not standalone files)
- Add validate.js error reference table to README
- Add MCP tool naming derivation table to README
- Improve .gitignore comment to explain Option A vs B for forks
- Sharpen Quick Start: fork vs clone distinction, specific first edit guidance, success signal for build step
- Add live demo link and "What it produces" section before examples
- Add ASCII data-flow diagram showing project.yml + data -> build -> docs
- Add "What to keep" callout in Replacing example data section
- Trim README Verification section to pointer; consolidate duplicate config prose in VERIFICATION.md
- Add optional gist semantic layer (enabled by default): @type annotations on JSON API items, context.jsonld at api/v1/, and ontology attribution block in index.json; disable with ontology.enabled: false in project.yml - Fix schema and data bugs: document source_file field, correct source_file paths in mapping/index.yml (container/ -> frameworks/), fix title: -> name: in CONTRIBUTING.md and VERIFICATION.md frontmatter examples - Clarify secondary entity role in project.yml (inline/mapping-defined, not standalone files) - Add validate.js error reference table to README - Add MCP tool naming derivation table to README - Improve .gitignore comment to explain Option A vs B for forks - Sharpen Quick Start: fork vs clone distinction, specific first edit guidance, success signal for build step - Add live demo link and "What it produces" section before examples - Add ASCII data-flow diagram showing project.yml + data -> build -> docs - Add "What to keep" callout in Replacing example data section - Trim README Verification section to pointer; consolidate duplicate config prose in VERIFICATION.md Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.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.