Research page template
When to use
Section titled “When to use”- Shelf:
learn/research/<topic>/ kind: research or synthesis note- Diátaxis mode: explanation / synthesis (not a tutorial)
- Readers served: future-you and agents needing evidence-backed decisions
Design rationale
Section titled “Design rationale”- Research pages answer a question — lead with the question, not background fluff (Good Docs research patterns).
- Method + sources section — reproducibility for agents and humans (Diátaxis — document your evidence trail).
- Findings before implications — separate observation from recommendation to avoid cherry-picking (evidence-based writing).
- ## Sources mandatory on research pages — both this template file and pages authored from it should end with citations when claims are external.
Copy-paste skeleton
Section titled “Copy-paste skeleton”---title: "<Research question>"description: One sentence — what we investigated and the headline answer.kind: researchstatus: drafttags: [research, topic]---
## Question
<Single clear research question.>
## Method
<What we searched, read, or compared — 3–5 bullets.>
## Findings
<Neutral observations — tables welcome.>
## Implications for ZajLibrary
<What we should do differently — links to playbooks/guides.>
## Sources
- [Title](url) — what it contributedAnti-patterns
Section titled “Anti-patterns”- Do not paste vendor dumps verbatim — synthesize (see repo-root
AGENTS.mdinbox policy). - Do not ship research without Sources when citing external claims.
Worked example
Section titled “Worked example”- Research hub (stub)
Sources
Section titled “Sources”- Diátaxis — Explanation — research synthesizes understanding, not procedures.
- Good Docs Project — structured doc types including research-oriented templates.
- Google developer documentation style guide — separate findings from recommendations.
- Writing style → Doc-type spines