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

Site IA: review and update #329

Closed
1 task done
martinwake opened this issue Jan 12, 2022 · 3 comments
Closed
1 task done

Site IA: review and update #329

martinwake opened this issue Jan 12, 2022 · 3 comments
Assignees
Labels
🔤 site content Updates to the content of the design system site

Comments

@martinwake
Copy link
Collaborator

martinwake commented Jan 12, 2022

What

The information architecture (structure) of the Design System website needs to be reviewed and likely updated.

Why

Several recent changes have highlighted this need, including:

  • we need to decide where the "Get started" pages should go
  • the Team page no longer has updates from individual team members, which means it no longer makes sense for it to sit under "latest updates"
  • we are planning to publish update articles and don't have anywhere for these to go

Done when

  • Site structure is reviewed and an updated structure agreed

Outcomes

New site structure

Home

Get started
	- For designers
	- For developers
	
Components (alphabetical list)
	- Component 1
	- Component 2
	- Retired components
	
Patterns (alphabetical list)
	- Pattern 1
	- Pattern 2
	- Retired patterns

Community
	- Latest updates
	- Roadmap
	- Backlog
	- Contribute
	- The team

Who needs to know about this

Design System team

Related stories

#296
#216
#297
#298
#265
#308

@martinwake martinwake self-assigned this Jan 12, 2022
@martinwake
Copy link
Collaborator Author

martinwake commented Jan 21, 2022

After reviewing other sites it looked like we could address these issues by

  • Merging the Backlog, Contribute and Roadmap sections into one section called "Community"
  • Adding a "Get started" section

The main sections would then be:

- Get started
- Components		
- Patterns		
- Community		

This is coincidentally the same as GOV.UK but without the "Styles" section.

I did a quick tree test (https://www.nngroup.com/articles/tree-testing/) on this proposed structure using a free online tool, which had 10 respondents (8 content designers, 2 interaction designers). They also provided freeform comments on the site which are here: #197 (comment)

The test was set up with 3 tasks:

  1. You want to find out what new work is planned for the design system. Where can you find this information?
  2. You want to suggest a new pattern to be included in the design system. Find out how to do this.
  3. You've found a pattern that you want to use in your prototype. Where would you find out how to do this?

10 people took part in the test (8 content designers and 2 interaction designers). The tasks were presented in a random order to counteract the effects of people learning from previous tasks.

The test suggested this slightly revised structure:

Get started
	- For designers
	- For developers
	
Components (alphabetical list)
	- Component 1
	- Component 2
	---
	- Component 3 (retired)
	
Patterns (alphabetical list)
	- Pattern 1
	- Pattern 2
	---
	- Pattern 3 (retired)

Community
	- Roadmap (current)
		○ October 2021
	- Backlog
	- Contribute
	- The team

@martinwake
Copy link
Collaborator Author

Comments from test participants here: #197 (comment)

@martinwake
Copy link
Collaborator Author

Discussed with @simoneduca and made minor changes to how the retired patterns/components are presented. Updated structure in description.

@martinwake martinwake added the 🔤 site content Updates to the content of the design system site label Feb 2, 2022
@martinwake martinwake assigned martinwake and simoneduca and unassigned martinwake Feb 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔤 site content Updates to the content of the design system site
Projects
Development

No branches or pull requests

3 participants