Hi Steve,

To be honest, I have not had many problems with the 2.4 documentation myself, having recently upgraded from 2.3 to 2.4. While I will admit that the upgrade guide is a bit rough, the only real impracticality I have found is that the 2.3 documentation seems to have been taken down, leading to 404s more often than not when searching for topics still relevant in 2.4.

Perhaps you could share some concrete examples as to how the 2.4 documentation is lacking?

Steve Litt via dovecot schreef op 2025-07-12 14:45:
Are you planning to improve your Dovecot 2.4.x documentation? The
current 2.4.x documentation has:

* Non-obvious links between 2.4.x and 2.3.x
* Some 2.3.x specific grammar
* Almost no examples
* 2.4.x material is scattered across many pages
* Contains a few inaccuracies
* Contains some contradictions

2.4.x is such a huge change that it should have its own, standalone
documentation tree exclusively for 2.4.x. This tree should have a
different color scheme than your other docs so people know at a glance
exactly what they're looking at.

You could have a page devoted to often used dovecot.conf content,
with numerous examples, documented as if there had never been an
earlier version. You could have a page devoted to conversion of 2.3.x
dovecot.conf to 2.4.x, once again, with numerous examples. Another page
with more exotic dovecot.conf content, with numerous examples. Another
page discussing the 2.3.x features that don't appear in 2.4.x, what
capabilities that takes away, and how best to cobble together those
capabilities for those who don't want Dovecot Professional. Another
page for brand new capabilities of 2.4.x.

Thanks,

SteveT

Steve Litt
http://444domains.com

_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Met vriendelijke groeten,

William David Edwards

_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Reply via email to