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

# Developer Education

> Developer education for web3 teams: tutorials, technical articles, onboarding paths, workshops, and education-shaped DevRel delivered through clear, tested, practical work.

Developer education helps people understand, adopt, and succeed with your product. It includes tutorials, guides, learning series, technical articles, workshops, talks, onboarding paths, and education-shaped developer relations work.

This lane is a good fit if your users or developers are not getting enough support from your existing materials, or if your content does not match what the product actually does. It is not a good fit if you are looking primarily for reach, promotion, or community moderation.

## Two delivery models

<CardGroup cols={2}>
  <Card title="Your channels" icon="pen-nib">
    **Ghostwriting or guest authoring**

    I research, write, and help you publish technical content under your brand or as a guest author. The content builds your own documentation, blog, or developer-education asset.

    IP belongs to you. Scope is quoted per project, using a \$65/h base rate as reference.
  </Card>

  <Card title="My channels" icon="bullhorn">
    **Sponsored Technical Content**

    I research, write, and publish a disclosed sponsored piece on thecoding channels, such as Substack and X. This can include articles, tutorials, and follow-up content where appropriate.

    The work is disclosed as sponsored. Fixed packages apply, and pricing is listed below.
  </Card>
</CardGroup>

For most teams building their own long-term developer audience, **content on your channels is the recommended default**. Sponsored placement on my channels can be useful when you want an external explanation, launch support, or a disclosed third-party perspective.

## Products

<CardGroup cols={2}>
  <Card title="Consulting / Review Sprint" icon="comments-dollar">
    **\$350 · \~1 week**

    * Review of short technical content or a content strategy
    * Clear written recommendations
    * Technical communication strategy support, including crisis communication

    Best when you need focused feedback before investing in a larger project.
  </Card>

  <Card title="Tutorial / How-to" icon="book-open">
    **\$500 · \~2 weeks**

    * 1,000 to 2,000 word tutorial or how-to guide
    * Research and real testing of the product or feature
    * Clear steps, examples, and a brief technical introduction
    * Priced for a shorter, execution-focused format

    Best for one practical task developers or users need to complete.
  </Card>
</CardGroup>

<CardGroup cols={2}>
  <Card title="Standard Research Article" icon="file-lines">
    **\$650 · \~2 weeks**

    * 2,000 to 3,000 word technical article
    * Deep research and accurate explanations
    * Code snippets and practical visuals
    * One structured revision round

    Best for product explainers and feature deep-dives.
  </Card>

  <Card title="Pro Research Article" icon="trophy">
    **\$850 · \~2 weeks**

    Everything in Standard, plus:

    * Deeper source-code analysis
    * 1 to 3 concrete GitHub issues with documentation or DX suggestions
    * Stronger visual support and an animated cover where useful
    * Short video follow-up commenting on the piece

    A good default for teams that want the article to feed future documentation or developer experience work.
  </Card>
</CardGroup>

<CardGroup cols={2}>
  <Card title="Technical Education Sprint" icon="graduation-cap">
    **\$1,850 · \~3 to 4 weeks**

    * Series of practical tutorials or educational pieces
    * Based on real developer use cases
    * Code examples, diagrams, and clear explanations
    * Delivered as content, docs sections, or both

    Best when you need educational material developers can actually follow.
  </Card>

  <Card title="Workshops, Talks & Events" icon="users">
    **from \$750 · Scoped per event**

    * Technical talks and presentations
    * Hands-on workshops, remote or in person
    * Support for hackathons and developer events
    * Preparation, materials, and follow-up scoped by format and duration

    Best for education, onboarding, and live developer engagement.
  </Card>
</CardGroup>

<CardGroup cols={2}>
  <Card title="Onboarding & DX Sprint" icon="route">
    **\$2,450 · \~4 to 5 weeks**

    * Review and improvement of the critical developer path
    * Getting Started and key integration journeys
    * Documentation improvements and supporting content
    * Practical recommendations, with implementation via pull requests where possible

    Best when new developers struggle or support load is high.
  </Card>

  <Card title="DevRel Partnership" icon="arrows-rotate">
    **\$3,500 / month · Ongoing (60h / month cap)**

    * Ongoing part-time developer education
    * Regular content, workshops, or developer touchpoints
    * Explicitly scoped developer feedback loops
    * Prioritized backlog of developer experience improvements

    I work in focused blocks, typically reserving 15 hours per week per client. Best for teams that want practical DevRel without a full-time hire.
  </Card>
</CardGroup>

## How I work

<Steps>
  <Step title="Briefing">
    You share the product, audience, problem, and goal. We align on angle, depth, and constraints.
  </Step>

  <Step title="Research and testing">
    I study the product, documentation, code where relevant, and developer flows. If the work involves a tutorial or onboarding path, I test the steps.
  </Step>

  <Step title="Execution">
    I write, build, or prepare the material. Depending on the project, this may be delivered as a draft, pull request, published article, workshop plan, or event material.
  </Step>

  <Step title="Revision and handoff">
    One structured revision round is included. You receive the final material and, when useful, notes on next steps.
  </Step>
</Steps>

Most content engagements take about one to four weeks. Workshops and talks are scheduled according to the event and preparation needs. Timelines are conservative and assume normal capacity. Prioritized delivery is available for +25%.

## What makes this work useful

* I read the code and documentation rather than summarizing marketing material.
* I test flows when the project involves tutorials or onboarding.
* I write for developers and users who need to do something, not just admire something.
* I keep the structure clear, accurate, and honest about limitations.
* I can connect content work to documentation and developer experience gaps.

Many education projects reveal documentation problems. If that happens, the next step may be a [Docs Health Check or Focused Section Rebuild](/documentation).

## Selected work

Proof is shown on [Work](/work), with context, what shipped, and what was not done. Education-related examples include:

* Multiple technical articles and tutorials published on Substack and X, including sponsored work for Dash and Quai.
* Educational writing and mentorship connected to MultiversX community education in Brazil, during a past volunteer role.
* Guest authorship for the MultiversX blog, HackenProof, and Nano Foundation materials.
* Workshops, talks, and developer education work in online and in-person settings.

If a project is self-serve, volunteer, or limited in scope, I say so.

## Related pages

* [Documentation Engineering](/documentation) for docs audits, rebuilds, and ongoing docs ownership.
* [Pricing](/pricing) for the full catalog and terms.
* [Work](/work) for case cards.
* [Endorsements](/endorsements) for client feedback.

## Ready to start?

<Card title="Send a brief" icon="envelope" href="/contact" horizontal>
  Tell me the product, the surface that hurts, and your timing. Five lines are enough.
</Card>

Prefer talking first? [Book a 20-minute briefing](https://cal.com/vinib).