Cloudline Press - Architecture

This document describes the internal structure of Cloudline Press.

It explains how content moves through the system, how files are organized on disk, and why specific architectural decisions were made.

This is not a deployment guide. It is a structural map intended to help operators understand the system before modifying it.

Architectural Overview

Cloudline Press is a build-time publishing system.

All content transformation occurs before publication. The running web server serves only static files.

There is:

• no database
• no application server
• no runtime rendering
• no templating at request time

Once an edition is published, the server acts only as a file host.

High-Level Flow

1. upstream content is published
2. content is fetched and normalized
3. a full site is built in staging
4. a complete edition is created
5. a pointer is moved to activate the edition

At no point is partial output exposed publicly.

Directory Structure

A typical Cloudline Press installation follows this structure: