087f717f55
Some checks failed
Forgejo Android APK / Root app tests (push) Successful in 59s
Forgejo Docker Build / Root app tests (push) Successful in 53s
Forgejo Android APK / Build signed APK (push) Successful in 2m2s
Forgejo Docker Build / Build Docker image (push) Successful in 8s
Forgejo Docker Build / Deploy to the host (push) Failing after 2s
Markdown could express about five of the things the renderer can draw, so the model had no way to say "put this figure beside these three bullets" or "make this a comparison with two labelled columns" — my parser inferred a layout from the shape of a list, and inferring is what made every deck look the same. A presentation is now described as a deck: the model returns JSON naming a layout per slide and the prompt it wants each figure drawn from. Four layouts were added to the renderer for it — two tinted labelled columns for a comparison, a callout card for a red flag or a dose, a figure beside its bullets, and a full-slide figure. Articles stay markdown, which is what prose wants. Markdown is still produced, serialised from the deck, so Word export and text editing keep working and the stored artifact stays readable by a person. The deck is stored alongside it because that serialisation is lossy by design: round-tripping through markdown would throw away exactly the layout choices this was built to capture. A resource made before this, or an article forced into slides, still renders by inferring from its markdown. Nothing here can cost more than the thing that went wrong. A reply that is not a deck falls back to asking for markdown rather than saving the model's apology; a malformed slide degrades to bullets rather than throwing; a comparison with one column is not a comparison; a figure that cannot be queued leaves a slide of text rather than an empty frame; and JSON wrapped in fences or a covering sentence is read rather than refused. Verified live on "croup versus epiglottitis": the model chose section, bullets, table, compare, figure, callout and image layouts across thirteen slides, and the exported deck was rendered to PDF, rasterised and looked at — the comparison renders as two tinted cards, the red flag as a callout, and the figure sits beside its bullets. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Dv6sqaY6Vq3ChZHMem3cnU
18 lines
725 B
JavaScript
18 lines
725 B
JavaScript
// The deck a presentation actually is.
|
|
//
|
|
// Markdown stays the readable artifact — it is what Word renders and what a
|
|
// text edit edits — but it cannot express a two-column comparison, a callout, or
|
|
// a figure placed beside its bullets, so a deck round-tripped through markdown
|
|
// loses the layout the model chose. Storing the deck keeps those choices, and
|
|
// the markdown is serialised from it.
|
|
//
|
|
// Null for an article, and for every presentation written before this existed;
|
|
// those still render from their markdown.
|
|
|
|
exports.up = pgm => pgm.sql(`
|
|
ALTER TABLE user_resources ADD COLUMN IF NOT EXISTS deck JSONB;
|
|
`);
|
|
|
|
exports.down = pgm => pgm.sql(`
|
|
ALTER TABLE user_resources DROP COLUMN IF EXISTS deck;
|
|
`);
|