Documentation, and a tool reference that cannot go stale
Pekan.cloud now has documentation. Until today the site could tell you what Pekan was and what had shipped in it, but nothing on it explained how to actually do anything: how to install it, how to wire a coding agent to a board, or what any of the views were for. Seven pages at pekan.cloud/docs.html close that gap.
The order is deliberate. Getting started covers installing the desktop app, the two local services it starts, creating a first project, and what a task record actually holds. Connect your agent comes second because it is the page that matters most: Pekan is a board people and agents share, and none of that works until an MCP client is pointed at it. That page covers what agent setup writes into your project, how Claude Code, Codex, and Mistral Vibe each connect, why Codex and Vibe go through the stdio proxy rather than a direct URL, and the two failures worth recognising when a connection does not come up.
From there, Views tours the board, roadmap, telemetry, triage inbox, workspace editor and terminal, Git, and the workspace-wide activity feed. Workflows and hooks explains reusable column templates, the review and done column roles that let agents talk about your board without knowing your column names, and the five hook actions that fire when a task enters or leaves a column. Agent actions covers the built-in actions and, more importantly, the propose and apply contract that decides whether a launched action may change anything. Roadmap and milestones covers goals, milestones, and why roadmap actions deliberately stop at a proposal.
The seventh page is the MCP tool reference, and it is generated rather than written. It reads the tool registrations out of the server source when the site is built, so all 42 tools and their descriptions are the ones the server actually exposes. A hand-maintained list would have started drifting the first time a tool was added or renamed, which is exactly what had already happened to the machine-readable summary the site serves to crawlers: it still advertised two views that were retired some releases ago. That summary has been corrected and now points at the documentation as well.
Behind the scenes the site finally became genuinely multi-page, so the navigation and footer moved into single shared partials instead of being copy-pasted per page. One useful side effect: the version number in the navigation is now read from the newest published release rather than typed by hand, which had quietly left it six releases behind.
Highlights
- A seven-page documentation section at pekan.cloud/docs.html, with a sidebar, per-page contents, and prev/next navigation.
- A dedicated guide to connecting Claude Code, Codex, Mistral Vibe, or any other MCP client to a project board.
- An MCP tool reference generated from the server source, so it cannot drift from the tools the server registers.
- Documentation written as Markdown in src/docs, built to static pages by the same kind of generator the changelog uses.
- One shared navigation and footer across the whole site, with the version number derived from the newest release.
- A corrected machine-readable site summary that no longer lists two retired views.