Skip to content

Roadmap & delivery

Do these guidelines differ for your brand? Let us know in #design-system-guild.

Scheduled work by activity

Last updated: April 2024

Q2 2024

For FT staff see our Q2 OKRs and for more detail our Programme Delivery Plan.

Previously

Q1 2024

Q1 OKRS

  1. Foundations
    • Colour palette (done): Our colour palette lacks guidance on when to use what colour, making it tricky to produce a consistently on-brand product. E.g. “sky” is used for opinion pieces, but we have never documented that.
    • Colour use cases (done): Reaching for colours by use-case “page background”, “link”, allows us to find the colour we need more quickly, and roll out global updates from a central place.
    • Colour tinting (done): We have a range of colour tints available but no guidance on how to apply them.
    • Spacing scale (done): We’re aligning our spacing scale across brands and moving to an easier to remember t-shirt naming.
    • Typography scale (done): We’re aligning our typography scale across brands.
    • Product typography (carried over): Non-editorial headings and other typography styles are poorly adhered to, undermining our products. A design audit to identify needs, with new written guidelines, will help designers make consistent choices going forward.
    • Editorial typography (carried over): Multiple brands and sub-brands are working on Spark for Everyone, a shared content management system. We want to be ready to support with front-end components for article pages.
  2. Components
    • Buttons (done): Surprisingly complex and commonly used. An excellent test of design tokens to support multiple brands.
    • Tooltip (done): We know of 3 use-cases where our legacy o-tooltip is used, in ways it was not designed for. This often creates an inaccessible and inconsistent experience. Tooltip is therefore a great way for us to demonstrate our new, design guideline led approach. It also gives us an opportunity to explore technical decisions around building interactive components for our new architecture.
    • Labels – basic (postponed): We see this as a quick win. Our core brand’s labels are simple, and Sustainable Views’ use of labels could be improved. Right now they conflict in style with buttons and feel like they should be clickable.
    • Labels – badge/live (postponed): We have decided to postpone to better align with Customer Products’ roadmap.
  3. Patterns
    • Pagination (done): Previously part of our legacy o-buttons component, it was never widely adopted. Documenting pagination as our first pattern and adding to our Figma library makes this much more discoverable than before. A design audit will also allow us to make improvements for mobile.
  4. Onboard contributors (done): The Origami team are partnering with contributors in other teams so we can deliver a modern Origami design system, including design guidelines, new Figma libraries, and components for engineers. To support that we’re working on pairing, documentation, and workshops for onboarding to our new architecture.
  5. Publish
    • Review & publish new Figma libraries (done): We have new Origami Figma libraries for each brand, but these aren’t released for designers to use today.
    • Publish web components (done): Experimental components are out. We’d like to enhance React support, improve technical documentation, and make our first maintained release. We’re working with Sustainable Views as our first adopters.
    • Expand the brand support of this website (done): We want to add the Internal brand and Sustainable Views to this website, as we intend to provide a level of support to those brands.
  6. Archive the Origami Registry (done): We will migrate any remaining demos or documentation to Storybook, giving users one less source of design system demos. This is the first step to replacing the main Origami website with this, design guideline orientated website.