feat: tabbed settings, i18n, filemtime assets & readme (Epic #20) #108
No reviewers
Labels
No labels
area: build
area: ci
area: compare
area: model
area: plugin
area: provenance
area: rite
area: settings
area: ui
backport
blocked
breaking
confirmed
dependencies
duplicate
epic
invalid
needs-info
needs-triage
php
priority: high
priority: low
priority: medium
regression
type: chore
type: correction
type: docs
type: enhancement
type: feature
type: fix
type: perf
type: refactor
type: security
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Directorium/Ordo!108
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/20-settings-i18n-assets"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Ordo O5 — settings, i18n, assets & readme (Epic #20)
Completes the standalone v0.1 plugin: the settings screen, full internationalisation,
cache-busting assets, and the distribution readme.
Settings (#21)
A tabbed Settings → Ordo screen (Calendar · Appearance · Display · About) rendered to the
approved mockup (Surface 5), on the WordPress Settings API. One whitelisted
ordo_settingsoption, admin-only, tabs carried in the query string (shareable, no-JS). Every control is wired:
The rubric system is shown read-only (1962 is the only system v0.1 computes); the mockup's
rubrics-in-red / Latin-names toggles are deferred (nothing to drive in v0.1 — same
accuracy-first posture as O4).
Internationalisation (#22)
ordotext domain loads oninit; every front-end and admin string is wrapped.bin/make-pot.php→ a deterministiclanguages/ordo.pot(119 strings), including theblocks'
block.jsontitle/description/keywords (core'sblock title|description|keywordcontexts).bin/check-i18n.php(new CI gate) fails on a missing/mis-positioned text domain, an untranslatedescaped literal, or a stale .pot.
Assets (#23)
Every style/script is versioned by file modification time and enqueued only where a surface
renders; the chosen palette is added as inline CSS once per request.
Distribution (#24)
A WordPress.org
readme.txtwith accurate headers (Requires at least: 6.3, matching theblocks' API v3), a v0.1.0 changelog, and install steps matching the shipped surfaces.
Verification
phpcs(PSR-12) ·phpstanL6 · 56 PHPUnit tests / 191 assertions · clean-room guard ·the new i18n guard — all green. The settings screen was render-checked offline (13/13).
This change was reviewed by an adversarial multi-agent pass; the confirmed findings
(block.json extraction,
_nxsupport, domain-position check, the WP-floor/apiVersion mismatch,and a single-column day-view layout fix) are all folded in.
Closes #20
Closes #21
Closes #22
Closes #23
Closes #24