Timing
| Milestone | Date | Engineering | Design |
|---|---|---|---|
| Content loaded | |||
| Content ready for SME | |||
| Feedback from SME | |||
| Content signed off by SMEs | |||
| Content signed off by Mads or Katherine | |||
| Ready for proofreader | |||
| Sent to proofreader | |||
| Back from proofreader | |||
| Changes to existing site confirmed | |||
| Comms to Content Owners | |||
| Bugs fixed - high and highest | |||
| Content corrections done or assessed as ok | |||
| Go live |
Status of bugs
XXXXX
Second Topics - when content work is being done these should be prioritised
- Engineering
- Design
What needs to be in place by deployment:
- Bugs fixed - all highest and high
- Content approved by SME in situ
- People images in place
- Content checked and corrections made or a decision by Jane that they don't need to be made for release
- Proofread
- Process for demoting old content and promoting new content
- Comms plan
- Deployment plan
Before a SME checks:
- Content loaded in Squiz
- Rich media included - stories, slideshows, video
- Content correct - Jane to make a call on any outstanding items on the corrections page
- Tool tips in place or if they aren't an explanation
- Design doesn't have to be perfect across all devices and browsers - we will recommend Firefox, IE11 or Chrome all on either a desktop or laptop.
- Any bugs that aren't fixed Jane will let the SME know about