Document360

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Build me the documentation site I actually need instead of Document360.

Static site generators solved the publishing half years ago and do it better. The parts worth building are the workflow around them and the measurement afterwards.

STACK
- Astro with content collections, or Docusaurus, for the site itself
- Node 20+ with Fastify for the small dynamic half — search analytics, feedback, the reader's own signals
- SQLite through better-sqlite3, WAL mode
- Pagefind for search, built at build time, served statically
- Caddy in front

THE CONTENT
- Markdown in git, one file per article, with frontmatter: title, description, version, owner, reviewed_at, status
- Versions as directories, with a version switcher; **an unversioned documentation site is one that lies to everybody on an older release**
- Review through pull requests. That is the workflow the paid product is selling and you already have it

SEARCH THAT DOES NOT COST ANYTHING
- Pagefind builds an index at build time and serves it as static files — no search service, no index to keep in step, works on a static host
- Weight the title and the headings above the body
- **Log every query and every empty result to your small server.** That log is the entire content roadmap: the questions people ask that your documentation does not answer

THE READER
- One column, a sidebar that shows where you are, a table of contents on the right, and a search box focused by pressing slash
- Every code block copyable, and tabs for the languages
- Fast: this is documentation, and a person is reading it because something is broken

MEASUREMENT, WHICH IS THE PART PEOPLE SKIP
- 'Did this answer your question' on every page, yes or no plus an optional line. **The no's with comments are the highest-value editorial input you will ever get**
- Search queries with no result, and searches followed immediately by another search
- Time on page is noise here; the answer signal is not

KEEPING IT CURRENT
- reviewed_at in the frontmatter and a build warning for anything past its interval
- A stale banner on the page itself once it lapses, because a reader deserves to know
- Broken internal links fail the build; broken external links appear in a weekly report

WHAT MATTERS MOST
The empty-search log and the per-page answer signal. Publishing is solved; knowing what to write next is not.