Techie BabajiLearn to Code. Build Real Skills.
Contributors wanted

Write for Techie Babaji

Know a topic well? Help future developers by turning it into a clear, practical lesson — with editorial support and full author credit.

Pitch a topicRead the guidelines

Why write for us

Help learners

Your lesson helps students and developers who are where you were a few years ago.

Author credit

Published lessons carry your name and a link to your profile, portfolio or GitHub.

Editorial support

An editor reviews your draft for accuracy and clarity, and helps shape it into the house style.

Learn by teaching

Explaining a concept step by step is one of the best ways to master it — and it makes a strong portfolio piece.

What we’re looking for

  • Full lessons for topics marked “Outline” in any tutorial track
  • Step-by-step guides for projects marked “Brief” in the project library
  • Real-world debugging stories: a bug, how you found it, how you fixed it
  • Interview questions with clear, accurate answers and follow-ups
  • Comparisons that help people choose (e.g. Signals vs RxJS, EF Core vs Dapper)
  • Deployment walkthroughs for Azure, AWS, Docker and Hostinger

Tip: open any tutorial track — topics labelled Outline are the ones we most need written.

Writing guidelines

Please do

  • Original work, written by you, not published elsewhere
  • Plain language a beginner can follow; define jargon on first use
  • Working, tested code examples with the expected output
  • State the versions you used (e.g. React 19, .NET 9)
  • Cover common mistakes and best practices

Please don’t

  • AI-generated or spun content passed off as your own
  • Promotional posts, affiliate links or paid backlinks
  • Copied code or text without permission and attribution
  • Untested snippets or outdated, deprecated APIs
Lesson structure

Every lesson follows the same shape: learning objectives → simple explanation → syntax → code example with expected output → step-by-step walkthrough → real-world use case → common mistakes → best practices → practice exercise → mini quiz. See Array Methods for an example.

How it works

  1. 1

    Pitch

    Send a topic and short outline with the form below.

  2. 2

    Review

    An editor checks that it fits the curriculum and replies with feedback.

  3. 3

    Write

    Draft the lesson using our lesson structure: objectives, explanation, example, steps, mistakes, exercise and quiz.

  4. 4

    Edit & test

    We verify every code sample and edit for clarity together with you.

  5. 5

    Publish

    Your lesson goes live with your byline and is linked from the relevant track.

Pitch your topic

0/4000

Contributor FAQ

Do I need to be an expert?
No. You need to understand your topic well enough to explain it accurately and test the code. Clear explanations from someone who recently learned something are often the most helpful.
Is this a paid opportunity?
Contributions are currently unpaid. You receive author credit with a link of your choice on every lesson you publish.
Can I republish my lesson on my own blog?
Please don’t republish the full lesson elsewhere, to avoid duplicate content. You are welcome to share a summary that links to the published lesson.
Which format should I write in?
Any format is fine for the first draft — a document, Markdown or a GitHub gist. Editors convert accepted drafts into the site’s lesson format.
Do you accept sponsored posts or link insertions?
No. We do not accept sponsored content, paid links or link insertions in existing lessons.