Release notes / changelog bridge

This help centre explains how to use dFlow. Release notes and changelogs summarise what shipped in each version. Use both: one for tasks and mental models, the other for “what is new this week.”

Public changelog (marketing site)Copy Anchor Link

Shipped product updates are summarised on the public site:

• dFlow changelog: high-level feature and fix announcements.

That page is aimed at all visitors; it may not list every internal flag or Payload migration name.

This documentation packageCopy Anchor Link

• packages/docs/manifest.json versions the customer doc set (version bumps when structure or pages change materially). It is not the same as the application semver.
• The marketing changelog is the right place for time-ordered headlines.
• Databases and Templates are first-class sidebar sections. Their manifest.json owner fields (parallel-databases-writer, parallel-templates-writer) mark content ownership; navigation order still follows IA.md and root meta.json so readers see one coherent tree.
• Product model background for Applications vs legacy Projects lives under Product model changes; shipped feature headlines stay on dFlow changelog.

RelatedCopy Anchor Link

• What changed in dFlow: hub for model and docs changes.
• Documentation migration notes: legacy help centre and this package.