Decisions
Scope
The page builder is built from scratch, not from today's front page editor.P1
The brief was a better editor in every way.
You can make as many pages as you like: one front page plus landing pages, each with its own address per language.P2
Multiple pages was a requirement; a hierarchy needs navigation rules nobody has decided.
Pages look like ntb.no, and follow the chosen theme and light or dark mode.P3
ntb.no is the reference for design and typography. It has no dark mode, so the dark version is our own.
There are eight kinds of block, and they adapt to the page's width, so phone and tablet previews are real.P4
Covers the current editor's sections and ntb.no's patterns with fewer, more flexible types.
How today's blocks map onto the design system's sections, rows and cells is not worked out yet.OpenP24
The plan is for the page builder to become an editor for the design system's layouts (sections with or without a background, fixed or fluid containers, rows of 12 columns and cells, spacing from one half-gutter unit). The blocks were built before those principles were written down.
Languages
Pages come in Norwegian, English and Swedish, and a missing translation is shown as missing.P5
TT is a tenant; the site serves Norwegian and English.
Only finished languages go live, and Norwegian must always be finished.P6
An unfinished translation shouldn't block a Norwegian fix, and a half-translated page shouldn't go live.
Missing translations show up greyed out right where they're missing.P7
The editor sees what is missing where it is, without switching screens.
Each language has its own readable address, and switching language keeps you on the same page.P8
Readable URLs in each language.
Drafts and publishing
Every page has a draft that saves by itself; visitors only see what was published.P9
Editors can work without fear; the current editor publishes every change.
Serious problems stop a page from being published; smaller ones only warn.P10
Required fields must mean required.
Every publish keeps a version, and restoring one only changes the draft.P11
Restoring by mistake can't change the live site.
A page can be scheduled to go live at a set time, as the draft is at that moment.P12
Campaign pages go live on a date. Who is told when a scheduled publish fails is still an open question (lifecycle chart).
Every change in the editor can be undone and redone.P13
The current editor has buttons that do nothing.
Images
A page points to an archive image instead of copying it, so the picture and its details stay up to date.P14
The current editor copies whole records and URLs, which go stale.
Every image shows its photo credit, appearing when you point at it and always on touch screens.P15
Credit is required wherever an image is published; showing it on hover keeps it off the picture, as on ntb.no.
Every image needs a description for screen readers in every published language.P16
Accessibility. A headline is a start, not a description.
Click an image to mark what matters in it, so the subject stays in view however it is cropped.P17
Hero and card crops differ by device.
Every image shows which pages use it.P18
Before replacing or removing an image from the archive, someone needs to know where it is used.
Images that may not be cleared for marketing get a warning to check first.P19
Editorial images often may not be used in marketing. The real rule needs the rights team.
A gallery can show the latest results of a saved search instead of hand-picked images.P20
Keeps "latest" sections fresh without editing.
Site
Navigation and footer are edited on their own screen, with their own draft and publish.P21
The current footer is hardcoded and overwritten on every publish.
Links point to a page, a search, an image or a web address, and links to pages keep working when an address changes.P22
Internal links shouldn't break when an address changes.
Links to searches and images open the baseline prototype's search and image pages.P23
The prototype has no real portal; baseline stands in for it.