Activity tagged “documentation”
Some good suggestions for managing and customizing the Sphinx -> LaTeX -> PDF pipeline.
Pylons'/Pyramid's new unit testing guidelines. *Very* good stuff here.
A nice outline for how open source code documentation might be organized. I'm less than convinced that there needs to be a “standard,” but as a sort of conceptual framework for organizing docs this does a great job.
Swiss Army knife of markup formats. I'm bookmarking this specifically because it can convert HTML into reST, which I've not seen before. That means it'll be incredibly useful for converting old docs into Sphinx.
We rock, and now I've got statistics to prove it.
Great guide to upgrading from pre-1.0 django.comments to the version in 1.0.It's quite a bit better than the one in the docs, which probably means I should ask Patrick if I can adapt this into the documentation proper.
Some nice notes on how the Sphinx templates are laid out.
The new toolchain for the Python docs. Lots of smart stuff going on in here.
How to script conversion of documents through OpenOffice (and a big wad of duct tape). Works with NeoOffice, too!
Info about Postgres' stats collector and associated views. I just discovered the pg_stat_user_tables and pg_stat_user_indexes views which are amazingly helpful.
YA python to API doc tool. But this one's by mwh, so it's likely a cut above.
A quick tip to automatically regenerate your Sphinx docs as you make changes.
If you really want to produce great documentation, it needs to be edited.
How to develop a great technical writing style.
Tech docs can take a bunch of different forms ranging from high-level overviews, to step-by-step walkthroughs, to auto-generated API documentation. Unfortunately, no single format works for all users; there’s huge differences in the way that people learn, so a well-documented project needs to provide many different forms of documentation. This is the first in a series of posts that’ll cover the art of writing good technical documentation.