Core reference layer published
Core FKRP guides, audience entry points, and the initial public reference architecture went live.
Updates
Updates and maintenance now live here.
This page is the public changelog and maintenance model for FKRP Reference. It explains what changed, how often major content types are reviewed, and how new work moves into the backlog.
Recent updates
Major public-facing changes
Evidence library and study tracking added
Paper summaries, trial and registry tracking, and structured evidence detail pages were added to the public site.
Search, glossary, and launch-readiness checks added
Shared taxonomy, glossary pages, site-wide search, related-content modules, metadata updates, and automated validation checks were added.
Operating model
How the site stays current
Review cadence
Each major content type has an expected refresh window instead of ad hoc updates.
Source-first updates
Major revisions should start from published sources, registry records, or formal guidance, not memory alone.
Public changelog
Material updates are summarized here so changes are visible instead of silent.
Backlog triage
Accuracy and staleness risks are prioritized ahead of expansion or growth experiments.
Review cadence
Expected cadence by content type
Core guides
Formal review every 6 months, with earlier updates when major terminology, care framing, or guidance changes.
Papers and natural history summaries
Quarterly review, or sooner if a paper changes how phenotype, monitoring, or evidence limitations should be described.
Trials and registry records
Monthly status check against the source record, with same-week updates when recruitment or status materially changes.
Glossary and discovery pages
Review every 6 months and whenever taxonomy, search behavior, or naming conventions materially shift.
How outdated evidence is handled
- If a page passes its expected review window, it should move to the top of the maintenance backlog.
- If a trial, registry, or key evidence page changes materially, the update should be reflected in the source page and summarized here.
- Review dates should not be silently reset without a real source check and editorial pass.
Backlog process
How new work enters the queue
- Capture the change as an issue with the source, affected routes, and the reason it matters.
- Triage it into a priority tier before new writing starts.
- Update the relevant page or collection entry, then add a brief public note here if the change is material.
- Use the existing build validator and smoke tests before merging.
P1 Maintain accuracy
Review-due pages, trial-status changes, broken links, and any risk of outdated or misleading evidence.
P2 Expand coverage
New papers, new glossary terms, additional resources, and deeper summaries that fit the current structure.
P3 Growth work
Multilingual support, contributor workflows, community submissions, and analytics-informed UX improvements.