Once we update our flow, we need to make sure our doc is up to date
this can be parent ticket for all docs to track
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T407924 [Epic] Update documentations | |||
| Open | None | T408232 Silverpop/Acoustic documentation | |||
| Declined | None | T408244 Email Pref Center documentation | |||
| Open | None | T409246 Update exchange rate doc | |||
| Open | None | T410588 Donor Portal documentation | |||
| Resolved | AnnWF | T421142 Document Contact Save Logic |
Event Timeline
Comment Actions
In talking to Krobinson, she affirms that stakeholder teams should do documentation relevant to their function. "We do all of our own, and its not fr-tech's job to understand how we will use it to know what functionalities we need to document as users. That said, we obviously need support on understanding the workflows etc" She adds " However, we need to ensure that step is built in as part of release - we need time to test and use the platform / functionality / whatever to then document."
I still agree we need clear internal process on how and what we document for and with stakeholders. cc: @KHill-WMF