chore: changes for jaspr

.claude/settings.json

@@ -0,0 +1,57 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(lsof -ti:3000)",
+      "Bash(node capture.mjs)",
+      "Bash(node compare.mjs)",
+      "Bash(open /Users/john/projects/very_good_workflows/tools/visual-compare/screenshots/report.html)",
+      "Bash(node /private/tmp/check-h1.mjs)",
+      "Bash(node check-h1.mjs)",
+      "Bash(lsof -ti:4000)",
+      "Bash(npx serve build/jaspr -l 4000)",
+      "Bash(curl -s -o /dev/null -w \"%{http_code}\" http://localhost:4000/docs/overview/)",
+      "Bash(node capture.mjs --jaspr-only)",
+      "Bash(node inspect-dark.mjs)",
+      "Bash(node inspect-spr.mjs)",
+      "Bash(node inspect-width.mjs)",
+      "Bash(dart run jaspr_cli:jaspr build)",
+      "Bash(pkill -f build_daemon)",
+      "Bash(pkill -f dart.*build_runner)",
+      "Bash(curl -s http://localhost:4000/docs/overview/)",
+      "mcp__plugin_wingspan_dart__dart_fix",
+      "Bash(node capture.js --url=\"http://localhost:4000/docs/workflows\" --name=\"docs-workflows\" --width=1200)",
+      "Bash(node capture.mjs --url=\"http://localhost:3000/docs/workflows\" --name=\"docs-workflows\" --width=1200)",
+      "Bash(node capture.mjs --url=\"http://localhost:4000/docs/workflows\" --name=\"docs-workflows\" --width=1200)",
+      "mcp__plugin_wingspan_dart__hover",
+      "Bash(jaspr serve --port 4000)",
+      "Bash(curl -s -o /dev/null -w \"%{http_code}\" http://localhost:4000/docs/workflows)",
+      "Bash(node /tmp/measure-layout.mjs)",
+      "Bash(npm run capture:jaspr)",
+      "Bash(npm run compare)",
+      "Bash(node analyze-diffs.mjs)",
+      "Bash(ls /Users/john/projects/very_good_workflows/tools/visual-compare/screenshots/diff-*.png)",
+      "Bash(curl -s -o /dev/null -w \"%{http_code}\" http://localhost:4000/)",
+      "Bash(node measure.mjs)",
+      "Bash(node measure-home.mjs)",
+      "Bash(node measure-buttons.mjs)",
+      "Read(//Users/john/.pub-cache/hosted/pub.dev/jaspr_content-0.5.0/lib/components/**)",
+      "Bash(curl -s http://localhost:4000/)",
+      "Read(//Users/john/.pub-cache/hosted/pub.dev/jaspr_content-0.5.0/**)",
+      "Read(//Users/john/.pub-cache/hosted/pub.dev/jaspr-0.22.3/lib/src/dom/**)",
+      "Read(//Users/john/.pub-cache/hosted/pub.dev/jaspr-0.22.3/lib/**)",
+      "Bash(grep -n 'final class li\\\\|final class ul' /Users/john/.pub-cache/hosted/pub.dev/jaspr-0.22.3/lib/src/dom/html/*.dart)",
+      "Bash(while read hash msg)",
+      "Bash(do echo \"=== $msg ===\")",
+      "Bash(git diff-tree --no-commit-id --name-only -r \"$hash\")",
+      "Bash(done)",
+      "Bash(python3 -c \"import sys,json; h=json.load\\(sys.stdin\\); [print\\(f\"\"{e[''timestamp''][:16]}  {e[''parityScore'']}%\"\"\\) for e in h]\")",
+      "Bash(node -e \":*)",
+      "Bash(xargs kill -9)",
+      "Bash(lsof -ti:5467)",
+      "Bash(pkill -9 -f 'dart.*build_daemon')",
+      "Bash(python3 -m json.tool)",
+      "Bash(ls /Users/john/projects/very_good_workflows/tools/visual-compare/screenshots/parity*)",
+      "Bash(ls /Users/john/projects/very_good_workflows/tools/visual-compare/parity*)"
+    ]
+  }
+}

.github/cspell.json

@@ -15,28 +15,46 @@
     }
   ],
   "useGitignore": true,
+  "ignorePaths": [
+    "**/*.tmLanguage.json"
+  ],
   "words": [
     "amannn",
     "APPDATA",
     "brickhub",
+    "Consolas",
     "creatordate",
     "creds",
     "clsx",
     "Csvg",
     "Contador",
     "endtemplate",
+    "evenodd",
+    "flexbox",
+    "frontmatter",
     "Infima",
+    "jaspr",
     "linecap",
+    "linejoin",
     "localizable",
+    "Menlo",
     "mostrado",
     "noopener",
+    "noreferrer",
+    "Noto",
+    "Octicon",
     "página",
     "peaceiris",
+    "Scrollspy",
+    "Segoe",
     "srealmoreno",
     "retag",
     "Texto",
     "typecheck",
+    "unhighlighted",
+    "viewports",
     "webfactory",
-    "xlink"
+    "xlink",
+    "zoomable"
   ]
 }

JASPR_MIGRATION.md

@@ -0,0 +1,70 @@
+# Migrating from Docusaurus to Jaspr
+
+## 1. Scaffold the Jaspr project
+
+```bash
+dart pub global activate jaspr_cli
+jaspr create --template=docs site_jaspr
+```
+
+This gives you a Jaspr static site pre-configured with `jaspr_content`, which includes a `DocsLayout` with sidebar, header, dark/light mode, markdown parsing, and syntax highlighting out of the box.
+
+## 2. Migrate your content
+
+Your current docs are 10 Markdown files in `site/docs/` with YAML frontmatter (`sidebar_position`, `title`, `description`). These can largely be copied over as-is -- `jaspr_content` uses a `FilesystemLoader` that reads `.md` files from a content directory and supports frontmatter.
+
+The current sidebar is auto-generated from the filesystem in Docusaurus. In Jaspr, the sidebar is defined explicitly in Dart code:
+
+```dart
+sidebar: Sidebar(groups: [
+  SidebarGroup(links: [
+    SidebarLink(text: 'Overview', href: '/'),
+  ]),
+  SidebarGroup(title: 'Workflows', links: [
+    SidebarLink(text: 'Dart Package', href: '/workflows/dart_package'),
+    SidebarLink(text: 'Flutter Package', href: '/workflows/flutter_package'),
+    // ... etc
+  ]),
+]),
+```
+
+## 3. Recreate the custom homepage
+
+The current homepage (`site/src/pages/index.tsx`) is a custom React component with a hero banner, CTA button, and blog section. In Jaspr, you'd build this as a `StatelessComponent` using Jaspr's HTML element functions (`div`, `a`, `img`, etc.) with typed `Styles` for CSS.
+
+## 4. Migrate theming
+
+The custom CSS (`site/src/css/custom.css`) defines brand colors, Poppins font, and dark mode overrides. In Jaspr, theming is done via `ContentTheme`:
+
+```dart
+theme: ContentTheme(
+  primary: ThemeColor(Color('#2a48df'), dark: Color('#66fbd1')),
+  background: ThemeColor(Colors.white, dark: Color('#0b0d0e')),
+),
+```
+
+## 5. Update the deployment workflow
+
+Replace the Node/Docusaurus build steps in `.github/workflows/site_deploy.yaml` with Dart/Jaspr:
+
+```yaml
+- uses: dart-lang/setup-dart@v1
+- run: dart pub global activate jaspr_cli
+- run: jaspr build
+# Output goes to build/jaspr/ instead of site/build/
+```
+
+## Key differences to be aware of
+
+| Aspect | Docusaurus (current) | Jaspr |
+|---|---|---|
+| Sidebar | Auto-generated from filesystem | Manual definition in Dart |
+| Custom pages | React/TSX components | Dart `StatelessComponent` |
+| Styling | CSS/CSS Modules | Typed `Styles` in Dart + optional CSS |
+| Markdown extensions | MDX (JSX in Markdown) | Custom components registered in Dart |
+| Search | Algolia integration available | No built-in search |
+| Docs versioning | Built-in | Not available |
+
+## Tradeoffs
+
+The main benefit is staying entirely within the Dart ecosystem. The main costs are losing Docusaurus's auto-generated sidebar, built-in search integration, and the broader plugin ecosystem. The site is relatively straightforward (10 doc pages, one custom homepage), so the migration scope is manageable.

site_jaspr/.gitignore

@@ -0,0 +1,30 @@
+# Files and directories created by pub.
+**/doc/api/
+.dart_tool/
+.packages
+
+# Conventional directory for build output.
+/build/
+
+# Miscellaneous
+*.class
+*.log
+*.pyc
+*.swp
+.DS_Store
+.atom/
+.buildlog/
+.history
+.svn/
+migrate_working_dir/
+
+# IntelliJ related
+*.iml
+*.ipr
+*.iws
+.idea/
+
+# The .vscode folder contains launch configuration and tasks you configure in
+# VS Code which you may wish to be included in version control, so this line
+# is commented out by default.
+#.vscode/

site_jaspr/README.md

@@ -0,0 +1,15 @@
+# site_jaspr
+
+A documentation site built with Jaspr
+
+## Running the project
+
+Run your project using `jaspr serve`.
+
+The development server will be available on `http://localhost:8080`.
+
+## Building the project
+
+Build your project using `jaspr build`.
+
+The output will be located inside the `build/jaspr/` directory.

site_jaspr/analysis_options.yaml

@@ -0,0 +1,46 @@
+# This file configures the static analysis results for your project (errors,
+# warnings, and lints).
+#
+# This enables the 'recommended' set of lints from `package:lints`.
+# This set helps identify many issues that may lead to problems when running
+# or consuming Dart code, and enforces writing Dart using a single, idiomatic
+# style and format.
+#
+# If you want a smaller set of lints you can change this to specify
+# 'package:lints/core.yaml'. These are just the most critical lints
+# (the recommended set includes the core lints).
+# The core lints are also what is used by pub.dev for scoring packages.
+
+include: package:lints/recommended.yaml
+
+analyzer:
+#   exclude:
+#     - path/to/excluded/files/**
+
+# Jaspr has a custom analyzer plugin 'jaspr_lints', which is enabled here.
+#
+# You can toggle Jaspr specific lint rules in the 'diagnostics' section below.
+plugins:
+  jaspr_lints:
+    version: ^0.6.0
+    diagnostics:
+      prefer_html_components: true
+      sort_children_last: true
+      styles_ordering: true
+
+# Uncomment the following section to enable or disable additional rules.
+
+# linter:
+#   rules:
+#     camel_case_types: true
+
+# For more information about the core and recommended set of lints, see
+# https://dart.dev/go/core-lints
+
+formatter:
+  # Change this to your preferred line length.
+  page_width: 120
+  trailing_commas: preserve
+
+# For additional information about configuring this file, see
+# https://dart.dev/guides/language/analysis-options

site_jaspr/content/_data/links.yaml

@@ -0,0 +1,3 @@
+website: https://verygood.ventures
+devTools: https://developer.vgv.dev
+github: https://github.com/VeryGoodOpenSource/very_good_workflows

site_jaspr/content/_data/site.yaml

@@ -0,0 +1,3 @@
+# Site Configuration
+titleBase: Very Good Workflows
+favicon: favicon.ico

site_jaspr/content/docs/category/workflows.md

@@ -0,0 +1,8 @@
+---
+title: "Workflows"
+---
+
+<meta http-equiv="refresh" content="0; url=/docs/workflows">
+<link rel="canonical" href="/docs/workflows">
+
+If you are not redirected automatically, [click here](/docs/workflows).

site_jaspr/content/docs/overview.md

@@ -0,0 +1,45 @@
+---
+title: Overview
+description: A collection of reusable GitHub workflows used at Very Good Ventures.
+image: /images/meta/open-graph.png
+---
+
+# Overview
+
+[GitHub workflows][github_workflows_link] are configurable, automated processes that can run at various points during the development process. For example, a workflow can run when a pull request is created or updated to perform various code quality checks before allowing the changes to be merged.
+
+Very Good Workflows is a collection of workflows that we use at VGV to run automated checks in our CI pipelines. While built by VGV to be used internally, they can be used by anyone.
+
+## Quick Start 🚀
+
+To get started, add Very Good Workflows to an existing GitHub workflow:
+
+```yaml
+# A reusable workflow for Dart packages
+uses: VeryGoodOpenSource/very_good_workflows/.github/workflows/dart_package.yml@v1
+
+# A reusable workflow for Flutter packages
+uses: VeryGoodOpenSource/very_good_workflows/.github/workflows/flutter_package.yml@v1
+
+# A reusable workflow for ensuring commits are semantic
+uses: VeryGoodOpenSource/very_good_workflows/.github/workflows/semantic_pull_request.yml@v1
+
+# A reusable workflow for verifying package scores on pub.dev
+uses: VeryGoodOpenSource/very_good_workflows/.github/workflows/pana.yml@v1
+
+# A reusable workflow for running a spell check
+uses: VeryGoodOpenSource/very_good_workflows/.github/workflows/spell_check.yml@v1
+
+# A reusable workflow for publishing Flutter packages
+uses: VeryGoodOpenSource/very_good_workflows/.github/workflows/flutter_pub_publish.yml@v1
+
+# A reusable workflow for publishing Dart packages
+uses: VeryGoodOpenSource/very_good_workflows/.github/workflows/dart_pub_publish.yml@v1
+
+# A reusable workflow for publishing Mason bricks
+uses: VeryGoodOpenSource/very_good_workflows/.github/workflows/mason_publish.yml@v1
+
+```
+
+[github_workflows_link]: https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions
+[very_good_ventures_link]: https://verygood.ventures

site_jaspr/content/docs/workflows.md

@@ -0,0 +1,47 @@
+---
+title: "Workflows"
+description: "Learn about all of the workflows that Very Good Workflows supports."
+---
+
+# Workflows 🦄
+
+Learn about all of the workflows that Very Good Workflows supports.
+
+<div class="workflow-cards">
+  <a class="workflow-card" href="/docs/workflows/dart_package">
+    <h3>📄 Dart Package</h3>
+    <p>This workflow runs helpful checks on a Dart package according to the steps below. As with any workflow, it can be customized.</p>
+  </a>
+  <a class="workflow-card" href="/docs/workflows/dart_pub_publish">
+    <h3>📄 Dart Pub Publish</h3>
+    <p>We use this workflow to publish a Dart package to pub.dev.</p>
+  </a>
+  <a class="workflow-card" href="/docs/workflows/flutter_package">
+    <h3>📄 Flutter Package</h3>
+    <p>This workflow runs helpful checks on a Flutter package according to the steps below. As with any workflow, it can be customized.</p>
+  </a>
+  <a class="workflow-card" href="/docs/workflows/flutter_pub_publish">
+    <h3>📄 Flutter Pub Publish</h3>
+    <p>We use this workflow to publish a Flutter package to pub.dev.</p>
+  </a>
+  <a class="workflow-card" href="/docs/workflows/license_check">
+    <h3>📄 License Check</h3>
+    <p>At VGV, we keep track of the rights and restrictions external dependencies might impose on Dart or Flutter projects.</p>
+  </a>
+  <a class="workflow-card" href="/docs/workflows/mason_publish">
+    <h3>📄 Mason Publish</h3>
+    <p>We use this workflow to publish a brick to brickhub.dev.</p>
+  </a>
+  <a class="workflow-card" href="/docs/workflows/pana">
+    <h3>📄 Pana</h3>
+    <p>We use the Dart tool pana to validate that your pub score will be the max possible score before publishing a package to pub.dev.</p>
+  </a>
+  <a class="workflow-card" href="/docs/workflows/semantic_pull_request">
+    <h3>📄 Semantic Pull Request</h3>
+    <p>At VGV, we use conventional commits. This way, our commit history is clean and useful when we squash and merge — we can easily see the type and brief description of each PR.</p>
+  </a>
+  <a class="workflow-card" href="/docs/workflows/spell_check">
+    <h3>📄 Spell Check</h3>
+    <p>We use cspell for basic spell check on our projects.</p>
+  </a>
+</div>