> ## Documentation Index
> Fetch the complete documentation index at: https://thecoding.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Documentation Engineering

> Docs health checks (audits), focused section rebuilds, and ongoing documentation ownership for blockchain and Web3 teams. Docs-as-code, practical, and built for both humans and LLMs.

# Documentation Engineering

Clear, accurate documentation is one of the highest-leverage investments a technical team can make — and one of the easiest to under-invest in.

I help teams turn complex products and protocols into documentation that users and developers can actually understand, use, and share: well-structured, technically precise, practical, and ready for both humans and LLMs.

The focus is always the same: reduce friction for users and builders and make your product easier to understand, use, integrate, and trust.

<Tip>
  Available for one-off health checks, focused section rebuilds, or ongoing part-time ownership.
</Tip>

## Docs-as-Code Engagement

I work with **docs-as-code** principles and treat documentation as an essential product surface.

Typical work includes:

* Reviewing and improving existing documentation through pull requests
* Fixing broken or outdated flows and adding practical examples
* Rebuilding high-value sections (Getting Started, core concepts, key integrations)
* Improving structure and clarity for both human readers and LLMs
* Aligning documentation with the actual code and product behavior
* Ongoing ownership so docs stay accurate as the product evolves

I read the code, test the flows, and implement the improvements myself.

## Pricing

All prices are in USD. Payments are via **NEAR Intents** — you pay in the token and network you prefer, I receive in the token and network I prefer.

<CardGroup cols={2}>
  <Card title="Docs Health Check + Quick Wins" icon="magnifying-glass">
    **\$925**

    * Broad review of the full documentation surface
    * Priority given to critical paths
    * Implementation of the highest-leverage fixes via PRs
    * Examples, clarity, broken steps, small structural improvements, LLM-friendliness
    * Short summary + prioritized backlog of deeper work

    Best starting point when you want fast, visible improvement.
  </Card>

  <Card title="Focused Section Rebuild" icon="layer-group">
    **\$2,150**

    * Deep work on 1–3 high-value sections
    * Thorough research and testing of those sections
    * Possible restructuring + major rewrite
    * Complete examples, edge cases, and strong structure
    * Delivered via well-described pull requests

    Best when specific critical sections need to become excellent.
  </Card>
</CardGroup>

<CardGroup cols={2}>
  <Card title="Docs Partnership" icon="arrows-rotate">
    **\$1,500 / month**

    * Ongoing part-time ownership of a defined documentation surface
    * Continuous updates aligned with product changes
    * Prioritized backlog management
    * Regular progress check-ins

    Ideal for teams that ship often and want docs to keep pace.
  </Card>

  <Card title="Paid Discovery" icon="compass">
    **\$350**

    * Short engagement to understand the current state
    * Optional small goodwill fixes
    * Clear written recommendation of the highest-value next step
    * Fee credited if we proceed into a larger package

    Low-risk way to get a concrete plan.
  </Card>
</CardGroup>

<Note>
  Need something outside these packages? **Just say what you need**. Custom scopes are normal and expected.
</Note>

## Engagement models explained

### 1. Docs Health Check + Quick Wins

I review the **entire** documentation surface, with special attention to the most important journeys (Getting Started, core concepts, main integrations).

I then implement the highest-leverage improvements that can be done relatively quickly through pull requests. Typical work includes:

* Fixing broken or outdated steps
* Adding practical code examples
* Improving clarity and structure
* Better alignment between code and docs
* Making key pages more self-contained and LLM-friendly

This is **breadth + prioritized implementation**. It is not a full rewrite of major sections.

### 2. Focused Section Rebuild

We deliberately choose 1–3 high-value sections. I go deep on those sections only:

* Thorough research and real testing of the flows
* Possible restructuring of the information architecture
* Major rewrite or complete rebuild of the chosen sections
* Rich examples, edge cases, and strong progressive disclosure

This is **depth on a defined surface**.

<Tip>
  When a Health Check has already been completed, the research phase is largely done. In that case I re-quote the Focused Section Rebuild at a lower fixed price that reflects the work already completed.
</Tip>

### 3. Docs Partnership (Ongoing)

Part-time, continuous responsibility for keeping a defined area of the documentation accurate and useful as the product moves.

### 4. Paid Discovery

A short, fixed engagement that produces a clear recommendation of the highest-value next step (usually a Health Check or a Focused Section Rebuild). The fee is credited if we proceed.

## How I work

<Steps>
  <Step title="Briefing / Discovery">
    We clarify goals, current state, target audience, and constraints. For larger or unclear scopes I recommend starting with Paid Discovery.
  </Step>

  <Step title="Access & Research">
    I get temporary access to the docs repository (and related code when needed) and study the current state.
  </Step>

  <Step title="Implementation">
    I work directly in the repository and open pull requests with clear descriptions.
  </Step>

  <Step title="Feedback & Iteration">
    One structured revision round is included. Additional rounds or significant scope changes may carry a revision fee.
  </Step>

  <Step title="Delivery & Next Steps">
    Work is merged (or ready to merge). I provide a short summary and, when relevant, a clear recommendation for the next highest-value engagement.
  </Step>
</Steps>

Most Health Checks take 1–2 weeks.
Focused Section Rebuilds usually take 2–3 weeks depending on scope.

Urgent work can be prioritized under a **prioritization fee** of +25%.

<Tip>
  After a Health Check or Focused Section Rebuild, some teams also commission a [sponsored technical article or tutorial](/technical-writing) to increase visibility of the improved documentation. The two services often reinforce each other.
</Tip>

## Selected Work (Portfolio)

* **This website** was built as a documentation page with Mintlify, using docs-as-code principles.\
  Github Repo: [@vinibarbosabr/thecoding-docs](https://github.com/vinibarbosabr/thecoding-docs)

* **0xramp.app** documentation built with Mintlify and fully engineered and edited by Vini B | thecoding\
  Github Repo: [@0xramp-labs/0xramp-docs](https://github.com/0xramp-labs/0xramp-docs) | Site: [docs.0xramp](https://0xramp-docs.mintlify.site)

* Minor contributions to [@near/docs](https://github.com/near/docs), [@multiversx/mx-docs](https://github.com/multiversx/mx-docs), [@near-daos/sputnik-dao-contract](https://github.com/near-daos/sputnik-dao-contract), [@p2pdotme/docs](https://github.com/p2pdotme/docs)

## Ready to start?

<CardGroup cols={2}>
  <Card title="Book a briefing call" icon="calendar" href="https://cal.com/vinib">
    15–30 min briefing to align on goals and scope.
  </Card>

  <Card title="Send a brief" icon="envelope" href="/contact">
    Prefer async? Send details via Signal, Telegram, or email.
  </Card>
</CardGroup>

<Tip>
  Check the [**Recommendations & Endorsements**](/endorsements) page for real testimonies from other clients and partners.
</Tip>