codanomiq · Pages, templates and layouts

A page tree you can drag into shape.

Pages nest exactly as they appear in the site’s navigation, so the structure you edit is the structure a visitor walks. Templates and layouts hold the frame, and a change to the frame lands on every page carrying it.

Talk to us about a site
PagesTemplatesLayoutsObjects
Pages11
Templates2
Layouts4
Objects2
Content · PagesDemo data
One tree · Shared frames · Publishing is a permission · Sitemap written for you

What the tool does

In the admin as · Content › Pages
01

The tree

Pages nest under each other as they do in the navigation. Drag one and its children and its URL follow.

02

Templates and layouts

A template is the page shell; a layout is the arrangement of slots inside it. Both are edited in code or in Design mode, whichever suits.

03

Objects

A block used in more than one place — a header, a footer, a promo — written once and referenced everywhere. Turn any block of a template into one from a button underneath it.

04

Quick edits and locking

Small changes save without a full round trip. A publisher can lock a page, template or layout, making it read-only to everyone else until they release it.

05

Editing on the site

Signed in, open any published page and a slim bar appears along the bottom with an Edit toggle. The words change where they sit.

06

Translations and passwords

Any page can carry translations, and any page can be given a password from the selection bar.

The tool itself

Click any screen for a larger view

A demonstration installation, with invented data.

01

One change, every page that shares the frame

The reason a site becomes unmaintainable is that the same thing is written in forty places. Templates, layouts and objects exist so that it is written once.

Change the footer object and every page carrying it is republished. Change a layout and every page built on it follows. The work is in deciding what the frame should be, not in applying the decision forty times.

02

Publishing is a permission, not a habit

Putting something on the public site — publishing a page, unpublishing it, setting a password, locking a template — needs Publishing rights. Day-to-day editing does not.

So the people who write can write, and the moment something becomes public is a decision somebody was trusted with.

03

The parts search engines need are written for you

/sitemap.xml is generated on every publish from the page tree itself, so it cannot drift from the site. Pages published as code — stylesheets and scripts — are never offered to a menu or listed as destinations.

Structure you can see.

If your current site has a page nobody can find and a footer that is wrong on nine pages out of forty, that is the problem this solves. Get in touch →

Back to the platform →