[Website][Data] Markdown-to-site static content pipeline

[web2solutions]

Parent epic: #124
Story points: 8

Objective
Implement static content ingestion pipeline using Jumentix markdown docs as source of truth.

Scope

• Build parser/loader for selected MD files.
• Normalize frontmatter/metadata strategy for website consumption.
• Add content indexing for pages/sections/components.
• Provide fallback behavior for missing metadata.

Acceptance Criteria

• Website pages consume MD-driven data.
• Build is deterministic and static.
• Content mapping is documented for editors.

[web2solutions]

Progress update (implementation in workspace):

• Added source mapping contract:
  • apps/jumentix-website/config/content-sources.json
• Implemented static content generator:
  • apps/jumentix-website/scripts/sync-markdown-content.mjs
• Generated MDX output pages from repository markdown docs:
  • apps/jumentix-website/content/jumentix/*.mdx
  • apps/jumentix-website/content/jumentix/_meta.ts
• Wired auto-sync into website scripts:
  • content:sync
  • predev
  • prebuild
• Documented pipeline:
  • apps/jumentix-website/documentation/CONTENT-PIPELINE.md

Fallback behavior implemented:

• Missing title -> inferred from slug
• Missing description -> derived from title
• Missing source file -> build-safe generated page with "source file not found" content

Traceability status:

• PR: pending (will be attached before closure)
• Commit evidence: pending (will be attached before closure)

[web2solutions]

Completed.\n\nEvidence:\n- Markdown-to-site static ingestion pipeline implemented in .\n- Source mapping centralized in .\n- Deterministic generated content in .\n\nDelivery references:\n- PR: https://github.com/web2solutions/aaa-typescript-boilerplate/pull/132\n- Commits: 53895fa, b5cd96d

[web2solutions]

Evidence update: implemented and tracked via PR #132 (commits 53895fa and b5cd96d where applicable). Source references are available in the PR files list and linked docs pages.