One site. Two languages. A reviewable workflow.

A marketing page has a longer lifecycle than its published view suggests. Someone writes it, translates it, checks the claims, previews the result and keeps it current. The same article may later become a social deck. Designing those tasks as separate products would make the team repeatedly reconstruct the same context.

The repository brings three surfaces into one deployable application: Cefalo’s public English and Norwegian website, the editor used to maintain that content, and the Post Builder used to compose a carousel. The design problem is to connect them without making a public visitor, an editor and a publisher use the same interface.

The public site uses actual locale routes rather than swapping a dictionary inside one page. Its English and Norwegian pages have their own markup, language metadata and canonical relationships. That establishes a clear destination for each version while leaving the authoring interface responsible for keeping the versions aligned.

Inside the editor, the two languages are visible together. A writer can relate an English headline to the Norwegian field beside it, rather than switching away and comparing from memory. The tutorial frames show this relationship in the Hero inspector and the image-description guidance: context stays visible while a particular field is being edited.

The parity implementation draws an important boundary between saving and publishing. Writing one language before the other is a normal state of work. Refusing that save would make the editor obstruct the task it is meant to support. A partially translated draft can therefore exist without becoming an acceptable published page.

The publication check compares the corresponding section types and counts, localized fields and list lengths. The interface needs to turn a mismatch into a specific correction: which section, which field and what differs. The useful outcome is a reviewable problem at the point of commitment, rather than a generic failure after the writer believes the page is finished.

A publishing dialog can become misleading if its validation is written independently from the service. It may approve a document the server rejects, or display a different reason for the same failure. In this implementation, publish preflight imports the parity and proofreading functions used by the server hooks and prepares the document through the same composition adapter.

That shared rule becomes a UX advantage. The person can inspect the issue before submitting, and the explanation refers to the actual acceptance condition. Permission remains a server responsibility; the editor’s visible controls and local feedback help the person understand the action without replacing authorization or the final publishing check.

The Post Builder extends the workflow from a page or article into an editable slide deck. It needs to preserve the distinction between shared structure and localized words: a stored slide contains both languages, while a rendered slide resolves a single locale. Copy, images and module content must reach the renderer in a form it can reproduce.

The renderer mapping is deliberately direct. Template and format identifiers in the studio correspond to the renderer’s identifiers, rather than silently collapsing distinct layouts into a smaller set. The source includes a coverage check for that relationship. It is a design-system concern as well as an engineering one: the exported composition should represent the template the person actually selected.

The platform’s public site uses Source Sans 3 with a navy-tinted neutral scale, mint action surfaces and nearly square corners. The current token file names both the identity colors and the semantic roles used by public pages. Those roles matter because a logo swatch and a readable interactive surface are different design decisions.

The internal identity-led tools and the brand package are related sources, but they are not interchangeable instructions for every surface. The public site retains its mint and dark-navy semantics; the navy, green and cyan identity palette serves its documented applications. This case focuses on the working platform, while the separate Cefalo brand-system case explains the asset and guideline package.

A person can preview and download a deck without publishing it. The existing tutorial makes this distinction explicit in its export dialog, showing PDF, zipped PNG and MP4 options while explaining that the files download locally. A successful render therefore answers a different question from a successful publishing action.

The repository’s current workflow keeps public-site and LinkedIn publication under human control. AI-assisted work can prepare or refine material, but the review surface must still expose the language versions, the selected composition and the destination. The older automated text-post product was retired; it is not presented here as a current capability of this platform.