Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* NDS-385 Add image to hero component * NDS-385 Adjust scale and rotation of hero image angle * NDS-385 Update homepage, add prototyping and get started sections * NDS-385 Update hero image * NDS-385 Add links to prototyping docs * NDS-385 Update team email address * NDS-385 Add remaining prototyping assets --------- Co-authored-by: Chris Barker <chris.barker@nice.org.uk>
- Loading branch information
1 parent
e67fd24
commit 184ff0a
Showing
13 changed files
with
36,332 additions
and
36,080 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
import { ReactNode } from "react"; | ||
import Head from "next/head"; | ||
import { Breadcrumb, Breadcrumbs } from "@nice-digital/nds-breadcrumbs"; | ||
import { InPageNav } from "@nice-digital/nds-in-page-nav"; | ||
import { Grid, GridItem } from "@nice-digital/nds-grid"; | ||
|
||
import { type PageMeta } from "types/PageMeta"; | ||
|
||
export interface DefaultLayoutProps { | ||
children: ReactNode; | ||
meta: PageMeta; | ||
} | ||
|
||
export const DefaultLayout: React.FC<DefaultLayoutProps> = ({ | ||
children, | ||
meta | ||
}: DefaultLayoutProps) => { | ||
return ( | ||
<> | ||
<Head> | ||
<title>{`${meta.title} | NICE Design System`}</title> | ||
</Head> | ||
<Breadcrumbs> | ||
<Breadcrumb to="/">NICE Design System</Breadcrumb> | ||
<Breadcrumb>{meta.title}</Breadcrumb> | ||
</Breadcrumbs> | ||
|
||
<h1>{meta.title}</h1> | ||
|
||
<Grid> | ||
<GridItem cols={12} md={{ cols: 10 }} className="main-content"> | ||
{children} | ||
</GridItem> | ||
<GridItem cols={12} md={{ cols: 2 }}> | ||
<InPageNav | ||
headingsContainerSelector=".main-content" | ||
headingsExcludeSelector=".exclude-in-page-nav" | ||
headingsExcludeContainer=".exclude-container" | ||
/> | ||
</GridItem> | ||
</Grid> | ||
</> | ||
); | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
import { DefaultLayout } from "components/layouts/DefaultLayout"; | ||
|
||
export const meta = { | ||
title: "Get started", | ||
}; | ||
|
||
Our design system is here to help you design and build services at NICE. | ||
|
||
It is a collection of guidelines, design elements and tools that helps you create consistent, accessible and usable digital products. | ||
|
||
There are a number of ways you can use the design system or get involved: | ||
|
||
## Find and reference design elements | ||
|
||
Our current design [components](/design-library/#components) and [foundations](/design-library/#foundations) are documented with guidance and best practice on how to use them, including: | ||
|
||
- when and when not to use a component. | ||
- accessibility requirements and best practice. | ||
- any evidence or research behind a component. | ||
|
||
## Grab the code | ||
|
||
The code for all our design elements is available on the [component](/design-library/#components) and [foundation](/design-library/#foundations) pages. | ||
|
||
Use the HTML or React code for building, prototyping or experimenting with. | ||
|
||
## Prototyping | ||
|
||
There are a few different ways you can prototype new designs and concepts using the Design System. | ||
|
||
Our [prototyping](/prototyping) page has all the information you need to create low and high-fidelity prototypes. | ||
|
||
## Code and development | ||
|
||
View the [GitHub repo](https://github.com/nice-digital/nice-design-system) to learn how to update the system and use components in your code base. | ||
|
||
export default ({ children }) => <DefaultLayout meta={meta}>{children}</DefaultLayout>; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,96 @@ | ||
import { DefaultLayout } from "components/layouts/DefaultLayout"; | ||
|
||
export const meta = { | ||
title: "Prototyping", | ||
}; | ||
|
||
There are two main ways of creating prototypes with the design system: | ||
|
||
- design kits | ||
- HTML | ||
|
||
## Design kits | ||
|
||
Our design kits support single page mockups, low and high-fidelity prototypes and simple or complex interactions. | ||
|
||
Our design components and settings are available as Adobe XD and Axure RP files. | ||
|
||
- [Adobe XD - Design System UI kit](/assets/NICE-Design-System.xd) | ||
- [Axure RP - Design System UI kit](/assets/NICE-Design-System-v1.0.rplib) | ||
|
||
## HTML | ||
|
||
HTML is best for advanced functionality, complex logic or to simulate the most realistic user experience, for example when testing for accessibility. | ||
|
||
HTML prototypes currently need developer support to setup. [Contact the Design System team](mailto:designsystem@nice.org.uk) to see how we can help with this. | ||
|
||
## How to set up Axure RP | ||
|
||
Axure RP is an application used to create wireframes, mockups and interactive prototypes. | ||
|
||
### Add the NICE Design System Axure library to Axure RP | ||
|
||
1. Install [Axure RP](https://www.axure.com/) - make sure you install the latest version | ||
2. Get the Design System widget library. The library contains widgets for Design System components, design elements and patterns. | ||
3. Open Axure and click the 'Add Library +' icon at the top of the libraries pane. | ||
4. Locate and select the `NICE_Design_System_2023_v1.0.rplib` file. | ||
|
||
[NICE Design System Axure library](https://cxngys.axshare.com/?id=dmzedi&p=notes_about_the_nice_design_system_library&c=1) | ||
|
||
|
||
### Start Designing | ||
|
||
Use the widgets from the NICE Design System Axure library to start designing. The widgets are in the libraries pane on the left side panel. To add a widget to the canvas, click and drag it from the libraries pane. | ||
|
||
All widgets come with styles and interactions already built into them. | ||
|
||
### Support | ||
|
||
If you are new to Axure, there are lots of [tutorials](https://docs.axure.com/axure-rp/reference/getting-started-video/) to get you started. | ||
|
||
### Releases | ||
|
||
When a new library version is available, you must download the new file to replace the old one. | ||
|
||
## Pick the right tool for the job | ||
|
||
Consider what you need to learn with your prototype and choose the right prototyping tool. | ||
|
||
### Flat mockups | ||
Mockups of pages without interactions or navigation. | ||
|
||
#### Best used for | ||
Initial design feedback, early concepts, copy and content testing. | ||
|
||
#### Tools to use | ||
Adobe XD is good for quick mockups and simple user journeys. You can also use Axure if you are familiar with it, but it has a steeper learning curve for beginners. | ||
|
||
### Simple prototypes | ||
Ideal for demonstrating content and simple user flows and journeys, for example, navigating between pages. | ||
|
||
#### Best used for | ||
Simple journeys, user flows and interactions. | ||
|
||
#### Tools to use | ||
Adobe XD is suitable for simple user journeys and interactions. However, it lacks advanced prototyping functionality. | ||
|
||
### Complex prototypes | ||
Prototypes with more complex functionality and logic. For example, working filters, form fields and drop-down menus. | ||
|
||
#### Best used for | ||
Functionality and task performance, usability and user journey testing. | ||
|
||
#### Tools to use | ||
Axure allows you to add more complex interactions and functionality to your prototype, for example, logic and conditions. | ||
|
||
### HTML prototypes | ||
|
||
Building designs in HTML is the most realistic and accessible experience for testing but also potentially the most time-consuming to produce. HTML prototypes should only be considered if you are confident in the design and content. Try to learn as much as possible with simpler prototypes before considering HTML. | ||
|
||
#### Best used for | ||
Accessibility testing with assistive technologies. Testing of responsive design and layouts across viewports. Testing advanced interactions that would be too difficult or time-consuming to build in a design tool. | ||
|
||
#### Tools to use | ||
HTML prototypes will need support from developers to setup and build. [Contact the team](mailto:designsystem@nice.org.uk) if you think this is something you need. | ||
|
||
export default ({ children }) => <DefaultLayout meta={meta}>{children}</DefaultLayout>; |
Binary file not shown.
Binary file not shown.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.