@natjswenson/devlog 0.1.8 → 0.3.1

package/preview/demo.js

@@ -25,31 +25,33 @@ function offsetDate(daysAgo) {
 
 const ENTRIES = [
   {
+    version: 'v0.4.0',
     date: offsetDate(0),
     title: 'You are looking at fake data',
-    summary: "Hi. These aren't your entries. Your entries are 30 seconds away.",
-    body: `## What I Built
+    summary: "Hi. These aren't your releases. Your releases are 30 seconds away.",
+    body: `## What Shipped
 
 Nothing. I'm a placeholder. A handsome one, but still a placeholder.
 
 You're seeing this screen because the preview app couldn't find env vars
 pointing at your dev-log repo. Once that's fixed, this entire feed gets
 replaced with real entries, generated by the \`/devlog\` skill from your
-actual git commits.
+actual version releases — written in your voice.
 
 ## What's Next
 
 You. Setting things up. Probably while half-watching a YouTube tutorial
 about something unrelated. We believe in you.
 
-## Public Commits
+## Commits
 
-- [demo] make placeholder more passive-aggressive ([abcd123](#))
-- [demo] add a tiny bit of charm ([def4567](#))
+- make placeholder more passive-aggressive ([abcd123](#))
+- add a tiny bit of charm ([def4567](#))
 `,
   },
   {
-    date: offsetDate(1),
+    version: 'v0.3.0',
+    date: offsetDate(2),
     title: 'How to make this screen go away',
     summary: 'Two paths: the lazy one (recommended) and the manual one (also fine).',
     body: `## The lazy path
@@ -58,7 +60,7 @@ about something unrelated. We believe in you.
 npx @natjswenson/devlog init
 \`\`\`
 
-Answer four prompts. The CLI creates your dev-log repo on GitHub, installs
+Answer a few prompts. The CLI creates your dev-log repo on GitHub, installs
 the Claude Code skill, and writes your config. Run \`npx @natjswenson/devlog preview\`
 again. This entry vanishes. You feel powerful.
 
@@ -75,18 +77,20 @@ VITE_DEVLOG_PROJECTS=[{"key":"myproject","label":"My Project"}]
 
 ## What's Next
 
-The real preview, with your real entries. Try it.
+The real preview, with your real releases. Try it.
 `,
   },
   {
-    date: offsetDate(3),
+    version: 'v0.2.0',
+    date: offsetDate(5),
     title: "Why you'd actually want this",
-    summary: 'Build in public, but with style. And without remembering to write blog posts.',
-    body: `## What I Built
+    summary: 'Build in public, by release — with style, and without remembering to write blog posts.',
+    body: `## What Shipped
 
-The whole point: you commit code as usual. You run \`/devlog\` in Claude Code.
-The skill reads today's commits and writes a *narrative* entry — not "fix typo,
-fix typo again, ok actually fix it" but real prose about what you built and why.
+The whole point: you tag a release as usual. You run \`/devlog\` in Claude Code.
+The skill finds tags that don't have an entry yet and writes a *narrative*
+release note — not "fix typo, fix typo again, ok actually fix it" but real
+prose about what shipped and why, in your voice.
 
 That entry gets pushed to your dev-log repo. Your site (or this preview app,
 deployed to Vercel/Netlify/Cloudflare) renders it.
@@ -95,29 +99,30 @@ The result: you ship in public without ever opening a blog post editor.
 
 ## What's Next
 
-You'll set this up. You'll ship something on day one. You'll feel slightly
+You'll set this up. You'll tag a release on day one. You'll feel slightly
 smug about it on the train tomorrow. We're rooting for you.
 
-## Public Commits
+## Commits
 
-- [demo] write hopeful pep talk ([eeee101](#))
+- write hopeful pep talk ([eeee101](#))
 `,
   },
   {
-    date: offsetDate(7),
+    version: 'v0.1.0',
+    date: offsetDate(9),
     title: "Things this is not",
     summary: 'A short list, for the avoidance of disappointment.',
     body: `## Not features
 
 - A blog CMS. There are sixty of those. Use one if you want one.
 - A social network. Please don't.
-- An AI ghostwriter for marketing copy. The narratives come from *your*
-  commits. Garbage in, garbage out.
+- A marketing-copy generator. The narratives come from *your* releases, in
+  *your* voice. Garbage in, garbage out.
 - A way to make your past coding choices look better in retrospect. Sorry.
 
 ## Is features
 
-- A way to ship dev log entries without context-switching out of Claude Code.
+- A way to ship release notes without context-switching out of Claude Code.
 - A static, no-backend pipeline (manifest.json + markdown on GitHub).
 - Components you can drop into your own React site, or the preview app you
   can deploy as a standalone dev log.
@@ -132,9 +137,10 @@ Replace this fake entry with a real one. It's right there. Just go.
 const MANIFEST = {
   entries: ENTRIES.map((e) => ({
     date: e.date,
-    file: `${e.date}.md`,
+    file: `${e.version}.md`,
     title: e.title,
     summary: e.summary,
+    version: e.version,
   })),
 };
 
@@ -143,6 +149,7 @@ function entryMarkdown(entry) {
 title: "${entry.title.replace(/"/g, '\\"')}"
 date: ${entry.date}
 project: ${DEMO_PROJECT_KEY}
+version: ${entry.version}
 summary: "${entry.summary.replace(/"/g, '\\"')}"
 ---
 
@@ -156,9 +163,9 @@ function demoResponse(url) {
       headers: { 'content-type': 'application/json' },
     });
   }
-  const m = url.match(/(\d{4}-\d{2}-\d{2})\.md$/);
+  const m = url.match(/\/([a-zA-Z0-9._-]+)\.md$/);
   if (m) {
-    const entry = ENTRIES.find((e) => e.date === m[1]);
+    const entry = ENTRIES.find((e) => e.version === m[1]);
     if (entry) {
       return new Response(entryMarkdown(entry), {
         status: 200,

package/voice/voice-notes.example.md

@@ -0,0 +1,16 @@
+# Voice notes — recent corrections
+
+This file overrides `voice-profile.md` wherever they conflict. Put your most recent,
+explicit corrections here — the things you keep having to fix in generated entries. Keep
+it short and specific; it is read every time an entry is generated.
+
+## Defaults (safe to keep)
+- Write for the reader, not as a diary. Lead with the change and its impact, not "I".
+- No em dashes; use a comma or semicolon.
+- No tacked-on punchy filler lines and no rhetorical fragment lists for rhythm.
+- Never invent metrics, motivations, or outcomes the commits don't support.
+- A release entry is a release note, not a changelog dump — group commits into the
+  handful of changes that actually matter and explain why.
+
+## Your corrections
+(Append your own as they come up.)

package/voice/voice-profile.example.md

@@ -0,0 +1,37 @@
+# Voice profile — (your name)
+
+This is the fallback voice profile devlog uses when no other profile is found. It is
+generic. Replace it with your own — or, better, point `voicePath` in `config.json` at a
+richer profile you already maintain (e.g. ghostwriter's `voice/`). **`voice-notes.md` in
+the same directory overrides this file wherever they conflict.**
+
+devlog reads only `voice-profile.md` and `voice-notes.md`. It never reads `algorithm.md`
+(LinkedIn reach tuning) — a dev log is not a LinkedIn feed, so reach rules do not apply.
+
+## Voice & tone
+Warm, practical, honest. A builder writing release notes for people who follow along — no
+hype, no doom, no marketing gloss. Explain what shipped and why it matters in plain terms.
+
+## Sentence rhythm & structure
+- Short sentences, generous white space, one idea per line or per tiny paragraph.
+- Lead with the change, then the reason. Build to a crisp takeaway.
+- A short bullet list is fine to enumerate "what changed."
+
+## Openers (how to start a release entry)
+- A sharp statement of what shipped: "v0.3.0 makes the log release-driven."
+- A short framing of the problem the release solves.
+
+## Closers
+- A reframe or a genuine forward-looking line about what's next. Not a forced question.
+
+## Vocabulary & tics
+- Plain, modern, conversational; contractions; no corporate jargon or buzzwords.
+- Name real things: features, files, versions. Specifics over abstractions.
+
+## Emoji & hashtags
+- Emoji: sparing or none. Hashtags: none.
+
+## Never do
+- No hype words ("game-changer", "revolutionary"), no doom, no cynicism.
+- No corporate jargon, no fake humility, no fabricated metrics or motivations.
+- Don't pad. If a line isn't carrying weight, cut it.