1 min read

Why Two Sites?

While publishing here, I’ve also been setting up a second Ghost instance hosted on Render. That version is intended to mirror the kind of infrastructure a CMS administrator might work with in a production context—containerized, version-controlled, and self-managed.
Why Two Sites?

This site began as a quick deployment on Ghost(Pro) to support my application for the Ghost CMS Administrator role at Sticker Mule. The goal was to establish a live site that could demonstrate immediate familiarity with Ghost and offer a foundation for further development.


Why Two Sites

While publishing here, I’ve also been setting up a second Ghost instance hosted on Render. That version is intended to mirror the kind of infrastructure a CMS administrator might work with in a production context—containerized, version-controlled, and self-managed.

The two sites are part of a single workflow:

  • Ghost(Pro) serves as the primary authoring and presentation layer for now
  • The Render deployment is being used to test theme customizations and automation strategies

Current Status

At this stage, the Render instance is live but still running the default theme. The two sites are not yet synced in terms of content, navigation, or styling.

Upcoming work includes:

  • Migrating theme changes to the Render instance
  • Setting up version-controlled theme deployment
  • Exploring API-based automation for publishing and site structure updates

Purpose

This approach is meant to demonstrate not just comfort with Ghost as a tool, but the ability to manage it in a real-world environment where reliability, transparency, and coordination with developers matter.