Discussion: process for refactoring docs
Best process for CTRT refactoring of new doc
I'm interested in everyone's thoughts about a good process to follow when the team starts refactoring new feature doc for CTRT. With the understanding that the author is the technical DRI, and the writer is the wording/format/organization/style DRI, how will this work best? I've spoken with several of you about this topic already but would like to get everyone's input.
One idea for new docs that need a lot of changes is to correct any egregious errors, merge, and then open a new MR for the larger editing and reorganization work. This new MR (or maybe the original one?) would be labeled docs-technical-debt. Tech debt here indicates new content that is merged that doesn't follow style guidelines or CTRT organization. (And just as an aside, not every page will have all four kinds of content type.)