{...}Zakir Matloob.
Book a Call
All work

Docs that stay honest · 2025

DevelopersDoc

A developer platform for creating, generating, and sharing documentation with code — scan a repo, write the runbook, publish it to the team.

Visit sitedevelopersdoc.com
DevelopersDoc

Scan a repository. The workspace writes a Project Overview from evidence — stack, routes, schema — then the rest of the docs can be edited, shared, and published.

Challenge

Documentation dies the moment the code moves. Architecture lives in someone's head, runbooks live in Slack, and access is a forwarded tab.

Approach

I built a workspace that scans the repository into a Project Overview, keeps team docs in one tree, and shares them with Owner / Editor / Viewer roles instead of a link that anyone can lose.

Outcome

Docs become an engineering surface: generated from evidence, edited like production work, and published with a role attached.

Next.jsTypeScriptPrismaClerkPostgreSQL
01

Beat 01 / 04

One tree instead of five tools

The snag.

Runbooks, generated project docs, and teaching notes scatter across Slack, Notion, and someone's laptop. New engineers inherit a scavenger hunt.

What ships.

Dashboard, Published Docs, Projects, and Your Docs sit in one sidebar. HarAik, Software Engineering, and AI Engineering are folders in the same workspace — searchable with ⌘K.

Developers Doc project workspace for HarAik with documents, members, and sync status
0104