How to Document your Technical Projects

Maximus Soares
November 14, 2024
3 min

Why good documentation matters

Let’s talk documentation—often overlooked, but absolutely essential. Good documentation isn’t just a nice to have; it’s what makes your project accessible, relatable, and impactful. Whether you're a career switcher, seasoned dev, or new to tech, documentation is what takes your project from good to great. Here’s how to create great documentation that can boost your projects and career.

Start with the purpose of your documentation

Before you get writing, ask yourself—who’s this for?

  • For recruiters: This is your spotlight moment. Show you’re not just a coder, but someone who can think, communicate, and reflect. Highlight what you built, your thought process, key learnings, and any tough calls or limitations. Show that you understand the bigger picture—things like scalability and security.
  • For users: Keep it simple, keep it clear. A quick start guide, straightforward instructions, and a troubleshooting section will save your users’ day. They want answers, not a novel.
  • For contributors: Help them help you. Include step-by-step guides for setting up your project, coding standards to keep things clean, and an easy-to-follow submission process. The smoother you make it, the more people will jump in to contribute.
  • For Yourself: Trust me, future you will thank you. Document your process, lessons learned, resolved errors, and key decisions. Not only does this help you improve, but it also keeps your project from turning into an unsolvable puzzle when you revisit it later.
Documentation structure

What to include in your documentation

Here are the key pieces of documentation that make your project stand out:

  1. Overview: Give a snapshot of what your project does, why it matters, and its main features. This helps people quickly grasp the value.
    ⚒️ Adjust this based on audience or purpose—keep it high-level for users, more detailed for contributors or recruiters.
  2. Installation instructions: Provide clear, step-by-step guidance for setting up the project. Sharing your thought process here adds depth.
    ⚒️ Adapt the level of detail depending on whether you're aiming this at contributors or recruiters.
  3. Visual elements: Diagrams, screenshots, and other visuals can make your documentation clearer and more engaging. Use them to illustrate complex processes, workflows, or project architecture.
    ⚒️ Use detailed diagrams for contributors and recruiters, and simpler visuals for user-focused documentation.
  4. Challenges and decisions: Mention the obstacles you faced and the choices you made along the way. This shows problem-solving skills and transparency.
    ⚒️ Include more details if this is aimed at recruiters or contributors.
  5. What you’ve learned: Highlight the key takeaways and any new skills you gained. This shows growth, which recruiters love.
    ⚒️ For personal use or recruiters, emphasize learnings and improvements.
  6. Considerations: Add notes on things like scalability or security to show that you’re thinking ahead.
    ⚒️ Go deeper for contributors and recruiters, keep it light for user-facing documentation.
  7. References: Include supporting materials like technical articles, documentation links, code repositories, or community discussions that informed your project. This adds context and credibility to your work.

What to avoid ❌

❌ No documentation: The biggest mistake is not having any documentation at all. Start simple with an overview, setup instructions, and a usage guide. Even the basics are better than nothing!

❌ Excessive Length (when unnecessary): Be concise when quick guidance is needed, but in-depth documentation can be essential for complex projects. Use headings, bullet points, and visuals to make longer sections easy to navigate.

❌ Vague explanations: Be specific. Adjust your level of detail based on your audience—break down terms for beginners, and keep explanations concise but clear for experienced audiences.

What to Do with It

Once you’ve polished your documentation, make sure it’s visible:

  • Blog Platforms like Medium, LinkedIn, or Substack: Share your work, and insights and share within your community!
  • A personal portfolio website: Show off your skills and projects where recruiters and collaborators can easily see them.
  • GitHub repository: Keep it accessible for users and contributors.
  • YouTube: Tutorials and walkthroughs add a visual, interactive touch.

The Right Tools for the Job

Good documentation takes effort, but smart tools can help. Platforms like nextwork.org streamline the process by pulling together your learnings, screenshots, and guides automatically. This way, you can spend less time on admin tasks and more on building great projects. Otherwise, you can use a robust text editor like Google Docs, Notion or Word, where you can paste images and apply some formatting too!