Developer tools template

Ferrule Docs

For a team that ships an API and writes its own docs. Black on paper with one red accent, a narrow reading column and code blocks that copy in one click.

Opens the prompt in Crisp so you can change it before the build starts.

The look: Paper and Ink.

Quiet and editorial: black on paper, one red accent, words first. Headings in Instrument Serif, text in Inter.

  • background
  • surface
  • foreground
  • primary
  • accent
Opening
editorial: oversized type that fills the width, a thin rule under it, a short lede in a narrow column
Sections
numbered sections separated by hairline rules, generous margins, an index-style list of work or posts
Motion
reveal on sections only, no other motion
Texture
none; hairline rules carry the structure

The screens.

  1. 01Docs home
  2. 02Docs page
  3. 03Search
  4. 04API reference
  5. 05Pages
  6. 06Editor
  7. 07Feedback
The prompt Crisp receives
Build a documentation site for our developer product, Ferrule, an API for sending text messages. Developers read it; three people on our team write it. Data: sections (title, order), pages (section, title, slug, summary, Markdown body with code blocks, order, updated at, status: draft or published), code samples (page, language: curl, JavaScript or Python, body) and feedback (page, helpful yes or no, comment, date). Screens in order. The docs home: an oversized title, a thin rule, a one-line lede and a search box, then the sections as a numbered index of their pages. A docs page with the section tree in a left sidebar, the body in a narrow reading column, code blocks with language tabs and a copy button, a table of contents on the right, previous and next links, and a Was this helpful row. Search: results as you type across titles, headings and body text, the match shown in context, opened from any page with a keyboard shortcut. An API reference listing each endpoint with method, path, parameters and a sample response. Behind sign-in, for writers: a page list with drafts, a Markdown editor with a live preview, and Feedback with a page header, a one-line summary, stat cards for published pages, helpful rate and comments this week, then the comments list. Seed five sections and about twenty pages of real-looking content: quick start, authentication, sending a message, delivery webhooks, errors and limits.
Use this template

What Crisp builds from it

  • A docs home, page layout and API reference
  • Search as you type with matches in context
  • Code samples in language tabs with a copy button
  • A Markdown editor with drafts and live preview
  • Page feedback with a helpful rate

Change the name, the town and the details to yours before you start. How a build works.

More developer tools templates.

  • Steadyline Status

    One honest page that says what is working and what is not

  • Hookcatch

    See exactly what a webhook sends before you write the handler

  • Patternbox

    Test a pattern or tidy some JSON, then share it with one link

Every template