Skip to content
Sign inJoin waitlist

Editing without touching HTML — Cerette

Cerette’s HTML edition has no admin panel: projects, services, posts and every other text are written into the pages, and you edit files (Editing the site).

When someone who doesn’t write HTML needs to publish, the options are the same for every Framebrick template: keep editing the files (GitHub’s web editor works too), a visual editor such as CloudCannon, or an edition built for a CMS. They are explained in Edit HTML templates without touching HTML. This page lists what is specific to Cerette, for whoever sets that up.

For a CMS, the Cerette Astro or Cerette Next.js edition is the shorter road: the same design, with the collections below in data files and a documented path to Sanity, Payload, Strapi, Directus or any headless CMS.

The repeated content of the site, and the fields each item shows:

Collection In the demo Fields Pages
Projects 6 slug, title, summary, category, cover, year, location, duration, area, services (services’ slugs), overview, brief, scope, four story photos, result, three gallery photos, result photo project/<slug>.html, Home’s “Our Projects”, Projects, “Other Work”
Services 6 slug, name, summary, photo, about, included (a text and five deliverables, each a title and a text) service/<slug>.html, Home’s switcher, Services, the footer, a project’s details, the forms’ Project type
Testimonials 6 slug, name, role, photo, year, rating, quote Home, Projects
Team 12 slug, name, role, photo, summary About
Posts 12 slug, title, category (Architecture, Construction, Interior), date, excerpt, cover, content (rich text) blog/<slug>.html, Blog, Home’s three newest, “Similar posts”
Legal 2 slug, title, date (“Last updated”), content (rich text) legal/<slug>.html

Testimonials and team members have no pages of their own. The figures, the awards, the six reasons of “Why Cerette”, the founder’s quote and the call to action are single blocks of their pages, not collections.

No item holds a link to another in the HTML; each place holds a copy:

  • a project names its services: the Services line of its details, each a link to the service’s page (Aureline House: Architecture, Interior, Construction);
  • a service page’s form starts with the service’s name in Project type;
  • order: projects, services, testimonials and team members keep the order of their collection; “Other Work” is the first three other projects; posts are newest first, Home shows the three newest, and “Similar posts” is three other posts of the same category, newest first;
  • paging: the Blog shows six posts on desktops and four on tablets and phones, then more as the visitor scrolls; About’s team grid on tablets and phones shows six people at a time.

A post’s content and a legal page’s content are blocks:

  • paragraphs (<p class="mt-5 first:mt-0">); links inside them are underlined and turn brown on hover (none in the demo);
  • headings of one level (<h2>, drawn 28 / 32 / 36 px);
  • bulleted lists (<ul class="pl-[23px] list-disc …">), in the legal pages.

There are no bold or italic runs, numbered lists, quotes or images inside the text in the demo. A project’s and a service’s texts are plain paragraphs.

Every photo sits in a frame and is cropped to fill it, so a photo of other proportions works; use images at least as large as the layout needs:

Image Size
A project’s cover (its page’s hero, its cards) 2400 × 1600
A project’s two tall story photos 456 × 684
A project’s two wide story photos 1724 × 1150
A project’s gallery photos (three) 1090 × 730
A project’s result photo 2280 × 1520
A service’s photo 2280 × 1520
A post’s cover 2280 × 1520
A testimonial’s photo (shown 38 px round) 152 × 152
A team member’s portrait 800 × 1200