Merge pull request #500 from webstackdev/infrastructure/add-check-links-integration

Infrastructure/add check links integration

Author: webstackdev

.cache/pages.json

@@ -25,18 +25,25 @@
     "privacy": ["my-data"]
   },
   {
-    "services": ["create-custom-font-sets", "overview"]
+    "services": ["consulting", "overview", "web-development"]
   },
   {
     "tags": [
       "apiDesign",
+      "aws",
+      "ci",
       "cms",
       "code",
       "crm",
+      "databaseNormalization",
+      "deployment",
+      "devPortals",
       "graphql",
       "online-learning",
       "react",
+      "restful",
       "services",
+      "sqlOptimization",
       "typescript"
     ]
   }

.github/instructions/general.instructions.md

@@ -19,6 +19,7 @@ applyTo: "**"
 - Always create TypeScript files, not JavaScript files.
 - Prefer destructured imports over namespace imports when importing specific functions from modules (e.g., `import { resolve } from 'path'` instead of `import * as path from 'path'`).
 - Do not access nanostore observables (e.g., `$consent`) directly from components; expose helper/action methods in `@components/scripts/store` and import those instead.
+- Preact exists only for the Markdown E2E harness under `src/lib/markdown/__tests__/e2e`; all production UI components must use Lit web components instead of Preact.
 
 # Code Organization and Directory Structure
 

.github/workflows/test.yml

@@ -79,11 +79,9 @@ jobs:
       - name: Install dependencies
         run: npm ci --legacy-peer-deps
 
-      - name: Sync Astro types
-        run: npm run sync
-
-      - name: Run Astro check
-        run: npm run check
+      # Astro build runs sync, check, and integrations including verify links
+      - name: Verify green build
+        run: npm run build
 
       - name: Run unit tests (Vitest — coverage with GitHub Actions reporter)
         id: vitest

.husky/pre-commit

@@ -18,6 +18,9 @@ fi
 # Run lint suite (includes TypeScript check + ESLint + Stylelint + JSON formatting)
 npm run lint
 
+# Make sure types are sync'ed before commit
+npm run sync
+
 # Verify branch naming convention
 .husky/scripts/check-branch-name.sh
 

.vscode/settings.json

@@ -31,11 +31,14 @@
     "Fedibird",
     "Fediverse",
     "finnadie",
+    "firko",
     "Flink",
     "FNAME",
     "fosstodon",
     "FOUC",
+    "fprintf",
     "glidejs",
+    "gomodule",
     "GSAP",
     "hocho",
     "Hudi",
@@ -76,7 +79,12 @@
     "pleroma",
     "Poslovski",
     "Postg",
+    "postgrest",
+    "psql",
+    "qpart",
+    "qparts",
     "Qualys",
+    "redigo",
     "registrator",
     "repost",
     "reposts",
@@ -103,11 +111,13 @@
     "tsdoc",
     "tseslint",
     "tshirt",
+    "Turso",
     "tydata",
     "unspaced",
     "unstub",
     "uppy",
     "uuidv",
+    "valyala",
     "Veeam",
     "vercel",
     "virt",

_TODO.md

@@ -1,6 +1,16 @@
 <!-- markdownlint-disable-file -->
 # TODO
 
+## Fix E2E mock container test runner, migrate DB providers
+
+Refactor from using Suprabase and Upstash to using Astro DB + Turso
+
+[Astro DB](https://docs.astro.build/en/guides/astro-db/)
+
+## Mobile Social Shares
+
+See the example image in Social Shares.
+
 ## Performance
 
 Implement mitigations in test/e2e/specs/07-performance/PERFORMANCE.md
@@ -38,10 +48,6 @@ Lunr is a JS search library using an inverted index. Client-side search for stat
 
 Right now we're using string literals to define HTML email templates for site mails. We should use Nunjucks with the rule-checking for valid CSS in HTML emails like we have in the corporate email footer repo.
 
-## @TODO: Provide button to turn off animation in Hero
-
-"Scaling/zooming animations are problematic for accessibility, as they are a common trigger for certain types of migraine. If you need to include such animations on your website, you should provide a control to allow users to turn off animations, preferably site-wide.  Also, consider making use of the prefers-reduced-motion media feature — use it to write a media query that will turn off animations if the user has reduced animation specified in their system preferences. "
-
 ## Color vars
 
 brand primary:    #001733
@@ -101,12 +107,35 @@ cat.structure: Rules related to the document's overall structure, like the prope
 cat.tables: Rules for data tables, including headers and associations.
 cat.text-alternatives: Rules for ensuring that text alternatives are provided for non-text content, such as images.
 
+## Privacy policy errors
+
+fatal: /home/kevin/Repos/Webstack: '/home/kevin/Repos/Webstack' is outside repository at '/home/kevin/Repos/Webstack Builders/Corporate Website/astro.webstackbuilders.com'
+
+[privacy-policy-version] Could not get privacy policy version from git: Command failed: git log -1 --format=%cd --date=format:%Y-%m-%d -- /home/kevin/Repos/Webstack Builders/Corporate Website/astro.webstackbuilders.com/src/pages/privacy/index.astro
+
+fatal: /home/kevin/Repos/Webstack: '/home/kevin/Repos/Webstack' is outside repository at '/home/kevin/Repos/Webstack Builders/Corporate Website/astro.webstackbuilders.com'
+
+⚠️  Privacy policy version fallback applied: 2025-12-08
+
 ## @TODO: Add Check HTML Links to test workflow
 
 npm i -D check-html-links
 npx check-html-links _site
 `https://github.com/modernweb-dev/rocket/tree/main/packages/check-html-links`
 
+22:38:43 [ERROR] [astro-link-validator] ❌ Found 2 broken links:
+\n📄 index.html:
+  🔗 /services/web-development
+    File not found: services/web-development
+    Text: "Improve Your Product"
+  🔗 /services/consulting
+    File not found: services/consulting
+    Text: "Start from scratch"
+
+## Tags
+
+Can we add a markdown page to explain what each tag is, and use those pages instead of src/content/_tagList.ts to define the tags available?
+
 ## Social Media Preview Cards
 
 Looking at the social-card endpoint implementation, it's designed to work with third-party screenshot services, not the social networks themselves.

astro.config.ts

@@ -1,5 +1,6 @@
 import AstroPWA from '@vite-pwa/astro'
 import icon from 'astro-icon'
+import linkValidator from 'astro-link-validator'
 import lit from '@semantic-ui/astro-lit'
 import mdx from '@astrojs/mdx'
 import sentry from '@sentry/astro'
@@ -8,6 +9,7 @@ import tailwindcss from '@tailwindcss/vite'
 import vercelStatic from '@astrojs/vercel'
 import vtbot from 'astro-vtbot'
 import { defineConfig } from 'astro/config'
+import type { AstroUserConfig } from 'astro'
 import { fileURLToPath } from 'node:url'
 import type { PluginOption } from 'vite'
 /**
@@ -22,6 +24,7 @@ import {
   environmentalVariablesConfig,
   getSentryAuthToken,
   getSiteUrl,
+  isGitHub,
   isUnitTest,
   isVercel,
   markdownConfig,
@@ -70,6 +73,13 @@ const standardIntegrations = [
       exclude: ['downloads', 'social-shares', '/articles/demo', 'testing'],
     }),
   }),
+  /** Validate links in built site output on astro:build:done integration hook */
+  linkValidator({
+    checkExternal: isGitHub(),
+    failOnBrokenLinks: false,
+    verbose: true,
+  }),
+  /** Integration to write pages.json after build so E2E tests can discover what pages exist */
   pagesJsonWriter(),
   /** Debugging tools for Astro View Transition API */
   vtbot(),
@@ -81,6 +91,7 @@ export default defineConfig({
     enabled: false,
   },
   env: environmentalVariablesConfig,
+  markdown: markdownConfig as AstroUserConfig['markdown'],
   /**
    * Astro sets substantial Vite config internally in the framework. When you use Vitest
    * in an Astro project, you use Astro's getViteConfig helper to get the resolved internal