Page templates, lint-on-PR, and editing-language tidy#16
Merged
Conversation
added 3 commits
June 2, 2026 15:37
Replace the prose-only canvas descriptions in SCHEMA.md with ready-to-insert
template files in wiki/templates/ — one per page type (data-product, service,
process, team-resource, person, concept, comparison) plus a raw-source skeleton.
Each carries the required frontmatter and section headings with (TBD)/%% hints,
so section structure stops drifting between hand-written pages.
Templates fill {{title}}/{{date}} via Obsidian's built-in Templates plugin
(.obsidian/templates.json points it at wiki/templates). The folder is already
excluded by quartz ignorePatterns and the linter only scans entities/concepts/
comparisons, so templates are never published or linted.
README and SCHEMA now point contributors at the template files and document the
"create note -> Insert template" workflow.
Closes #10
Refs #14
Add a lightweight lint workflow (node scripts/lint.mjs) triggered on pull_request and push to main, so bad frontmatter, broken wikilinks, orphans, or a stale index are caught on the PR instead of only post-merge as a failed deploy. Separate from deploy.yml to stay fast (no Quartz clone). Mark 'lint' a required check on main. Closes #15
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.
What
Three changes:
Page templates (
wiki/templates/) — one ready-to-insert file per canvas(data-product, service, process, team-resource, person, concept, comparison)
plus a raw-source skeleton. Each carries the required frontmatter and section
headings with
(TBD)/%%hints, so structure stops drifting betweenhand-written pages. Wired to Obsidian's built-in Templates plugin via
.obsidian/templates.json. The folder is excluded by QuartzignorePatternsand the linter only scans
entities/concepts/comparisons, so templates arenever published or linted. README + SCHEMA document the
"create note → Insert template" workflow.
Lint on pull requests — new lightweight
lint.ymlrunningnode scripts/lint.mjsonpull_requestandpushtomain, so badfrontmatter / broken wikilinks / orphans / stale index are caught on the PR
instead of only post-merge as a failed deploy. After merge, mark
lintarequired status check on
main.Editing language — reframe the README away from overt "LLM Wiki" branding
toward a team-maintained knowledge base. Protocol unchanged.
Issues
workflow doc are still open, so Test workflow for Caltrans computers #14 stays open.
Notes
npm run checkpasses locally (16 pages, 0 errors, 0 warnings).lintas a required check is a one-time GitHub branch-protection step.