Froware Re-release

[okbrown]

As part of our re-release activities this epic is to group the key stories, tasks & issues that need to be addressed and completed to re-release the site.

Things to define:

• what does done mean for the team?
• risks
• define the how technically and non-technical tasks are worded

Loose high level summary of what needs to done:

• Disable both public facing Froware sites (Wordpress site and Discourse forum) @Genyus
• Provide an engagement homepage for prospective content providers/publisher @MikeDre
• Update home page articles with community meta data @Genyus
• Provide user logged in call to actions for non-logged in users
• Update Events Calendar UI with Froware styling
• Source images/photography/iconography for design and partial style guides
• Accessibility options on text, text on images and other a11y
• Re-define/review all pages of site, taking a UX/UI approach (wireframes) @MikeDre
• What have i missed?

[Genyus]

My thoughts on the points requiring clarification:

Definition of "Done"

• Integration tests written and passing
• UI tested on major platforms/browsers
• Accessibility review completed
• Changelog updated
• Deployed to production

Risks

• Inaccurate/incomplete estimations
• Miscommunicated requirements/expectations
• Insufficient time commitment

Wording

Technical tasks

I tend towards standard user stories with Gherkin-formatted acceptance criteria

Non-technical tasks

I don't have a specific format I'd use, any suggestions?

[okbrown]

Fully agree, very used to this way of working.
Gherkin is very close to my current way, but I like this much more, thanks!

Non Technical, I guess would end up being the same in that sense.