Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

4 tiers designs #1071

Closed
helennickols opened this issue Jan 10, 2025 · 10 comments
Closed

4 tiers designs #1071

helennickols opened this issue Jan 10, 2025 · 10 comments
Assignees

Comments

@helennickols
Copy link
Contributor

helennickols commented Jan 10, 2025

What

Create designs to help people understand which building blocks have been revised more recently, and which are due a review. This needs to fit into the design treatment of the community components. This can be done without performing a discovery or a full technical, design and accessibility audit.

Why

Various methods have been used for creating and updating components since the Design System was created. Some components have been superseded by GOV.UK, for example, and will be revised or deprecated in time.

Who needs to be involved

  • led by Content Designer
    Whole team to be involved.
@helennickols helennickols self-assigned this Jan 10, 2025
@helennickols helennickols converted this from a draft issue Jan 10, 2025
@robertjmccarthy
Copy link
Contributor

Hey @helennickols,

I caught up with Matt and Graham today about the community components. It would be good if you could have a chat with them about this work as I think it's closely aligned. I see there being 4 phases of a component:

  1. Community components that the design system team haven't worked on (i.e. community contributed)
  2. Components in the DS right now that haven't been improved by the DS team (i.e. needing improvement)
  3. Components in the DS right now that have been improved or have been worked on by the DS team (i.e. new/improved)
  4. Components that have been removed/archived (i.e. deprecated)

The main reason to chat with Graham and Matt is that they are working on the community contributed components and I think some work needs to go into where these community contributed components sit and how they are differentiated from the other components. Matt and Graham have done a little bit of work on this but they're mainly focussed on how components are added via a contribution form, and how they're displayed on a page.

Can you have a chat with them both to get up-to-speed on the community space work, and see how this work crosses over please?

@helennickols
Copy link
Contributor Author

Hey @robertjmccarthy

We're very aligned in our thinking. I caught up with them last week and saw the visual treatment.

My sketches cover the first 3 categories, which have the working names 1. robust, 2. due for review and 3. community but I'll include no 4 as well. The styling will all fit together.

I'll pop some time in for me and you to talk it through.

@helennickols helennickols changed the title Designs to help users understand how and when a building block was developed 4 tiers designs Jan 16, 2025
@helennickols
Copy link
Contributor Author

@robertjmccarthy I've run through our conversation with @murrlipp and added him to the ticket. He's now working on the designs.

@murrlipp
Copy link
Contributor

Designs reviewed today. Discussed how we might ensure people who arrive on a page via an anchor link see the status of a component, and ultimately agreed that:

  • we do not have enough insight to suggest this is an issue right now, and
  • an assumed edge case should not delay us releasing something we assume will benefit the majority of visitors

Next steps:

@murrlipp
Copy link
Contributor

@mattnixon1 and @GrahamBaird1:

Tier banners can be found here for testing W/C 3rd Feb.

@Whersi we could either keep this ticket open and roll it into the next cycle as that's when we'll hear the results of the testing, OR close this ticket now and create a new one for building the design.

@Whersi
Copy link

Whersi commented Jan 24, 2025

I’ll close the ticket and ensure it’s referenced as part of the upcoming testing. We can create further tickets once we’ve received the results.

@Whersi Whersi closed this as completed Jan 27, 2025
@github-project-automation github-project-automation bot moved this from In Progress to Done in MoJ Design System: Team planning Jan 27, 2025
@helennickols
Copy link
Contributor Author

helennickols commented Jan 28, 2025

@mattnixon1 Hi, I've changed the top tag to 'Reviewed' from 'Standard met'. Have talked this through with Murray. Please make the change in the kit, if it's in there already. ta!

@robertjmccarthy
Copy link
Contributor

@murrlipp @helennickols have you had any thoughts on the content page(s) for the tiers? Do you see these as individual pages or one page which the tiers would link as an anchor to a part of the page? And, where do you see the page(s) sitting in the hierarchy of the site?

@helennickols
Copy link
Contributor Author

@robertjmccarthy @murrlipp I'd see it as an individual page which the banners deep/ anchor link to. I see it as sitting under 'Using the design system'. Do you know if there'll be any changes to that section as a result of the community component work?

@Whersi Whersi moved this from Done to In Progress in MoJ Design System: Team planning Jan 30, 2025
@robertjmccarthy
Copy link
Contributor

@helennickols and @murrlipp

Thanks for the info. I've setup a new ticket #1133 to create the content page with tier information.

The placement in the nav makes sense and I don't see there being any changes to that section as a result of the community component work.

I'll close this ticket now as we have the content page ticket setup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

4 participants