← Websites Case study / Website · Astro Aligne AI · Responsible AI consultancy

From Webflow to code, with a CMS the sales team runs

I first built Aligne's site in Webflow, then rebuilt it in Astro on Cloudflare. The sales team now publishes blogs, events and case studies themselves through a Git-based CMS.

RoleDesign + build
StackAstro · Cloudflare
CMSPages CMS (Git-based)
SectorResponsible AI
CollectionBlogstitle · author · category · body
·
CollectionEventsdate · time · format · venue
·
CollectionCase studiesclient · category · body
·
CollectionAuthorsname · photo
CMS structureEach collection is a folder of Markdown files in GitHub. Saving in the CMS makes a commit, and Cloudflare rebuilds the site.

Problem

Aligne needed one site for the consultancy and its Altrum product pages, with one shared design. The sales team also needed to publish blogs, events and case studies every week without waiting on a designer or a developer.

Process

I moved the site from Webflow to Astro, page by page. First came a shared design system (tokens, header, footer, sections and buttons) used by both the Aligne and Altrum pages. Then each content type became a folder of Markdown files in GitHub, edited through Pages CMS, a simple editor that sits on top of the repository.

Key decisions

  1. Static-first on Cloudflare. Pages are built ahead of time and served from Cloudflare’s network, so they load fast.
  2. A private staging site. Changes go to staging first. Going live is a separate, approved step.
  3. Forms, not code, for the sales team. Pages CMS gives them a form for each blog, event, case study and author. They never touch Git or code.
  4. One design system for two brands. Aligne and Altrum share tokens and components, so one change updates both.

Outcome

The site is live at aligne.ai. The sales team adds blogs, events and case studies themselves, and new pages are built from the same components.

Visit live site ↗