Hypothesis review comments + home and Why VCALM copy edits#11
Merged
Conversation
Wire the Hypothesis embed into the base layout for inline, text-anchored review comments, as a ready-made alternative to pasting page snippets into Slack. It is off by default so production ships no third-party script. A review build enables it with HYPOTHESIS_COMMENTS=1, and HYPOTHESIS_GROUP scopes the client to a Hypothesis private group so only logged-in DB group members see and post comments. Config lives in site.js; the layout only emits the script (and the group config) when enabled. Document the env vars and the private-group / access-gated review pattern in the README. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Cloudflare Pages previewDeployed this PR to a live preview: https://feature-hypothesis-comments.learnvcorg.pages.dev This deploy: https://32b471a7.learnvcorg.pages.dev Updated for commit fd5205d. |
Wire the Hypothesis env vars into the Cloudflare Pages preview build so each PR preview carries inline review comments, scoped to a private group. Production (GitHub Pages) is untouched and never loads Hypothesis. The build only enables comments when the HYPOTHESIS_GROUP repository variable is set, so previews stay clean until the private group id is configured. Harden the site config so comments require both the flag and a group, never loading in public groupless mode by accident. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Work through the review notes left on the home page: - Lead with Student IDs; rename Education to "Diplomas"; hide Supply Chain from the chooser, nav, footer, sitemap, and llms.txt for now (the page still builds at /supply-chain/ and is one line to relist). - Rewrite the "Why VCALM?" blurb around the vendor-lock-in framing and the formats/protocols VCALM supports (W3C VCs, mDL, mDoc, SD-JWT, OID4VCI, OID4VP, HAIP, DIDComm). - Expand "VCALM" to its full name in the site description, tighten the call to action, and update the company blurb. - Add a question mark to "What is VCALM?", drop the "Why VCALM" and "See an example" links for now, collapse the footer About column, and add Verifiable Credentials and Decentralized Identifiers reference links. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Section 5 led with the feature ("native W3C Verifiable Credentials"),
which doesn't tell the reader why they should care. Lead with the
advantage instead — no format lock-in — and make format support the
supporting evidence.
- Heading: "Native W3C Verifiable Credentials — and the rest"
→ "No format lock-in — bring any credential format".
- Body leads with issuing the format each relying party needs, mixing
them, and changing later without re-architecting; W3C VCs / SD-JWT /
mdoc become the proof, not the headline.
- At-a-glance row reframed to "Freedom to choose credential format".
This also makes the section consistent with the page's other
benefit-led headings.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
djscruggs
changed the title
The home page lists the full set of formats and protocols VCALM supports, but the Why VCALM format section listed only W3C VCs, SD-JWT, and mdoc. Align it so the two pages agree. - Body now names W3C VCs, SD-JWT, ISO mdoc, and mDL as formats, and OID4VCI, OID4VP, HAIP, and DIDComm as protocols (kept distinct so the formats-vs-protocols claim stays accurate). - At-a-glance row reads "W3C VCs, SD-JWT, mdoc, mDL, and more". The "Does VCALM support W3C Verifiable Credentials?" FAQ stays focused on that specific question. Co-Authored-By: Claude Opus 4.8 <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.
This branch grew to cover three related pieces of the review/iteration workflow. Grouped by commit below.
1. Hypothesis inline review comments (
b167e4e,f406fda)Adds Hypothesis for inline, text-anchored review comments on the live site — an off-the-shelf alternative to pasting page snippets into chat.
HYPOTHESIS_GROUPrepository variable is set, scoping the client to a private group so only logged-in group members see/post comments; the public sees nothing.src/_data/site.js(comments, env-driven);base.njkconditionally emits the script + group config. Hardened so comments require both the flag and a group — never public/groupless by accident.2. Home-page editorial pass (
17c762b)Applies review feedback left on the home page:
/supply-chain/; one line to relist).3. Why VCALM — benefit-led format section (
5789cb8)Reframes section 5 from feature-led to benefit-led per review:
Verification
npx @11ty/eleventybuilds clean (23 files)./supply-chain/still builds.Notes
🤖 Generated with Claude Code