Brief · 2026
Designing a Durable Research Publication
A practical architecture for credible, readable, and maintainable web-native reports.
Executive summary
A research website should behave like a publication, not a chronological blog. Durable URLs, explicit revisions, structured citations, restrained typography, and accessible documents matter more than novelty.
Key findings
- The report is the primary unit. Every report receives a stable URL, publication status, and suggested citation.
- Evidence remains inspectable. Sources should be linked near the claims they support.
- Reading quality is infrastructure. Strong contrast, useful headings, and low JavaScript improve comprehension.
- Revision is a feature. Substantive updates should be dated instead of silently replacing the record.
Publication architecture
The personal site establishes identity. The research subdomain is the canonical home for reports, briefs, topic indexes, and future datasets.
| Layer | Responsibility |
|---|---|
| GitHub | Source and review history |
| Astro | Static rendering and templates |
| Netlify | Preview and production deployment |
| Domain | Stable canonical identity |
Editorial standard
Every report should identify its question, methods, sources, limitations, and confidence. Facts, interpretation, and speculation should remain distinct.
The goal is not to remove uncertainty. It is to make uncertainty legible.
Accessibility and performance
The publication targets WCAG 2.2 AA. Pages are statically rendered, keyboard accessible, responsive, and usable without client-side JavaScript.
Limitations
This initial brief demonstrates the publication template rather than presenting original empirical research. Search, structured bibliographies, and PDF generation are planned extensions.
Revision history
- July 11, 2026: Initial publication architecture and report template.
Suggested citation
Jiang, Jun. “Designing a Durable Research Publication.” Jun Jiang Research, 2026.