Monorepo for Aesthetic.Computer
aesthetic.computer
1# News Score
2
3Guidelines for writing prose commit summaries on [news.aesthetic.computer](https://news.aesthetic.computer).
4
5---
6
7## Title
8
9Always use: **Commits From {date} to {date}**
10
11Use the dates of the oldest and newest commits in the batch.
12
13## Voice
14
15Write like Jeffrey talking to people who follow the project. Tell the story of what you worked on — the arc of a session or a day. Open with a greeting or a note about what the focus was. This is a devlog, not release notes.
16
17**News vs. Change Blog:** News tells *what happened* — the story of the work. Deeper *why* reasoning (architectural decisions, design philosophy, project direction) belongs on [change.pckt.blog](https://change.pckt.blog) via `publish-changelog.mjs`.
18
19## Structure
20
21- **Tell the story.** "Spent the morning getting CL builds to stand on their own..." not "The build pipeline now separates C and CL paths." The commits are evidence — the post is the narrative.
22- **Group by session, not by system.** What did you work on first? What did that lead to? What was the last thing you touched?
23- **Name the right place.** Changes live in specific sub-sites and tools:
24 - [aesthetic.computer](https://aesthetic.computer) — the main platform, pieces, prompt
25 - [kidlisp.com](https://kidlisp.com) — KidLisp language site; Shop/Buy tab is here
26 - [news.aesthetic.computer](https://news.aesthetic.computer) — news/updates
27 - [prompt.ac](https://prompt.ac) — the AC prompt (also `prompt.mjs`)
28 - [blank](https://aesthetic.computer/blank) — the AC laptop product
29 - VS Code extension (`vscode-extension/`) — OTA status bar, build triggers
30 - oven (`oven/`) — the native build server
31 - session server (`session-server/`) — multiplayer, chat
32 - AT Protocol / PDS (`at/`) — decentralized identity and data
33- **Don't flatten everything into "the web side."** If a change is on kidlisp.com, say kidlisp.com. If it's in the VS Code extension, say that.
34
35## Links
36
37- **Every notable change should link to its commit** using the full GitHub URL: `https://github.com/digitpain/aesthetic-computer/commit/{hash}`
38- **Link product names to their AC URLs** — `[blank](https://aesthetic.computer/blank)`, `[prompt](https://aesthetic.computer/prompt)`, etc.
39- **Link external tools/libraries** when relevant — QuickJS, Claude Code, etc.
40- Use markdown: `**bold**` for emphasis, `` `code` `` for technical names, `[text](url)` for links.
41
42## Tone
43
44- Personal, conversational. You're telling people what you've been up to.
45- OK to mention what's in progress or what something is a step toward.
46- Skip trivial version bumps and typo fixes unless they're part of the story.
47- Save the deeper "why" for the [change blog](https://change.pckt.blog).
48
49## Workflow
50
51```bash
52# 1. See what happened
53ac-news commits --since "1 week ago"
54
55# 2. Read the commits, group them mentally, write the prose
56
57# 3. Dry run
58ac-news post "Commits From March 17 to March 24" "Your prose..." --dry-run
59
60# 4. Post
61ac-news post "Commits From March 17 to March 24" "Your prose..."
62```
63
64Or use `--editor` to write in your editor, or `--file` to post from a markdown file.