Skip to content
Sign inJoin waitlist

CMS options — Marai Neesu

Marai Neesu’s HTML edition has no admin panel: projects, products, 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 Marai Neesu, for whoever sets that up.

For a CMS, the Marai Neesu Astro or Marai Neesu Next.js edition is the shorter road: the same design, with every collection 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
Project 6 title, summary, service, client, date, cover, description (rich text), highlights (rich text), gallery (up to three screens) project/<slug>.html, the cards of Home, Projects and “See more projects”, the CV’s Project rows
Product 6 title, tagline, price, demo link, buy link, cover, two screenshots, specification, overview (rich text) product/<slug>.html, the cards of Home, Products and “More Products”
Post 12 title, photo, category, date, text (rich text) blog/<slug>.html, the Blog, “Latest Articles & Publications”, “See more posts”, the CV’s Writing rows
Service 4 title, starting price, description, link, four photos The cards of Home and Services, the contact form’s interests, a project’s service
Testimonial 8 name, role, portrait, quote, rating (stars) “Trusted by Professionals” on Home
Experience 4 title, company, period, link, description “My Experiences” on About, the CV’s Work Experience
Tool 9 name, category, logo, link “Stack” on About
Social 4 label, two letters, link, logo The social tiles of the Home hero

The course, its modules and FAQ, the CV’s education, contact rows and certifications, the services’ FAQ and the client logos of the Projects page are page copy, not collections.

No item refers to another by a key; in the HTML each place holds a copy:

  • lists follow the order of the HTML, not the dates: the demo’s posts are newest first, and Home and the CV show the first items of a list (four projects, three posts, six products; the CV four projects, four experiences and four posts);
  • “See more projects” shows the first two projects that aren’t the current one; “More Products” the first other products (three on desktops and phones, four on tablets);
  • “See more posts” lists up to three other posts of the same category (Product Design, Web Design or UX/UI in the demo);
  • a project’s service is the name of a service, and its link at the top of the project page is that service’s link;
  • the contact form’s interests are the services’ titles, typed in contact.html.

Post texts, a project’s description and highlights, and a product’s overview use a small set of HTML: paragraphs (<p>), headings (<h3> in a post, <h5> in a product’s overview), bulleted and numbered lists whose items hold paragraphs, bold (<strong>) and code (<code>, set in the text’s own font). There are no links or images inside the text in the demo. The classes to copy are in Editing the site.

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 1440 × 1080 (4 : 3)
A project’s gallery 1440 × 1080 for the first two screens, 2240 × 1680 for the third
A product’s cover and screenshots 1200 × 814
A post’s photo (the card and the cover) 1600 px wide
A service’s photos 400 px wide
A testimonial’s portrait 150 × 150 (shown round, 50 px)
A tool’s logo 100 × 100 (shown 50 px)
A social logo SVG, shown 26 px