It should not take more than a few minutes to know how to read and write documentation.
Documentation is more than you think
Everything that is involved in making great documentation everywhere and all at once.
Civboot
Let's work together to create and refine a public domain tech stack which enables learning through simple but powerful software. This project is for students, teachers, professionals, and creators to use for learning and to supercharge their personal development stack.
Full featured documentation deployment platform
Read the Docs is a documentation building and hosting platform aimed at helping developers creating documentation from code with versioned documentation, integrated search, pull request previews and more.
Making Documentation Simpler and Practical: Our Docs-as-Code Journey — Squarespace Engineering Blog
In the fast-paced world of software development, documentation often gets a bad rap. It's perceived as a chore, a necessary evil, and sometimes, unfortunately, an afterthought. But what if writing documentation could be as dynamic and collaborative as writing the code itself? What if it could be si
Docs as Code: The Best Guide for Technical Writers
Recently, my work has involved writing a lot of documentation and. Doing this has introduced me to...
civboot/notes/hardware.md at main · civboot/civboot
Civilizational Bootstraper: landing page and wiki. Contribute to civboot/civboot development by creating an account on GitHub.
Writing design docs – Ceejbot's notes
How to figure out what to do and tell your colleagues at the same time
Why good non-techie user documentation is vital for a wider embrace of the ATmosphere - Debbie's Blatherings - by Debbie Ridpath Ohi
Plus tips on writing good user documentation
What I'm building? - Cavu Reader - Pardy Time DevLog
Why I'm building an online ereader
Docs — Turn your team's content into knowledge
Docs is the open-source document editor that turns your team's content into knowledge: real-time collaboration, structured knowledge, and full data ownership. Self-host it anywhere, or try a public instance in seconds.
How I Ship Code Without Reading It — Daniele Salatti
Yesterday I shipped 1,300 lines of infrastructure code and I didn't read most of it. Docker images, a 9-phase build script, an egress proxy with per-phase network isolation, Nomad job templates, the whole thing. And no, it's not because I don't care. It's because I found something that (mostly) works better than reading.
i was annoyed that this isn't explained how i want in the docs so i wrote my own mini-guide to publishing lexicons:
atproto made simple: publishing lexicons
underreacted.leaflet.pubMy "Introduction to #ATProto" blog post that I've been working on for some time is ready 🙂 It goes through things like records, lexicons, DIDs, then PDS/AppView etc. and how it all works together. Let me know if anything is wrong! More parts later, with the Fedi comparisons & misconceptions etc.
Introduction to AT Protocol
mackuba.eu
