diff --git a/Gruntfile.js b/Gruntfile.js index 08681cce7..5bf7cadfc 100644 --- a/Gruntfile.js +++ b/Gruntfile.js @@ -511,7 +511,6 @@ module.exports = function(grunt) { 'autoprefixer', 'browserify:dev', 'browserify:lexicon', - 'browserSync', 'watch' ]); diff --git a/docs/docs/components/button.mdx b/docs/docs/components/button.mdx index 11aab8e16..6a8ca339f 100644 --- a/docs/docs/components/button.mdx +++ b/docs/docs/components/button.mdx @@ -83,7 +83,7 @@ The text label you use for a button should be clear enough for any user to under If the button relates to an action, the label should ideally be a verb, use the common state classes to reinforce dangerous or destructive actions with colour, but don't rely on colour alone to communicate a button’s intention.
- +       
Other recommendations for labelling your buttons include: @@ -94,12 +94,12 @@ Other recommendations for labelling your buttons include:
Do use title case
-
-
- -
-
Don’t use sentence case or all caps
+
+
+
+  
+
Don’t use sentence case or all caps
@@ -127,7 +127,7 @@ If an action relates to creating new items of content, use 'New', Do not use 'Cr If a button triggers more than one action you should communicate the chain of events to the user, ideally in the order in which they will happen. This helps users to build a mental model of what is happening when they push a button.
- +  
## Using icons diff --git a/docs/docs/guides/getting-started.mdx b/docs/docs/guides/getting-started.mdx index 3e3bd1bf3..c4d045c13 100644 --- a/docs/docs/guides/getting-started.mdx +++ b/docs/docs/guides/getting-started.mdx @@ -10,46 +10,46 @@ As a Jadu designer or developer, you’re probably working on one or more of the ## Team -
-
-
-
-
- -
-

Paul Stanton

+
+
+
+
+
+ +
+

Paul Stanton

-
+
Head of User Experience @jadu
- -
-
-
-
+
+
+
+
-
-

James Jacobs

+
+

James Jacobs

-
+
Accessibility Lead
-