What's your preferred granularity of docs?
(a) A whole module on one page, e.g. https://pkg.go.dev/time, making search easy?
(b) A function per page, e.g. https://www.php.net/manual/en/function.time.php, giving more space for examples and See Also sections?
I'm torn, and I've seen both done well.
miniblog.
Related Posts
Pharo's git integration (using Iceberg) is shockingly good.
All your commits are well-structured changes, so you can toggle at class/method granularity what you want to commit. Thanks to Iceberg, these classes in your *live* image serialise to text files!
Today I learnt that Pharo has integrated history!
This isn't a VCS, this is just a convenient way of reverting changes at the granularity of a method ('message' in ST terminology). It's a good level of granularity (cf file-level undo in a text editor).
Squashing commits is great for s/w, but it perhaps not for blog posts. Seeing old drafts is valuable. Choosing granularity is hard though.