/ raymatic

Raymatic

Static publishing without managing an SSG.

Write content.
Raymatic handles the publishing machinery.

01 — Create & preview

~/projects
$ ray new my-site
$ cd my-site
$ ray dev
Preview available at http://127.0.0.1:3000

02 — A valid publication

my-site/
├── content/
├── presentation/
└── README.md

03 — Write content

content/hello-world.md
+++
title = "Hello, world"
+++

Hello, world

My first Raymatic publication.

04 — Publish

$ ray check
$ ray build

After a successful build, the complete static publication is written to output/.

Philosophy

Publishing should be the work. Not managing the publisher.

Traditional static publishing exposes machinery that should not need your attention: tool selection, plugin integration, configuration, build debugging, maintenance. The ceremony becomes the project.

Raymatic assumes responsibility for that routine operational complexity and leaves the intentional publishing decisions to you. Low operational surface, high explanatory power.

tool selection → integration → configuration → debugging → maintenance → publication
content → presentation → publication

Explainability

When something breaks, Raymatic explains itself.

A diagnostic should read like a colleague pointing at the exact line — what failed, where, why, what was expected, and what to do next.

error[CONTENT002]: Missing required attribute: title
  --> content/hello-world.md:1:1
  expected: title = "A title"
  help: Add a title to the front matter.

Command surface

Four commands. The whole lifecycle.

$ ray new

Create a valid publication.

$ ray dev

Local preview, watching and feedback.

$ ray check

Validate the publication.

$ ray build

Produce publishable static output.

Principles

01

Strong defaults

Routine publishing decisions should not require configuration.

02

Explainable behavior

When something fails or changes, Raymatic tells you what, where and why.

03

Portable content

Your writing stays plain files — readable and diffable outside Raymatic.

04

Intentional customization

Configuration is a deliberate deviation from defaults.

05

Performance without ceremony

Speed removes waiting and complexity, not just benchmarks.

Start publishing

Make the publication the thing you manage.