← All posts
Illustration originally made for the Lyfar Studio website.

technology

This website needed one place to edit the content

Visit the website (opens in a new tab) lyfar.com

An article can appear on the blog, a service page and the homepage. Editing its title shouldn’t mean finding three copies of the same card.

The Lyfar site uses EmDash for published Posts and Projects. Astro renders the pages, and the listings read those records at request time. Change the content in the CMS and the next page request can use it.

One record, several places to read it

Posts carry the article, topic, thumbnail and description. A service page selects the posts in its topic. The homepage selects its featured stories. Both use the same editorial content.

An optional featured rank controls which stories lead. That separates editorial selection from publication date. You can keep a useful article near the front without changing when it was written.

Guides have their own publication section inside Posts. They appear in the Guides area and its sitemap, while the ordinary Blog feed excludes them. A shared collection doesn’t have to mean one undifferentiated list.

The published listing also checks publication status. A draft stays out of it. Previewing a piece and publishing it are separate steps, which matters when a title is ready before the article is.

The old files still have a job

The first version of this site kept its content in Markdown. Those files still exist as source material and backups. They don’t overwrite a newer CMS edit when the site builds.

That ownership rule is less visible than the front end, but it prevents a very ordinary mistake: an article gets edited in one place, then an older copy comes back through another route.

The site runs on Astro with a Cloudflare Worker, D1 and media storage. Those choices support the workflow. The important editorial question is simpler: which copy owns the published result?

Before adding another place to edit content, answer that question. Decide which fields are shared, who changes them and how a draft reaches the public page. Then the design can show the same story in several contexts without creating several versions of it.

The same question shaped the EVia website handoff : the person maintaining the content needs a clear place to do the work.

Interested in this?

Learn about Technology →