Service
Improve the docs
I rework your quickstarts, references and examples so developers reach a working result faster.
I work in your docs stack and in your team's voice. When the project ends, your team owns docs it can keep up to date without me.
- Price
- From €170 plus taxes*For a single short page, about 2 to 3 hours at €85 per hour. Larger projects are estimated per scope and agreed in the proposal.
- Format
- Remote, in English or German
- You get
- Reworked docs, merged into your repository, and a handover
- Stack
How taxes work
For clients in Germany, 19% VAT is added to the invoice. For clients abroad, I invoice the net amount and you account for the tax in your own country, for example through reverse charge. Please make sure your business can do that.
Is this for you?
A good fit if one of these sounds familiar
- Your quickstart has more steps than anyone wants to follow.
- The reference is complete, but nobody finds what they need in it.
- Examples are fragments that don't run on their own.
- An audit showed what to fix, and now someone needs to do it.
What I work on
The parts developers read first
We pick the parts that matter most for your developers and agree on them before we start.
Quickstarts
The shortest honest path from zero to a first working result.
Tutorials and guides
Step-by-step paths for the tasks your developers actually have.
Reference structure
Clear headings, consistent pages and types you can rely on.
Examples and samples
Complete, runnable code that people can copy and build on.
Navigation
An information architecture that matches how developers search.
Docs tooling
Setup that keeps code samples tested and the docs easy to maintain.
What it looks like
The same steps, but clearer
An illustrative example of a quickstart, before and after.
## Getting started
1. Create an account and verify your email.
2. Create an organisation and a project.
3. Generate an API key in Settings > Security.
4. Clone the example repository.
5. Copy .env.example to .env and fill in six values.
6. Install dependencies and run the build.
7. Start the dev server and open the dashboard.## Send your first request
Time: about 5 minutes. You need Node 20+
and an account (sign up at example.com).
1. Get a test key: Settings > API keys.
Test keys can't touch production data.
2. Create the example app:
npm create example-app@latest
cd example-app
3. Add your key to .env (one value):
EXAMPLE_API_KEY=sk_test_...
4. Send the request:
npm run hello
You should see: { "status": "ok" }
Anything else? See Troubleshooting.
Next: build your first integration (10 min).How it runs
Four steps, one clear finish
- Step 1
Choose the journeys
We pick the developer journeys and pages that matter most, and agree on the scope.
- Step 2
Draft
I write and restructure in your repository, with runnable examples.
- Step 3
Review
Your team checks the drafts for accuracy, and I fold in the feedback.
- Step 4
Publish and handover
The new docs go live, and your team knows how to keep them that way.
What's not included
Being clear about scope is part of the deal.
- Changes to the product itself. I point them out, and your team builds them.
- Ongoing docs maintenance after the handover
- Pages outside the agreed scope
Common questions
Should we start with an audit?
Not necessarily. If you already know where developers get stuck, we can start here. If you don't, a DevEx audit makes the docs project more focused.
Do you work in our docs tooling?
Yes, I work in what you already use. I know Docusaurus, VitePress, Astro Starlight, MkDocs (especially with Material for MkDocs) and TypeDoc / JSDoc well.
Will the docs also work for AI coding assistants?
I write for people first. Clear structure, real headings, complete examples and explicit types are exactly what language models handle well, so they benefit anyway.
Which page do developers struggle with most?
Send me a link, and we'll talk about what a docs project could change.
Prefer email? Write to me directly