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.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
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.Docs Health Check + Quick Wins
$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
Focused Section Rebuild
$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
Docs Partnership
$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
Paid Discovery
$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
Need something outside these packages? Just say what you need. Custom scopes are normal and expected.
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
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
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
1
Briefing / Discovery
We clarify goals, current state, target audience, and constraints. For larger or unclear scopes I recommend starting with Paid Discovery.
2
Access & Research
I get temporary access to the docs repository (and related code when needed) and study the current state.
3
Implementation
I work directly in the repository and open pull requests with clear descriptions.
4
Feedback & Iteration
One structured revision round is included. Additional rounds or significant scope changes may carry a revision fee.
5
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.
Selected Work (Portfolio)
-
This website was built as a documentation page with Mintlify, using docs-as-code principles.
Github Repo: @vinibarbosabr/thecoding-docs -
0xramp.app documentation built with Mintlify and fully engineered and edited by Vini B | thecoding
Github Repo: @0xramp-labs/0xramp-docs | Site: docs.0xramp - Minor contributions to @near/docs, @multiversx/mx-docs, @near-daos/sputnik-dao-contract, @p2pdotme/docs
Ready to start?
Book a briefing call
15–30 min briefing to align on goals and scope.
Send a brief
Prefer async? Send details via Signal, Telegram, or email.

