Initial Lektor site
This commit is contained in:
@@ -0,0 +1,11 @@
|
||||
_model: page
|
||||
---
|
||||
title: Not Found
|
||||
---
|
||||
eyebrow: Error 404
|
||||
---
|
||||
summary: This page is missing from the record.
|
||||
---
|
||||
body:
|
||||
[Return to the chronicle](/).
|
||||
|
||||
@@ -0,0 +1,18 @@
|
||||
_model: entry
|
||||
---
|
||||
title: Boring Deployments Are a Feature
|
||||
---
|
||||
date: 2026-08-10
|
||||
---
|
||||
kicker: Article
|
||||
---
|
||||
summary: Why a small, transparent deployment chain is often the most resilient one.
|
||||
---
|
||||
body:
|
||||
A static site does not need a sprawling production stack. A canonical Git
|
||||
repository, an isolated build tool, immutable release directories, an atomic
|
||||
symlink, and nginx are enough to make deployment understandable and reliable.
|
||||
|
||||
The important property is not novelty. It is that a failed build cannot replace
|
||||
the working site.
|
||||
|
||||
@@ -0,0 +1,8 @@
|
||||
_model: section
|
||||
---
|
||||
title: Articles
|
||||
---
|
||||
eyebrow: Field Notes
|
||||
---
|
||||
summary: Longer-form technical notes, decisions, and lessons worth keeping.
|
||||
|
||||
@@ -0,0 +1,8 @@
|
||||
_model: section
|
||||
---
|
||||
title: Blog
|
||||
---
|
||||
eyebrow: Dispatches
|
||||
---
|
||||
summary: Short updates from the Labyricorn workshop.
|
||||
|
||||
@@ -0,0 +1,16 @@
|
||||
_model: entry
|
||||
---
|
||||
title: Hello from Labyricorn
|
||||
---
|
||||
date: 2026-08-11
|
||||
---
|
||||
kicker: Blog
|
||||
---
|
||||
summary: The first entry from the new Git-backed Lektor site.
|
||||
---
|
||||
body:
|
||||
The new Labyricorn site starts here: an intentionally small publishing system
|
||||
with content that is easy to edit, review, build, deploy, and roll back.
|
||||
|
||||
More project notes, articles, and experiments will follow.
|
||||
|
||||
@@ -0,0 +1,12 @@
|
||||
_model: page
|
||||
---
|
||||
title: Home
|
||||
---
|
||||
eyebrow: The Chronicle
|
||||
---
|
||||
summary: A living record of what's shipping, what's written, and what's quietly under construction.
|
||||
---
|
||||
body:
|
||||
Every entry is maintained in Git and published through a repeatable static build.
|
||||
Commit it, deploy it, and it appears.
|
||||
|
||||
@@ -0,0 +1,8 @@
|
||||
_model: section
|
||||
---
|
||||
title: Projects
|
||||
---
|
||||
eyebrow: Workbench
|
||||
---
|
||||
summary: Experiments, production systems, and useful things built in public.
|
||||
|
||||
@@ -0,0 +1,18 @@
|
||||
_model: entry
|
||||
---
|
||||
title: Labyricorn Website
|
||||
---
|
||||
date: 2026-08-11
|
||||
---
|
||||
kicker: Project
|
||||
---
|
||||
summary: A Git-backed Lektor website built into immutable releases and served by nginx.
|
||||
---
|
||||
body:
|
||||
This website is the first production project in the new Labyricorn publishing
|
||||
system. Source lives in Git; Lektor renders static files; nginx serves only the
|
||||
active release.
|
||||
|
||||
The deployment process validates every build before atomically switching the
|
||||
public document root, keeping the previous release available for rollback.
|
||||
|
||||
Reference in New Issue
Block a user