Foundation

Shared wiki architecture

Use this guide before adding project-specific pages or workflow status surfaces.

Folders

  • assets/css/main.css owns design tokens, responsive layout, utilities, components, and theme variables.
  • assets/js/main.js owns shared header, sidebar, breadcrumbs, footer, theme handling, navigation behavior, generated status rendering, and search hooks.
  • data/workspace-status.json is the committed status feed consumed by the homepage, AI Workspace, and timeline.
  • projects/ holds project entry points and Markdown source snapshots behind rendered HTML pages.
  • docs/ holds foundation and contribution guidance.

Page pattern

Every HTML page should include the shared stylesheet, module script, skip link, header slot, sidebar slot, breadcrumbs slot, content container, and footer slot. Keep page content focused on the document body while shared chrome is rendered by JavaScript.

Component rules

  • Prefer existing classes such as panel, section-stack, widget-grid, button, and utility classes before adding custom CSS.
  • Expose new reusable behavior as small functions in assets/js/main.js or future focused modules.
  • Preserve keyboard access, visible focus states, semantic headings, landmarks, and reduced duplication.
  • Use CSS variables for color, spacing, radius, and shadow changes so dark theme support stays consistent.