Skip to main content

Case study · Software

Perdura

A Shared Family Archive Relatives Can Add To and Keep

Status
Public beta
Platform
Astro, Payload CMS, TypeScript and PostgreSQL
Live site
perdura.org
A published Perdura memorial archive, with a portrait, dates and the opening of a life story set on a warm cream ground

What Perdura Needed

A traditional obituary captures a few facts about a person. It rarely has room for the stories, photographs, friendships, work and habits that make a life recognizable to the people who knew it.

Perdura began with a practical question. How can a family create an archive that relatives can add to, that someone in the family reviews, and that the family can keep if the hosted service changes? Many memorial services offer a short tribute or a printed book, and online access depends on the company keeping the material.

We defined the product, designed the experience, built the application, and continue to run and improve it.

What We Built

  1. Designed From the Start for Families to Keep a Copy

    Published archives are static pages, and we modeled the content and media so a family can keep its own copy. Today the export produces a content bundle and a printable book. The complete export of written content and original media is still in development.

  2. A Private Way for Relatives to Contribute

    Family members receive a private link where they can write a memory, record their voice, or add photographs and video from a phone. Nothing is published until an owner or editor in the family reviews it, and contributors do not create an account before they take part.

  3. A Publishing System Designed for Many Families

    Each archive publishes to its own address while using shared content models and a themed design system. Every new archive follows the same publishing process, with no custom build for each family.

  4. A Design System Made for Careful Reading

    We set type, color, spacing and content patterns for pages people read closely, share with relatives and come back to. Each archive needed to feel personal and calm and still match the others.

From Contribution to Published Archive

Besides the public page, a family archive needs a private way to add material, a clear review step, a repeatable publishing process and a copy kept outside the platform. Perdura handles each one separately, so none of them adds work for the family.

  1. Structured Content

    Stories, moments, people, photographs and messages are stored as separate, related content types. That gives the archive room to grow while keeping new material consistent and easy to place.
  2. Private Contribution and Review

    Contributors use private links to add memories and media. An owner or editor decides what appears publicly. Contributing stays simple, and the family controls what is published.
  3. Static Publishing

    Approved content publishes as a static Astro site. Public pages are served as prebuilt files, with no application code running for each reader. That keeps the public archive light and simpler to run.
  4. Family Export

    The export gives a family a bundle it can keep and use away from the hosted service. Today that is a content bundle and a printable book, with the full written and media export in development. We designed the data and publishing around that export from the start.

What Families and Editors Can Do

  • Families Can Keep Their Own Copy

    The export produces a content bundle and a printable book today, with the full written and media export in development, so access does not depend on the hosted service alone.

  • Relatives Can Contribute Without Giving Up Editorial Control

    Private links make it easy to add material. An owner or editor decides what becomes part of the published archive.

  • A Personal Archive Can Still Be Practical to Run

    Shared content models and documented design rules let new archives follow a consistent publishing process instead of requiring a new build each time.

Contribution, Timeline and Mobile Views

Contributing Without an Account

The contribution section of a published archive, showing a candle-lighting panel and an Add a Memory form noting that submissions are reviewed before they appear
A relative can write a memory, record their voice, or add photographs and video through a private link. The form says plainly that someone in the family reviews each submission before it appears, and nobody creates an account to take part.

A Life in Moments

A timeline section of the archive, showing dated moments from the person's life with photographs and short descriptions
The timeline gives a family a place to add dated stories, photographs and milestones over time. Each entry has fields for its date, place, media and story, and the published timeline still reads as a life story.

Built for the Phone It Will Be Read On

Two phone screenshots side by side, the Perdura marketing site and a published memorial archive
A memorial link is often opened on a phone, in a moment when the reader needs the page to be clear and calm. The mobile layout keeps the story, photographs and spacing readable, so the archive does not shrink into a feed.

One Visual System Across Every Archive

The Perdura brand page, showing the typographic scale, color palette and interface components used across the product
Type, color, spacing and components are documented as a shared system. Each new archive can still feel like Perdura while following the same visual rules and the same publishing process.

Need a Product, Portal or Publishing System Built Around Your Process?

We design and build custom applications for work that does not fit a template, including structured content, user roles, approval steps, private workflows, publishing systems and data exports. Perdura is one product we defined, built and continue to run.