Header
- In progress
+ Header
+ Complete
Breakpoints
- In progress
+ Breakpoints
+ Complete
Tabs
- In progress
+ Tabs
+ Complete
Status
diff --git a/public/patterns/core/breakpoints/index.html b/public/patterns/core/breakpoints/index.html
index a8801e3..6d12e98 100644
--- a/public/patterns/core/breakpoints/index.html
+++ b/public/patterns/core/breakpoints/index.html
@@ -5,8 +5,12 @@
What is it
+ Breakpoints enable responsive mobile design.
When to use it
+ Use breakpoints when designing for different screen sizes.
+ The breakpoints SCSS mixin included implements media queries to allow for the change of the layout and design based on pre-defined screen sizes.
How to use it
+ This pattern is only available for SCSS breakpoints. The mixin is avai
When using this, use the default break points as they are set to the same as the Bootstrap framework. The grid for the design system at large break point has been widened to accompdate 3 colour cards across.
//- DS2 core (c) 2024 Alexander McIlwraith
diff --git a/public/patterns/core/header/index.html b/public/patterns/core/header/index.html
index 2a14da5..ba020ac 100644
--- a/public/patterns/core/header/index.html
+++ b/public/patterns/core/header/index.html
@@ -5,8 +5,11 @@
What is it
+ A header is layout pattern that helps the user identify the site.
When to use it
+ Use a header at the top of every page. The 'front page' of a site may have a different header than the rest of the pages.
How to use it
+ Place the header at the top of the page after the skip to main content link. This basic header should be replaced with your own site's header.
diff --git a/public/patterns/core/status/index.html b/public/patterns/core/status/index.html
index bb72b18..272a5fb 100644
--- a/public/patterns/core/status/index.html
+++ b/public/patterns/core/status/index.html
@@ -49,15 +49,15 @@
Complete
Header
- In progress
+ Complete
Breakpoints
- In progress
+ Complete
Tabs
- In progress
+ Complete
@@ -77,23 +77,15 @@
Not started (0)
- In progress (3)
+ In progress (0)
+
+
+ Complete (10)
Breakpoints
Layouts
-
- Header
- Layouts
-
-
- Tabs
- Layouts
-
-
- Complete (7)
-
Colours
@@ -102,6 +94,10 @@
Components
+
+ Header
+ Layouts
+
Layouts
@@ -118,6 +114,10 @@
Switch
Components
+
+ Tabs
+ Layouts
+
Tooltip
Components
@@ -137,7 +137,7 @@
Breakpoints
- In Progress
+ Complete
Layouts
@@ -152,7 +152,7 @@
Header
- In Progress
+ Complete
Layouts
@@ -177,7 +177,7 @@
Tabs
- In Progress
+ Complete
Layouts
diff --git a/public/patterns/core/tabs/index.html b/public/patterns/core/tabs/index.html
index 730206e..b4db36a 100644
--- a/public/patterns/core/tabs/index.html
+++ b/public/patterns/core/tabs/index.html
@@ -5,7 +5,7 @@
What is it
- When to use it
+ A tabs component that provides different sections of content that are displayed one at a time when the user selects that information.
How to use it
The tabbed user interface enables users to jump to their target section quickly. Tabs present like logically group information on the same page. Information should
@@ -15,6 +15,7 @@
- obvious where they begin and end
Users should not need to see content of multiple tabs simultaneously and the user should be able to easily recognise where they are within the content.
+ When to use it
The tab module can be initialised by importing a file with the javascript module using import * as tabs from "../pg/patterns/layouts/tabs/_tabs.js"; contains a modularized version of the jQuery code, so that it can be called on demand. It is what is used in the design system so that the JavaScript can be called at run time (after loading content).
diff --git a/src/pg/_config.pug b/src/pg/_config.pug
index 357f2f0..2adb3da 100644
--- a/src/pg/_config.pug
+++ b/src/pg/_config.pug
@@ -45,17 +45,17 @@
files: [
{
name: "header",
- status: "in-progress",
+ status: "complete",
core: true,
},
{
name: "breakpoints",
- status: "in-progress",
+ status: "complete",
core: true,
},
{
name: "tabs",
- status: "in-progress",
+ status: "complete",
core: true,
},
]
diff --git a/src/pg/patterns/core/breakpoints/index.pug b/src/pg/patterns/core/breakpoints/index.pug
index 49b9e93..00fbb43 100644
--- a/src/pg/patterns/core/breakpoints/index.pug
+++ b/src/pg/patterns/core/breakpoints/index.pug
@@ -5,8 +5,15 @@ extends ../../../core/_master-pattern
block content
+h(0)
+ p Breakpoints enable responsive mobile design.
+
+h(1)
+ p Use breakpoints when designing for different screen sizes.
+
+ p The breakpoints SCSS mixin included implements media queries to allow for the change of the layout and design based on pre-defined screen sizes.
+
+h(2)
+ p This pattern is only available for SCSS breakpoints. The mixin is avai
p When using this, use the default break points as they are set to the same as the Bootstrap framework. The grid for the design system at large break point has been widened to accompdate 3 colour cards across.
diff --git a/src/pg/patterns/core/header/index.pug b/src/pg/patterns/core/header/index.pug
index 5981903..967bb85 100644
--- a/src/pg/patterns/core/header/index.pug
+++ b/src/pg/patterns/core/header/index.pug
@@ -5,8 +5,13 @@ extends ../../../core/_master-pattern
block content
+h(0)
+ p A header is layout pattern that helps the user identify the site.
+h(1)
+ p Use a header at the top of every page. The 'front page' of a site may have a different header than the rest of the pages.
+
+h(2)
+ p Place the header at the top of the page after the skip to main content link. This basic header should be replaced with your own site's header.
+
div.tab-group#header
pre.language-html(data-tab="html")
diff --git a/src/pg/patterns/core/tabs/index.pug b/src/pg/patterns/core/tabs/index.pug
index effd841..8a39849 100644
--- a/src/pg/patterns/core/tabs/index.pug
+++ b/src/pg/patterns/core/tabs/index.pug
@@ -5,9 +5,9 @@ extends ../../../core/_master-pattern
block content
+h(0)
- +h(1)
- +h(2)
+ p A tabs component that provides different sections of content that are displayed one at a time when the user selects that information.
+ +h(2)
p The tabbed user interface enables users to jump to their target section quickly. Tabs present like logically group information on the same page. Information should
ul
@@ -19,11 +19,9 @@ block content
p Users should not need to see content of multiple tabs simultaneously and the user should be able to easily recognise where they are within the content.
+ +h(1)
p The tab module can be initialised by importing a file with the javascript module using import * as tabs from "../pg/patterns/layouts/tabs/_tabs.js"; contains a modularized version of the jQuery code, so that it can be called on demand. It is what is used in the design system so that the JavaScript can be called at run time (after loading content).
-
-
-
tabset#tabs
pre.language-html(tab="html")
include _tabs.pug
//- DS2 core (c) 2024 Alexander McIlwraith diff --git a/public/patterns/core/header/index.html b/public/patterns/core/header/index.html index 2a14da5..ba020ac 100644 --- a/public/patterns/core/header/index.html +++ b/public/patterns/core/header/index.html @@ -5,8 +5,11 @@What is it
+A header is layout pattern that helps the user identify the site.
When to use it
+Use a header at the top of every page. The 'front page' of a site may have a different header than the rest of the pages.
How to use it
+Place the header at the top of the page after the skip to main content link. This basic header should be replaced with your own site's header.
diff --git a/public/patterns/core/status/index.html b/public/patterns/core/status/index.html index bb72b18..272a5fb 100644 --- a/public/patterns/core/status/index.html +++ b/public/patterns/core/status/index.html @@ -49,15 +49,15 @@Complete Header -In progress +Complete Breakpoints -In progress +Complete Tabs -In progress +Complete @@ -77,23 +77,15 @@ Not started (0) - +In progress (3) +In progress (0) ++ Complete (10) - Breakpoints Layouts - -Header -Layouts -- -Tabs -Layouts -- Complete (7) -+ Colours @@ -102,6 +94,10 @@ Components + Header +Layouts ++ Layouts @@ -118,6 +114,10 @@ Switch Components + Tabs +Layouts +Tooltip Components @@ -137,7 +137,7 @@Breakpoints -In Progress +Complete Layouts @@ -152,7 +152,7 @@ Header -In Progress +Complete Layouts @@ -177,7 +177,7 @@ Tabs -In Progress +Complete Layouts diff --git a/public/patterns/core/tabs/index.html b/public/patterns/core/tabs/index.html index 730206e..b4db36a 100644 --- a/public/patterns/core/tabs/index.html +++ b/public/patterns/core/tabs/index.html @@ -5,7 +5,7 @@ What is it
-When to use it
+A tabs component that provides different sections of content that are displayed one at a time when the user selects that information.
How to use it
The tabbed user interface enables users to jump to their target section quickly. Tabs present like logically group information on the same page. Information should
@@ -15,6 +15,7 @@
- obvious where they begin and end
Users should not need to see content of multiple tabs simultaneously and the user should be able to easily recognise where they are within the content.
+When to use it
The tab module can be initialised by importing a file with the javascript module using import * as tabs from "../pg/patterns/layouts/tabs/_tabs.js"; contains a modularized version of the jQuery code, so that it can be called on demand. It is what is used in the design system so that the JavaScript can be called at run time (after loading content).
diff --git a/src/pg/_config.pug b/src/pg/_config.pug index 357f2f0..2adb3da 100644 --- a/src/pg/_config.pug +++ b/src/pg/_config.pug @@ -45,17 +45,17 @@ files: [ { name: "header", - status: "in-progress", + status: "complete", core: true, }, { name: "breakpoints", - status: "in-progress", + status: "complete", core: true, }, { name: "tabs", - status: "in-progress", + status: "complete", core: true, }, ] diff --git a/src/pg/patterns/core/breakpoints/index.pug b/src/pg/patterns/core/breakpoints/index.pug index 49b9e93..00fbb43 100644 --- a/src/pg/patterns/core/breakpoints/index.pug +++ b/src/pg/patterns/core/breakpoints/index.pug @@ -5,8 +5,15 @@ extends ../../../core/_master-pattern block content +h(0) + p Breakpoints enable responsive mobile design. + +h(1) + p Use breakpoints when designing for different screen sizes. + + p The breakpoints SCSS mixin included implements media queries to allow for the change of the layout and design based on pre-defined screen sizes. + +h(2) + p This pattern is only available for SCSS breakpoints. The mixin is avai p When using this, use the default break points as they are set to the same as the Bootstrap framework. The grid for the design system at large break point has been widened to accompdate 3 colour cards across. diff --git a/src/pg/patterns/core/header/index.pug b/src/pg/patterns/core/header/index.pug index 5981903..967bb85 100644 --- a/src/pg/patterns/core/header/index.pug +++ b/src/pg/patterns/core/header/index.pug @@ -5,8 +5,13 @@ extends ../../../core/_master-pattern block content +h(0) + p A header is layout pattern that helps the user identify the site. +h(1) + p Use a header at the top of every page. The 'front page' of a site may have a different header than the rest of the pages. + +h(2) + p Place the header at the top of the page after the skip to main content link. This basic header should be replaced with your own site's header. + div.tab-group#header pre.language-html(data-tab="html") diff --git a/src/pg/patterns/core/tabs/index.pug b/src/pg/patterns/core/tabs/index.pug index effd841..8a39849 100644 --- a/src/pg/patterns/core/tabs/index.pug +++ b/src/pg/patterns/core/tabs/index.pug @@ -5,9 +5,9 @@ extends ../../../core/_master-pattern block content +h(0) - +h(1) - +h(2) + p A tabs component that provides different sections of content that are displayed one at a time when the user selects that information. + +h(2) p The tabbed user interface enables users to jump to their target section quickly. Tabs present like logically group information on the same page. Information should ul @@ -19,11 +19,9 @@ block content p Users should not need to see content of multiple tabs simultaneously and the user should be able to easily recognise where they are within the content. + +h(1) p The tab module can be initialised by importing a file with the javascript module using import * as tabs from "../pg/patterns/layouts/tabs/_tabs.js"; contains a modularized version of the jQuery code, so that it can be called on demand. It is what is used in the design system so that the JavaScript can be called at run time (after loading content). - - - tabset#tabs pre.language-html(tab="html") include _tabs.pug