The Writing page adopts the Transmission Archive theme — each blog post is styled as an intercepted signal transmission, complete with a transmission ID, timestamp, and a brief decoded excerpt. The layout deliberately evokes the aesthetic of a mission log or comms archive, keeping the writing section tonally consistent with the rest of the night-sky portfolio.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/apursley2012/aurora-borealis/llms.txt
Use this file to discover all available pages before exploring further.
What the Page Displays
The/writing route presents a vertically scrolling list of four blog post entries. Each entry is a styled card that shows:
- A transmission ID (auto-generated from the post’s position in the array, e.g.,
TX-001) - The post title as the main heading
- A date displayed in
YYYY.MM.DDformat to match the space-ops aesthetic - A short excerpt (two to three sentences) that acts as a teaser
Post Entry Data Structure
All four entries live in aPOSTS array in main.js:
Field Reference
| Field | Type | Purpose |
|---|---|---|
id | string | Unique slug used as the React key; also displayed as the transmission ID tag |
title | string | Post heading — keep to 60–80 characters for best card layout |
date | string | Publication date in YYYY.MM.DD format |
excerpt | string | Two-to-three sentence teaser rendered as the card body |
Adding a New Post Entry
Write your post content
Before editing code, have the
title, date, and excerpt ready. The excerpt should summarize the post’s central argument or insight — not just restate the title.Append to POSTS
Add a new object at the end of the
POSTS array (or at whatever position reflects the chronological order you want):Increment the transmission ID
Use the next sequential
tx-NNN value for the id field to keep the transmission numbering consistent.Editing an Existing Entry
Locate the entry by itsid in the POSTS array and update any field directly. The changes reflect immediately on save — no additional wiring is needed.
Removing an Entry
Delete the object fromPOSTS. The remaining entries will re-render in their new order. You do not need to renumber the id fields, but if visual consistency matters, you may want to update them.
Linking to Full Post Content
By default, the Transmission Archive is a static list — the
excerpt is the entire content displayed, and clicking a card does not navigate anywhere. To add navigation:- Add a
urlorslugfield to each post object. - Wrap the card component in a
<Link href={post.url}>tag. - Create a corresponding route or external URL for each post.
The Writing page is a static list with no CMS integration. All post data lives directly in the
POSTS array in main.js. There is no markdown parsing, no file-based routing, and no external data fetching on this page by default.Styling the Transmission Cards
Each card’s visual style is defined in the project’s CSS. Key class names:| Class name | What it styles |
|---|---|
.transmission-card | Outer card container — border, background, padding |
.transmission-id | The TX-001 badge in the top-left corner |
.transmission-date | The date string in YYYY.MM.DD format |
.transmission-title | The post title heading |
.transmission-excerpt | The body excerpt text |
main.js and your CSS file together.
Related Pages
Case Studies
The in-depth Nebula DB project breakdown — a long-form companion to the shorter blog entries.
About
The career narrative that gives context to why these topics matter to you.