Tasks to be done for docs

There's a lot of ideas and jobs floating around. Here's a couple that I'm aware of:

  • "branch per version" is not a good use of branches. Personally I think a top-level directory per version is the way to go. Docs for one version should be able to link to other versions, as well as to common version-agnostic resources (e.g. glossary and assets such as logos).
  • Included files generate duplicate label warnings. Amazingly enough, we're not the first to run into this: Sphinx's .. include:: directive and “duplicate label” warnings.
  • Create glossary and index.

@svx :eyeglasses:

2 Likes

Plone Foundation Code of Conduct