question : is site copy vs faq still a useful division of the teams? (ditto site copy vs faq vs editing, although I can more easily see the utility of 'generate new thing' vs 'polish existing thing')
I have no immediate idea what I should/could be working on (- apart from maybe copying into comments the email-to-self I have of things I have thought while looking at the FAQs, which I haven't done because I don't want to tread on toes in the faq team.) Transfer to the editing team, I guess, as I don't feel like I know enough detail to generate guides / faqs? Sweeping for terminology, naming, and trying to focus on accessibility sounds both manageable and never ending :)
I have thoughts / questions about getting and responding to feedback from users about the site copy and FAQ, but I'm not sure I can pin them down in words right now, but one of them is:
Do we / can we get access to the search text people use on the site, when they're searching the 'faq' set? I suspect that would be useful in seeing what people are finding themselves needing to know (both topic and terminology)
(How might feedback from the support and abuse teams filter back to docs? Do we want a formal-ish PM-direct-answer system, or to invite users who spot things that are wrong / unclear / could be better to post to / comment to a community or wiki where the discussion is publicly visible? How does the existing wiki fit into the future plans for the site documentation/planning/KB?)
no subject
I have no immediate idea what I should/could be working on (- apart from maybe copying into comments the email-to-self I have of things I have thought while looking at the FAQs, which I haven't done because I don't want to tread on toes in the faq team.) Transfer to the editing team, I guess, as I don't feel like I know enough detail to generate guides / faqs? Sweeping for terminology, naming, and trying to focus on accessibility sounds both manageable and never ending :)
I have thoughts / questions about getting and responding to feedback from users about the site copy and FAQ, but I'm not sure I can pin them down in words right now, but one of them is:
Do we / can we get access to the search text people use on the site, when they're searching the 'faq' set? I suspect that would be useful in seeing what people are finding themselves needing to know (both topic and terminology)
(How might feedback from the support and abuse teams filter back to docs? Do we want a formal-ish PM-direct-answer system, or to invite users who spot things that are wrong / unclear / could be better to post to / comment to a community or wiki where the discussion is publicly visible? How does the existing wiki fit into the future plans for the site documentation/planning/KB?)