Web · Static Site · Migration

Moving Razor’s Edge Ventures from WordPress to a static site

A WordPress-to-Pelican migration that moved content into Markdown and automated static publishing to Amazon S3 with GitHub Actions.

Abstract navy and orange graphic of stacked content pages flowing into two storage panels
Introduction

Razor’s Edge Ventures’ website ran on WordPress with a custom theme designed by another agency. In early 2025 Orpheus moved it to a static site while keeping the existing design.

The project

A new platform under an existing design

Razor’s Edge Ventures’ website was built on WordPress, with a custom theme designed and built by another agency. Orpheus’s job was the platform underneath it: move the site to Pelican, a Python static site generator, without changing how it looks.

The migration ran from late January to early March 2025.

Scope
Content migrationTemplate rebuildSEO carry-overAutomated publishing
Content

Every section moved to Markdown

Orpheus moved the site’s content out of the WordPress database into Markdown files: nearly 300 news articles, 27 investments, 14 careers entries, 13 team profiles, and the site’s core pages, along with their images and files.

Google Analytics, page-level SEO metadata, and an XML sitemap were carried over to the new site.

Templates

WordPress templates rebuilt in Jinja

Each WordPress template was rebuilt as a Pelican Jinja template that matches the existing site: the homepage, about, investments, careers, news with pagination, blog, posts, contact, and the shared header, page header, and footer.

Publishing

From a push to a published site

Orpheus set up GitHub Actions workflows that build the site with Pelican and sync the output to Amazon S3. A push to the main branch publishes production, and a push to the staging branch publishes to a separate staging bucket.

Let's build something
worth shipping.

A short conversation about your goals, what's in the way, whether Orpheus is a fit, and a sensible next step.