ssr-pipeline

Trace or modify Madoc TS server-side rendering for site and admin. Use when changing SSR output, template injection, dev HMR SSR wiring, or debugging SSR redirects and template tokens in services/madoc-ts.

Aller à l'installation

Dépôt: digirati-co-uk/madoc-platform
Dernière activité de la source: 5 février 2026 à 21:05
Langue détectée de SKILL.md: anglais
Étoiles: 57
Forks: 15

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

npx skills add https://github.com/digirati-co-uk/madoc-platform --skill ssr-pipeline

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Explorateur de fichiers

2 fichiers

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’installation

crowdsourcing-task-review-workflow

Understand and modify the full Madoc TS crowdsourcing contribution and review pipeline. Use when changing claim creation rules, crowdsourcing-task and crowdsourcing-review lifecycle behavior, reviewer assignment policy, or project settings that control submission/review flow in services/madoc-ts.

2026-05-07

frontend-site

Work on Madoc TS site UI structure, React routes, and site-specific SSR behaviors. Use when adding or updating site pages, loaders, or site theme usage in services/madoc-ts.

2026-04-14

madoc-docker-ops

Build, run, and debug the Madoc Docker/compose stack with the Docker daemon already running, including rebuilding images, starting/stopping services, inspecting containers/images, and using pm2 inside the madoc-ts container (server/queue/scheduler/auth) plus frontend rebuilds for volume-mounted assets.

2026-04-08

Tout voir dans ce dépôt

name	ssr-pipeline
description	Trace or modify Madoc TS server-side rendering for site and admin. Use when changing SSR output, template injection, dev HMR SSR wiring, or debugging SSR redirects and template tokens in services/madoc-ts.

SSR Pipeline (Madoc TS)

Overview

Explain how server-side rendering is performed for site and admin, how SSR output is injected into HTML templates, and how dev-mode HMR SSR output is constructed.

Key Entry Points

Site SSR handler: services/madoc-ts/src/routes/frontend/site-frontend.ts
Admin SSR handler: services/madoc-ts/src/routes/frontend/admin-frontend.ts
Site template: services/madoc-ts/src/site.html
Admin template: services/madoc-ts/src/admin.html
Client entrypoints referenced in templates:
- services/madoc-ts/src/frontend/site/client.ts
- services/madoc-ts/src/frontend/admin/client.tsx

SSR Flow Summary (Based on Source)

Both site and admin handlers set context.staticPage to an async renderer.
Each renderer calls a corresponding render* function:
- Site: renderSite from src/frontend/site/server
- Admin: renderAdmin from src/frontend/admin/server
The render result includes body, head, htmlAttributes, and bodyAttributes.
If result.type === 'redirect', the handler returns a redirect (status result.status || 307) or a 404 if no to is provided.
In NODE_ENV === 'development', HTML is built inline with Vite HMR scripts and a dynamic host-based dev URL (port 3088).
In non-dev, context.siteTemplate or context.adminTemplate is used, with token replacement:
-  replaced by result.body
-  replaced by result.head
- <html> and <body> tags are replaced to include attributes from SSR output.

Quick Start Workflow

Inspect site-frontend.ts and admin-frontend.ts to see how context.staticPage is set and how SSR results are injected.
Confirm template token usage in site.html and admin.html.
For dev SSR, verify HMR and client script injection for the correct entrypoints:
- Site: /src/frontend/site/client.ts
- Admin: /src/frontend/admin/client.tsx
If changing SSR output shape, ensure callers handle result.type === 'redirect' and result.body/head expectations.

Development Mode Details

Dev HTML includes @react-refresh and a viteProtocol derived from TLS certs at /home/node/app/openssl-certs.
Hostname is taken from context.request.hostname.
Site adds a stylesheet link to src/frontend/site/index.css in dev mode.

Common Tasks

Update SSR head/body injection
Debug SSR redirect behavior
Add SSR-injected assets (ensure matching template tokens)
Troubleshoot dev HMR SSR boot failures

Pitfalls

Missing or renamed template tokens (, )
Mismatch between SSR output and template replacement
HMR dev URLs breaking on custom hostnames or protocol mismatch

Suggested Checks

One request to a site page (SSR HTML contains result.head and result.body)
One request to an admin page (SSR HTML contains result.head and result.body)
In dev, confirm the HMR preamble loads and the client entrypoints are correct

ssr-pipeline

Informations de source

Options d'installation

Vérifiez les fichiers source

Plus depuis ce dépôt

Plus depuis ce dépôt

SSR Pipeline (Madoc TS)

Overview

Key Entry Points

SSR Flow Summary (Based on Source)

Quick Start Workflow

Development Mode Details

Common Tasks

Pitfalls

Suggested Checks

SSR Pipeline (Madoc TS)

Overview

Key Entry Points

SSR Flow Summary (Based on Source)

Quick Start Workflow

Development Mode Details

Common Tasks

Pitfalls

Suggested Checks