Frontend for design-history.education.gov.uk. Changes and approvals are managed by @andyjones81 or DfE Design Ops. (See the DFE Design Manual for details)
We have more products in the division, but I'm specifically talking about:
Apply to become an academy
Prepare conversions and transfers
Complete conversions, transfers and changes
They were all run by separate teams in the past. They're all, now, managed by 1 team: the Manage academy projects team.
This is mostly down to boring reasons about the way the work and teams doing that work had to be chunked up in order to get the things live and in use.
Most of the time, we can write design histories that focus on specific work that happened in each product, so that's easy to assign to 1 "service" category or another.
But sometimes we do work that applies across all 3 of our products, like reviewing and updating page titles to make them accessible.
It'd be good to be able to write this once and associate it to each product, rather than silo it in 1 design history and it not appear in the list of posts for the other 2.
1 solution is for is to start a new design history that covers all the work across those products. But that feels like it'd be yet another place for folk to look for information and it would introduce another bucket of stuff for things to get soiled into, so I'd rather not do that.
Is there a way we could publish once but associate that post to multiple "services"?
Is it, or could it be, possible to assign a design history post to more than one "service" category?
In RSD, some of our "services" in the design history thing are actually products that form part of a wider service and are not services in themselves.
We have more products in the division, but I'm specifically talking about:
They were all run by separate teams in the past. They're all, now, managed by 1 team: the Manage academy projects team.
This is mostly down to boring reasons about the way the work and teams doing that work had to be chunked up in order to get the things live and in use.
Most of the time, we can write design histories that focus on specific work that happened in each product, so that's easy to assign to 1 "service" category or another.
But sometimes we do work that applies across all 3 of our products, like reviewing and updating page titles to make them accessible.
It'd be good to be able to write this once and associate it to each product, rather than silo it in 1 design history and it not appear in the list of posts for the other 2.
1 solution is for is to start a new design history that covers all the work across those products. But that feels like it'd be yet another place for folk to look for information and it would introduce another bucket of stuff for things to get soiled into, so I'd rather not do that.
Is there a way we could publish once but associate that post to multiple "services"?