Breaking down those long-tailed topics was pretty brutal.
I found some advice I wrote about the manual way (though I appreciate that there are multiple ways to tackle the job) and thought it could be fun/useful to compare against the AI assisted version:
Splitting these theme component topics out into digestible ‘one issue per topic’ chunks is what I’ve been aiming for. It is a little slow-going though.
Ideally, when I tackle one I’m looking to:
Update the OP to match the current ‘style’ with the settings and hosted blurb included (eg.DiscoTOC - automatic table of contents )
Update and name screenshots
Refresh and include info on any new features
For the replies, ‘one issue per topic’ as if they were created in their respective categories and tagged properly from the get-go. I’m looking to preserve Support UX Feature Dev Bug completed
Also, contemplate whether something requires a guide. Not normally one for theme components, but this one may fit the bill.
Sometimes a post can contain multiple issues. This can make splitting harder, but I try and handle the easy ones first and thin the replies out before weighing up what to do with the more muddled ones.
Reset bump date is also a big friend of mine.
6 个赞
Something like this would have helped immensely. 