Template: standardise the Example Queries section on the landing page - #2
Merged
Merged
Conversation
…plate Every provider site now closes its landing page with an "Example Queries" H2 (the shared table-of-contents entry), one intro sentence under it so the H2 never sits directly on an H3, and one H3 per example with a lead-in sentence and a sql block. The template header content carries that shape with the intro sentence as fixed text rather than a TODO, and README.md, CLAUDE.md and the skill reference describe the convention, including that the favicon files belong at the static/ root. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
A repository just created from the template has no provider-dev/config/spec_pin.json, so the build step failed on every push to the template itself and the scheduled spec-drift job opened a bogus drift issue. Both jobs now detect the missing pin, skip the pin-dependent steps with a notice, and run everything as before once a spec is pinned. The generation-drift check also excludes spec_pin.json, whose "fetched" date is refreshed by fetch-spec on every run. Co-Authored-By: Claude Fable 5.1 <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
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.
Summary
headerContent2.txt: the example section is now## Example Queries(the table-of-contents entry every provider site shares), followed by the fixed intro sentence (Try the following queries using \stackql shell`, or run them from a script or CI pipeline with `stackql exec`.) so the H2 never sits directly on an H3. Each H3 example carries a one-sentence lead-in ending in a colon before itssqlblock, and the TODO spells out the rules (heading text and intro fixed, last section of the file, no stacked headings, plain prose with-`).README.md,CLAUDE.mdand.claude/skills/stackql-provider-development/references/docs-and-ci.mddescribe the convention so new providers (and the skill) produce the same shape, and note that favicons must sit at thestatic/root (the shared config links them root-relative; copies understatic/img/are never used).Context
Applied across all 34 provider microsites in the September 2026 landing-page PRs; this makes it the default for new providers built from the template.
🤖 Generated with Claude Code
CI
The template has no
provider-dev/config/spec_pin.json(the firstmake fetch-specwrites it), sobuild-and-testfailed on every push to the template itself and the scheduledspec-driftjob kept a bogus "Upstream spec drift detected" issue open (#1, now closed). Both jobs now detect the missing pin, skip the pin-dependent steps with a notice, and run every step as before in a repository where a spec is pinned. The generation-drift check also excludesspec_pin.json, whosefetcheddate is refreshed byfetch-specon every run (the same fix applied to the godaddy repository).