Project

Project: website refresh

A case-study style page. Projects, campaigns, and events all share the same block library, so a new page type is mostly a naming decision.

The brief

Rebuild a small marketing site so that routine content changes no longer require a developer, while keeping deployment and version history under engineering control.

The approach

Content moved into Markdown files in a Git repository. A browser-based editor writes to those files, and every save becomes a commit that triggers a rebuild.

Placeholder project screenshot

Outcome

The result is this site. The screenshot placeholder here would normally show the finished work.

What was delivered

Content model

Two page collections, a settings file, and ten reusable blocks.

Editing workflow

Browser-based editing with Git commits behind every save.

Hosting

Static files served from a CDN, rebuilt on every content change.

Related