research-package RP-2026-001
Reusable Research Publishing System
Build a reusable publishing system that turns research Markdown into a searchable static site.
Executive Summary
Visual Engineering needs a publishing workflow that preserves Markdown as the canonical source while generating a readable, searchable website.
Repository Context
The repository began empty apart from a prompt. That makes reusability easier to enforce because there is no legacy rendering stack to preserve.
Current Understanding
The system should separate content normalization, relationship modeling, and page rendering so that future repositories can reuse the same package through configuration.
Key Discoveries
- Static generation is sufficient for the current repository shape.
- Search requires two artifacts: public catalog JSON and a full-text index.
- Relationship resolution is stronger when stable identifiers outrank filenames.
Open Questions
- How strict should CI become once more repositories adopt the schema?
- Which additional artifact types need first-class layouts?