New component testing

BRIEF: stress-test and optimise around 30 new components to ensure they meet the needs of the CMS team. Plus make sure they meet digital accessibility and functionality standards both back end and front end.

IDENTIFY COMPONENT USE CASES

Ensure that components are fit for the intended content. And that CMS editors will be able to identify this when building pages. This included:

Feeding back on any high-level issues with design and build requirements.
Defining appropriate naming conventions for components.

STRESS TEST COMPONENTS

Ensure components are intuitive to build with - and to edit. And confirm that they work as expected. This involved:

Stress testing to identify any bugs - keeping a log and feeding back to the FED and development teams.
Building out pages to push the boundaries of character limitations and image types - feeding back to UX Design.
Continuing to re-test components as new ones become available and are fixed.

TRAIN CMS TEAM

Bringing the content design team up to scratch with using and publishing the new components. This involved:

Group training sessions to establish best practice and house style.
One-on-one training sessions to fix specific issues and help junior content designers.
Creating and maintaining a fall back 'How to' guide that CMS team can reference - and to reduce the amount of support required from the development team.

ONGOING OPTIMISATION

Suggesting tweaks and edits to components as the team continues to use them and the content evolves. This includes:

Collating feedback from the CMS team to identify pain points and opportunities with existing components.
Attending regular sessions with the development, FED, Product Design and UX team - to review and recommend component changes.
Monitoring Siteimprove to check whether components are impacting accessibility or functionality of website.
User testing with the CRO team to identify if any components are hindering user engagement.