Everything a host needs to run content beyond pages, so that a host builds none of it locally.
Four features as tables with admin screens:MEDIA, BLOG, PROJECTS and PHOTOS. Eighteen tables, four more areas with homes, six value lists, image and file previews. Each feature is gated by cms.features and needs CORE (and MEDIA where it points at media).
Changelog for the new tables: create changesets under the existing 1.0.0-create-<table> naming, constraints per feature, the cross-feature constraints, seed rows for media types and blog types, and a guard that stops on a name collision. A feature can be switched on at a later migration. docs/ddl/postgres.sql is regenerated from the changelog.
Value-list fields accept only the values of their list: a record error on insert and update (CmsValueListCheck), and a check constraint in the database. QQQ offers a fixed list in a form but accepts any value in a write.
The qbit ships its own help:help/qbit-cms.yaml, 643 entries covering every app, home, table, section, field, child list and value list. It is registered when the default prefixes are used and held to QQQ core's HelpBundleAssertions gate, so a host writes no CMS help.
Smaller fixes: "Media" is its own plural; home text is sized in rem.
One change to a released changeset (please read)
1.0.0-guard-existing-tables no longer has runAlways. With it, every migration rewrote the changeset's row in DATABASECHANGELOG, so a second run was never a no-op and a rollback by count began with the guard. A host whose migrations must be repeatable could not include this changelog and had to copy the tables instead.
The changeset now runs once, before the tables are created, and carries validCheckSum: ANY so an install that already recorded it under 0.1.0-RC.2 migrates on without complaint. CmsInstallTest.testRerunIsNoop asserts that the migration history is unchanged by a second run, and that a history recorded by the earlier version is accepted.
Not in this change
File upload, storage and renditions (a media record points at a file by its address), publishing processes, the content stream, the Site API, permalink templates, the lookup filter that keeps a project's category to its own site, and data health rules.
## What this adds
Everything a host needs to run content beyond pages, so that a host builds none of it locally.
- **Four features as tables with admin screens:** `MEDIA`, `BLOG`, `PROJECTS` and `PHOTOS`. Eighteen tables, four more areas with homes, six value lists, image and file previews. Each feature is gated by `cms.features` and needs `CORE` (and `MEDIA` where it points at media).
- **Changelog for the new tables:** create changesets under the existing `1.0.0-create-<table>` naming, constraints per feature, the cross-feature constraints, seed rows for media types and blog types, and a guard that stops on a name collision. A feature can be switched on at a later migration. `docs/ddl/postgres.sql` is regenerated from the changelog.
- **Value-list fields accept only the values of their list:** a record error on insert and update (`CmsValueListCheck`), and a check constraint in the database. QQQ offers a fixed list in a form but accepts any value in a write.
- **The qbit ships its own help:** `help/qbit-cms.yaml`, 643 entries covering every app, home, table, section, field, child list and value list. It is registered when the default prefixes are used and held to QQQ core's `HelpBundleAssertions` gate, so a host writes no CMS help.
- **Smaller fixes:** "Media" is its own plural; home text is sized in `rem`.
## One change to a released changeset (please read)
`1.0.0-guard-existing-tables` no longer has `runAlways`. With it, every migration rewrote the changeset's row in `DATABASECHANGELOG`, so a second run was never a no-op and a rollback by count began with the guard. A host whose migrations must be repeatable could not include this changelog and had to copy the tables instead.
The changeset now runs once, before the tables are created, and carries `validCheckSum: ANY` so an install that already recorded it under `0.1.0-RC.2` migrates on without complaint. `CmsInstallTest.testRerunIsNoop` asserts that the migration history is unchanged by a second run, and that a history recorded by the earlier version is accepted.
## Not in this change
File upload, storage and renditions (a media record points at a file by its address), publishing processes, the content stream, the Site API, permalink templates, the lookup filter that keeps a project's category to its own site, and data health rules.
## Checks run locally
`./mvnw -B verify`: 40 tests pass, Checkstyle 0, guardrail and coverage checks pass.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Eighteen content tables from the kof22 website's models, as standard QQQ
tables in the qbit's own style: media and media types; blogs, blog types,
authors, blog tags, blog posts with their tags, media and related versions;
project categories, projects and project updates; album folders, photo
albums, photos, photo tags and their links.
- Entities under media/model, blog/model, projects/model and photos/model,
with six value-list enums registered in CmsTables.VALUE_LISTS and produced
as possible-value sources named with the table prefix.
- CmsTableDefinition gains imagePreview, filePreview and help; the table
builder turns them into QQQ file-preview adornments and field help.
- Four more areas (Media, Blogs, Projects, Photos), each with its own home.
- Changelog: 1.0.0-create-<table> for each table, constraints per feature,
two changesets for the links between two features, generic media and blog
type seeds, and a run-once guard against name collisions. Every content
changeset is gated on the features it needs, so a feature can be installed
by a later run and a feature whose needs are missing installs nothing.
- A feature that is off produces nothing; a lookup, a child list or a
foreign key that links two features exists only when both are on.
- Reference DDL regenerated from the changelog on PostgreSQL 17 (the eleven
CORE tables come out unchanged).
Not in this change: file upload, storage and renditions (a media record
points at a file by its address), the publishing processes, the content
stream and the Site API.
Tests: 37 (6 new in CmsContentFeaturesTest), Checkstyle 0, guardrails and
coverage checks pass.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
QQQ offers a fixed list (a possible-value source of an enum) in a form but
accepts any value in a write: through the API a project could be saved with
a status that is not on the list. Found by a live check in a host
application.
- CmsValueListCheck: a pre-insert and pre-update customizer on every table
with a value-list field; a record with another value gets an error and is
not written, and an update is checked only for the fields it names.
- Changelog: check constraints on the same columns (as kof22 has for
media_type and blog_post_version; the project status check is new), and
kof22's checks on media_type.max_file_size_mb and the focal point of a
project's image. They are part of the not yet released
1.0.0-constraints-<feature> changesets.
- Reference DDL regenerated.
Tests: 37, Checkstyle 0, guardrails and coverage checks pass.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
The table label and the home counts read "Medias" and "0 medias". Seen in
the admin of a host application.
Tests: 37, Checkstyle 0, guardrails and coverage checks pass.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
A host should take the CMS whole from this qbit: its tables, its help and
its schema. Two things forced a host to write CMS material of its own; both
are fixed here.
- Help: help/qbit-cms.yaml (643 entries) covers every app, home, table,
section, field, child list and value list. The producer registers it when
the host uses the default names. CmsHelpTest holds it to the core's
coverage gate (HelpBundleAssertions) and to every section.
- Schema: the first guard changeset (1.0.0-guard-existing-tables) no longer
has runAlways. It rewrote its DATABASECHANGELOG row on every migration,
so a second migration was never a no-op and a rollback by count began with
it; a host whose migrations must be repeatable had to copy the tables. It
runs once now, with validCheckSum: ANY so an install that already ran it
migrates on unchanged. This changes a released changeset on purpose;
CmsInstallTest.testRerunIsNoop covers a second run and an install the
earlier version recorded.
- Homes: text sizes in rem (labels 0.875rem instead of 13px), so they follow
the reader's text size.
Tests: 40, Checkstyle 0, guardrails and coverage checks pass.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What this adds
Everything a host needs to run content beyond pages, so that a host builds none of it locally.
MEDIA,BLOG,PROJECTSandPHOTOS. Eighteen tables, four more areas with homes, six value lists, image and file previews. Each feature is gated bycms.featuresand needsCORE(andMEDIAwhere it points at media).1.0.0-create-<table>naming, constraints per feature, the cross-feature constraints, seed rows for media types and blog types, and a guard that stops on a name collision. A feature can be switched on at a later migration.docs/ddl/postgres.sqlis regenerated from the changelog.CmsValueListCheck), and a check constraint in the database. QQQ offers a fixed list in a form but accepts any value in a write.help/qbit-cms.yaml, 643 entries covering every app, home, table, section, field, child list and value list. It is registered when the default prefixes are used and held to QQQ core'sHelpBundleAssertionsgate, so a host writes no CMS help.rem.One change to a released changeset (please read)
1.0.0-guard-existing-tablesno longer hasrunAlways. With it, every migration rewrote the changeset's row inDATABASECHANGELOG, so a second run was never a no-op and a rollback by count began with the guard. A host whose migrations must be repeatable could not include this changelog and had to copy the tables instead.The changeset now runs once, before the tables are created, and carries
validCheckSum: ANYso an install that already recorded it under0.1.0-RC.2migrates on without complaint.CmsInstallTest.testRerunIsNoopasserts that the migration history is unchanged by a second run, and that a history recorded by the earlier version is accepted.Not in this change
File upload, storage and renditions (a media record points at a file by its address), publishing processes, the content stream, the Site API, permalink templates, the lookup filter that keeps a project's category to its own site, and data health rules.
Checks run locally
./mvnw -B verify: 40 tests pass, Checkstyle 0, guardrail and coverage checks pass.🤖 Generated with Claude Code