A design for filing three kinds of notes (ideas, problems and thoughts), making them easy to create and read, and showing them on each project's homepage. A note can belong to a project, or to none. This is a plan to review, not built yet.
A new code page should show up in goatboat (and so in /tests, feeds and the tree) as soon as I save the file, with no commit or push. This doc is the design. It's a plan to review, not built yet.
The by-day stream with one article and one code page, punctuated different ways. The day heading carries the date, so each entry's line shows the time.
Slashes
The current one: [… N words] on its own line, then time / project / tags.
Entries grouped under a day heading, the word count in brackets right where the opening stops, then a small date / project / tags line and a hairline before the next entry.
A design for filing three kinds of notes (ideas, problems and thoughts), making them easy to create and read, and showing them on each project's homepage. A note can belong to a project, or to none. This is a plan to review, not built yet.
A new code page should show up in goatboat (and so in /tests, feeds and the tree) as soon as I save the file, with no commit or push. This doc is the design. It's a plan to review, not built yet.
A new code page should show up in goatboat (and so in /tests, feeds and the tree) as soon as I save the file, with no commit or push. This doc is the design. It's a plan to review, not built yet.
A design for filing three kinds of notes (ideas, problems and thoughts), making them easy to create and read, and showing them on each project's homepage. A note can belong to a project, or to none. This is a plan to review, not built yet.
A new code page should show up in goatboat (and so in /tests, feeds and the tree) as soon as I save the file, with no commit or push. This doc is the design. It's a plan to review, not built yet. Goatboat knows about code pages (src/app//page.tsx in the site) only through the routes sync. Today that runs in…
A design for filing three kinds of notes (ideas, problems and thoughts), making them easy to create and read, and showing them on each project's homepage. A note can belong to a project, or to none. This is a plan to review, not built yet. - Three kinds of page: ideas (features I'd like), problems (things that are broken or…
A report from an agent, written from one listpages call through the goatboat MCP server against local goatboat: One call returned exactly the pages that need work, with enough context to write each description. No page had to be opened. 8 pages under /docs have no description. Across the whole site, 27 of 126 pages are missing one. Path Status…
A new code page should show up in goatboat (and so in /tests, feeds and the tree) as soon as I save the file, with no commit or push. This doc is the design. It's a plan to review, not built yet.
A design for filing three kinds of notes (ideas, problems and thoughts), making them easy to create and read, and showing them on each project's homepage. A note can belong to a project, or to none. This is a plan to review, not built yet.
One paragraph per page with the title in bold at the start. The densest option.
Dev sync: new pages appear while I work. A new code page should show up in goatboat (and so in /tests, feeds and the tree) as soon as I save the file, with no commit or push. This doc is the design. It's a plan to review, not built yet. Goatboat knows about code pages (src/app//page.tsx in the…
Ideas, problems and thoughts. A design for filing three kinds of notes (ideas, problems and thoughts), making them easy to create and read, and showing them on each project's homepage. A note can belong to a project, or to none. This is a plan to review, not built yet. - Three kinds of page:…
MCP read report: pages without a description. A report from an agent, written from one listpages call through the goatboat MCP server against local goatboat: One call returned exactly the pages that need work, with enough context to write each description. No page had to be opened. 8 pages under /docs have no description. Across the whole…
A new code page should show up in goatboat (and so in /tests, feeds and the tree) as soon as I save the file, with no commit or push. This doc is the design. It's a plan to review, not built yet.
A design for filing three kinds of notes (ideas, problems and thoughts), making them easy to create and read, and showing them on each project's homepage. A note can belong to a project, or to none. This is a plan to review, not built yet.
A new code page should show up in goatboat (and so in /tests, feeds and the tree) as soon as I save the file, with no commit or push. This doc is the design. It's a plan to review, not built yet. Goatboat knows about code pages (src/app//page.tsx in the site) only through the routes sync. Today that runs in…
A design for filing three kinds of notes (ideas, problems and thoughts), making them easy to create and read, and showing them on each project's homepage. A note can belong to a project, or to none. This is a plan to review, not built yet. - Three kinds of page: ideas (features I'd like), problems (things that are broken or…
A report from an agent, written from one listpages call through the goatboat MCP server against local goatboat: One call returned exactly the pages that need work, with enough context to write each description. No page had to be opened. 8 pages under /docs have no description. Across the whole site, 27 of 126 pages are missing one. Path Status…
A new code page should show up in goatboat (and so in /tests, feeds and the tree) as soon as I save the file, with no commit or push. This doc is the design. It's a plan to review, not built yet.
A design for filing three kinds of notes (ideas, problems and thoughts), making them easy to create and read, and showing them on each project's homepage. A note can belong to a project, or to none. This is a plan to review, not built yet.