Page builder
Try it
Compared with today
The current frontpage editor in im-web (commit 97870a1) against this feature.
| Area | Today | Page builder |
|---|---|---|
| Pages | One front page | Front page and any number of landing pages, from templates or copies |
| Languages | None | Norwegian, English, Swedish for every text, with what’s missing shown in place |
| Drafts | Every publish is live | A draft that autosaves; visitors see the published version |
| Publishing | Publish everything, unchecked | Publish the languages that are ready, now or at a set time |
| Validation | Required fields accept empty text | Errors block publishing, warnings ask for judgement, both point to the block |
| History | Kept but hidden | Every published version, compared with the draft, restorable |
| Undo | Buttons that do nothing | Undo and redo for every change |
| Editing | A form beside a preview | Type into the page itself, or use the inspector |
| Sections | Can’t be removed once added | Add anywhere, drag to reorder, duplicate, hide, delete |
| Images | Copied records and URLs that go stale | Relations to the archive with focal point, crop and alt text per language |
| Credits | Hero only, for screen readers | With every image, in the page’s language, from the record |
| Image sources | Editorial SDL only, picked by hand | Editorial and creative, by hand or from a saved search |
| Responsive | Some sections have no mobile layout | Desktop, tablet and phone previews of the real layout |
| Navigation and footer | Hardcoded, overwritten on publish | Edited per language, with its own draft and publish |
How images work
A page never copies an image. It points to the record and keeps only what belongs to this one use.
The record in the archive
Preview, headline, creator and credit, supplier instructions. Owned by the archive; can change.
The relation on the page
Which record (id), focal point, shape, alt text per language, and whether it links to the image in the portal.
What visitors see
Today's preview, cropped around the focal point, with “Foto: creator / credit” in their language.
Because it's a relation, every image knows where it's used (“Where is this image used?”), and a removed record shows up as an error before publishing instead of a broken image.
What a page builder still needs
Not built here. Some need decisions first; the lifecycle chart marks the open questions.
People and process
- Roles: who may edit, who may publish. Approval before publishing (four eyes), at least for the front page.
- Comments on a draft, and notifying someone to review.
- Two editors on the same page at once: today the last save wins.
- An audit log of who changed what.
Images and media
- Video and albums as sources; upload of tenant-owned images.
- Different crops per device, not only a focal point.
- Real usage rights: which images may be used in marketing, from the rights data, not a heuristic.
- Warnings when a used image is withdrawn or its rights change after publishing.
Pages and site
- A page tree and navigation built from it; breadcrumbs.
- Redirects when an address changes or a page is unpublished.
- Reusable sections shared between pages (e.g. one contact band everywhere).
- Scheduled unpublishing for campaigns that end.
- Search engine image, social sharing previews, sitemap.
Languages
- A translation workflow: mark text as changed since translated, send to a translator, machine translation as a first draft.
- Admin in Norwegian and Swedish (the admin is English only today).
- Per-language images where a picture only fits one market.
Quality
- Automatic accessibility checks: contrast of text on images, heading order.
- Link checking for web addresses.
- Page analytics: which blocks get clicks.
Decisions made while building are in Page builder: decisions.