Building with Framework: design
Guidance and documentation
Detailing what the Framework is, relevant processes, how to engage with the team and guidance for creating compliant design assets: your single source of truth for designing with Abeille Assurances' global design system.
Design: templates and how-to guides
Designing for the Framework is very easy using the existing templates for design and documentation. This section details how to ensure designs are FW compliant covering the relevant assets and deliverables for successful consumption.
Templates
There a three outputs required when designing for the Framework design system - acceptance criteria, design assets and usage guidelines. These form the basis of any component or pattern in the Framework. For the design assets to be included in the master file and accompanying documentation for the Framework website, it is recommended to download these first.
-
For Jira tickets
Acceptance criteria
The objectives for the component or pattern from which its success can be measured.
Short and concise where possible. Consider base level functionality, accessibility, usability and globalisation considerations. Usually captured on a Jira ticket.
-
For design assets
Sketch file template
Contains relevant formatting and grids for desktop, tablet and mobile.
Provides additional guidance for things to consider when designing for Framework and submission. Pre-formatted for inclusion in the master file.
-
For component documentation
Usage guidelines
Required documentation to accompany a design for build.
Includes detail around structure, design, content, accessibility, interaction, design and non-js scenarios. For component documentation in the Framework website.
How to raise a Jira ticket
Raising a JIRA ticket will allow the FW team to assess and begin work on a particular request. This is added to our end-to-end board for tracking and also serves as a single source of truth for both updates and tracking each stage of the tickets life cycle. Guidance on how this can be done is included on the Jira template ticket. At a glance, this guidance this can be broken down as:
-
Step 1
Clone the Framework template ticket
Clone this ticket by selecting ‘Clone’ from the ‘More’ dropdown menu at the top of the ticket:
-
Step 2
Choose a ticket category
Add the appropriate ticket category in the ‘Component/s’ field of the cloned ticket:
-
Step 3
Complete section A
Complete Section A, followed by all relevant additional sections (dependent on the type of request), ie. removing red guidance text, and marking anything which is not applicable:
-
Step 4
Attachments and assets
Ensure all required attachments and/or assets are attached to this ticket. This can include any design assets, InVision links or external resources which could help as references or visual aids:
What happens next?
-
Step 1 of 3
Tracking
Once a ticket is raised and subnitted it will appear on our backlog. The ticket will be trackable on the Engagement and Delivery overview board.
-
Step 2 of 3
Triage
The ticket is then assessed and reviewed by the FW core team. We will aim to triage your ticket within 2-3 working days.
-
Step 3 of 3
Shaping
Once triaged, it will be shaped if required. This can sometimes require further input and the core team will be in touch. This is then moved on to the relevant delivery stream for resolution.
Learn more about our processes and Jira boards
To learn more more about FW processes and the above JIRA boards see our information on Jira tracking and delivery.
The Framework core team
Our core team consists of of process leads, designers and developers, based in both Bois-Colombes, FRANCE. Feel free to contact someone within your respective domain if that is preferred:
-
Claire PAUMLAZ
Product owner
-
Romain GILBERT
Visual developer - Technical lead for DESY