Skip to content
← Documentation Internal notes

Internal seed and migration notes

How baseline seeds, migrations and platform changelog entries are used to reproduce ExtensionFlow state without manual database edits.

01

Чистые установки

New environments should receive current platform docs, compatibility registry defaults and changelog entries from migrations/seeds.

02

Обновления работающих окружений

Existing environments should be patched through migrations, not by hand-editing the baseline SQL first.

03

Чистый baseline

After migrations normalize a database, a new dump can become the next baseline SQL.

Seed and migration notes are internal maintenance material. They explain why registry values, CTA docs, platform changelog entries and documentation references are created automatically during deployment.

What belongs here

  • Compatibility baseline changes for Joomla, PHP and database product lines.
  • Documentation reference seeds for ADR/PDF/API/ERD supporting files.
  • Product-specific documentation seeds such as Baby in Brazil CTA.
  • Platform changelog seeds that describe what changed in the system itself.

What does not belong here

End-user setup instructions, CTA field explanations and template override guides should not be buried in migration notes. They belong in user or developer docs so the right reader can find them quickly.