This is great. I'm relatively new Darktable but felt the need to refine the copy. Reducing written word down to its core parts does take time.
There's a saying, "Sorry I didn't have time to write less." :) About the choice between Hugo or Jekyll, I realize that some may like the speed of Hugo, but Jekyll does have incremental builds (I read that Hugo doesn't have that). In my experience working on sites with thousands of pages, by using the incremental build tag and limiting the number of languages on my local end, I would have a site I can re-test in a second or two. Hugo is written in Go also. That might be obvious from the name, Hu"go", but it probably isn't to most. So I suppose those who might want to do the documentation would need to access whether they want to use a Go binary over Ruby. J On 2020-10-19 02:44 UTC Mica Semrick <m...@silentumbrella.com> wrote: > Hey Torsten, > > Minimalism is a basic tenant of technical writing. We should strive to > convey the "thing" in question using the fewest words and image to (1) > reduce the maintenance overhead and (2) more words/images generally do > not make the "thing" clearer, in fact, quite the opposite. It often > muddies the picture. > > The current documentation has a colloquial verbosity to it that (I feel) > doesn't enhance the understanding of the reader. Similarly, there are > images that don't enhance the readers understand either, for instance in > the current documentation there is a image of every since module just > ahead of the textual description of that module. In the new docs, we've > split out module references into their own section and we assume you > have darktable open in front of you (or you know what a module generally > looks like) and thus we omit the image. > > If there are specific instances where you think not enough is written, > you are encouraged to open an issue. > > Hope that makes sense. > Hey Torsten, > > Minimalism is a basic tenant of technical writing. We should strive to > convey the "thing" in question using the fewest words and image to (1) > reduce the maintenance overhead and (2) more words/images generally do > not make the "thing" clearer, in fact, quite the opposite. It often > muddies the picture. > > The current documentation has a colloquial verbosity to it that (I feel) > doesn't enhance the understanding of the reader. Similarly, there are > images that don't enha ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
