Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/apursley2012/choose-your-destiny/llms.txt

Use this file to discover all available pages before exploring further.

The Writing section transforms the developer’s blog into a simulated system log viewer. The page header reads SYSTEM_LOGS and a terminal prompt tails an imaginary file: Tailing /var/log/developer_thoughts.log.... Each post appears as a log entry inside a monospace NeonCard panel, prefaced by an ISO-style timestamp and a color-coded tag indicating the post’s type. Hovering a log entry shifts its left border from transparent to neon orange and reveals a terminal command: > READ_FILE --force. The page closes with a live terminal prompt (guest@portfolio:~/logs$) and a blinking cursor, reinforcing the illusion that the portfolio itself is a running process. Route: /writing (hash: #/writing)
Color theme: Neon orange (#F97316 / --neon-orange)

​
Log Entry Format

Every post renders in the following structure: 
[2023-10-24 14:32:01] [TECH_WRITING]
WHY I STOPPED WORRYING AND LEARNED TO LOVE THE LINTER
A descent into madness, followed by the realization that the red squiggly
lines are actually your friends. How strict TypeScript saved my production build.

> READ_FILE --force    ← visible only on hover
The timestamp and tag appear on one line in the monospace font-terminal typeface. The post title renders in arcade font below, and the excerpt follows in font-code. The > READ_FILE --force action line has opacity: 0 by default and transitions to opacity: 1 on group-hover.

​
Log Entries

Date: 2023-10-24 14:32:01
Tag: TECH_WRITING (cyan)
Title: Why I Stopped Worrying and Learned to Love the Linter
Excerpt: A descent into madness, followed by the realization that the red squiggly lines are actually your friends. How strict TypeScript saved my production build.

​
Tag Color Coding

Each log entry has a color property that determines the neon accent applied to the [TAG] label:
TagColorMeaning
TECH_WRITINGCyanTechnical articles, deep-dives, and opinion pieces
BUG_REPORTMagentaDebugging stories and post-mortems
REFLECTIONLimeCareer reflections and personal essays
TUTORIALOrangeStep-by-step guides and walkthroughs

​
Data Structure

// Writing log entries — ym array (source)
const ym = [
  {
    id: "log-001",
    date: "2023-10-24 14:32:01",
    tag: "TECH_WRITING",
    title: "Why I Stopped Worrying and Learned to Love the Linter",
    excerpt: "A descent into madness, followed by the realization that the red squiggly lines are actually your friends...",
    color: "cyan",
  },
  {
    id: "log-002",
    date: "2023-09-15 02:14:44",
    tag: "BUG_REPORT",
    title: "The Case of the Disappearing Div",
    excerpt: "It was a dark and stormy night. The z-index was 9999...",
    color: "magenta",
  },
  {
    id: "log-003",
    date: "2023-08-01 09:00:00",
    tag: "REFLECTION",
    title: "From Healthcare to Hex Codes",
    excerpt: "Translating triage skills to bug triaging...",
    color: "lime",
  },
  {
    id: "log-004",
    date: "2023-06-20 16:45:12",
    tag: "TUTORIAL",
    title: "Building a Cyberpunk UI with Tailwind",
    excerpt: "Step-by-step guide to making your users feel like they are hacking the mainframe...",
    color: "orange",
  },
];

​
Terminal Footer

At the bottom of the log panel, a persistent terminal prompt renders in neon lime: 
guest@portfolio:~/logs$  █
This is composed of a static <span> containing the prompt string and a BlinkingCursor component (<span> with the blinking-cursor CSS animation class). The footer is separated from the last log entry by a top border in border-dark-lighter.

​
Adding a New Log Entry

This is a pre-built static site — assets/main.js is a minified bundle and is not meant to be hand-edited. To add new writing entries, fork or clone the original source repository, make changes to the source files, then run vite build to regenerate the bundle and redeploy.
1

Choose your tag

Pick a tag from the existing set (TECH_WRITING, BUG_REPORT, REFLECTION, TUTORIAL) or add a new one. If you add a new tag, also decide on a neon color value for its label.
2

Append to the ym array in the source

Fork the original source repository. In the source, find the ym array and add a new object at the top of the array (latest first) with a unique id, ISO-formatted date, tag, title, excerpt, and color.
3

Rebuild and deploy

Run vite build to regenerate assets/main.js. The new entry will appear automatically at the top of the log list.
Dates in the date field are purely cosmetic — the format YYYY-MM-DD HH:MM:SS is chosen to reinforce the system-log aesthetic. You can use any string here, including fictional timestamps, as long as the format is consistent for visual rhythm.

Build docs developers (and LLMs) love

Get started for freeTalk to us