feat: switch website scripts from npm-run-all to concurrently (#2629)

Co-authored-by: Dylan Hyun <dylan.hyun@hashicorp.com>

Author: shleewhite

website/cspell-config/dictionary-docs-examples.txt

@@ -0,0 +1,25 @@
+# Proper nouns in examples
+Atticus
+Exupéry
+Maudie
+O’Shaughnessy
+pharell
+Picoult
+Tartt
+
+# Example Spanish words
+adicional
+Contenido
+elemento
+Mostrar
+ocultar
+
+# Sample random strings
+fbrct
+Mhmn
+Nqpt
+Tcqv
+tyng
+
+# Example incorrectly spelled word
+organisation

website/cspell-config/dictionary-lorem.txt

@@ -1,84 +1,97 @@
-lorem
-ipsum
-dolor
-amet
-consectetur
+accumsan
+achromatopsia
+adipiscig
 adipiscing
-elit
-sed
-eiusmod
-tempor
-incididunt
-labore
-dolore
-magna
+adipisicing
 aliqua
-enim
-minim
-veniam
-quis
-nostrud
-exercitation
-ullamco
-laboris
-nisi
+aliquam
+aliquet
 aliquip
-commodo
-consequat
-duis
+amet
+anim
+arcu
+assumenda
+auctor
 aute
-irure
-reprehenderit
-voluptate
-velit
-esse
 cillum
-fugiat
-nulla
-pariatur
-excepteur
-sint
-occaecat
-cupidatat
-proident
-sunt
+commodo
+consectetur
+consecteu
+consequat
 culpa
-qui
+cupidatat
+dapibus
 deserunt
-mollit
-anim
-laborum
-achromatopsia
-adipiscig
-aliquet
-arcu
-consecteu
 dignissim
 direcly
 dolar
+dolor
+dolore
+duis
 eget
+eiusmod
+elit
+enim
+esse
 etiam
+excepteur
+exercitation
+expedita
 facilisis
 faucibus
 felis
+fuga
+fugiat
 iaculis
+impedit
+incididunt
+ipsum
+irure
+iure
+labore
+laboris
+laborum
 lacinia
 lobortis
+lorem
+magna
+minim
+molestiae
 mollis
+mollit
+natus
 nibh
+nisi
+nostrud
+nulla
+nunc
+occaecat
+odit
 orci
+pariatur
 pellentesque
+Perferendis
 porttitor
+proident
+qui
+quis
+quisque
+reprehenderit
+sed
+sint
 somelink
+sunt
+suscipit
+tempor
 tortor
-varius
-vestibulum
+ullamco
 ultrices
-venenatis
-auctor
-aliquam
-dapibus
-nunc
+unde
+varius
 vehicula
-quisque
-accumsan
+velit
+venenatis
+veniam
+vestibulum
+voluptate
+voluptates

website/cspell-config/project-words.txt

@@ -1,36 +1,63 @@
+affordance
+Autoscaler
+borderless
+codemod
 codemods
 commodo
 concat
+Consolas
+Credly
 datacenter
 datacenters
+datagrid
 Deque’s
 devdot
+dialogprimitive
 dropdowm
+duplicative
 flexbox
 flyouts
 frontmatter
 hcp’s
+heatmaps
 hmac
+Knowledgebase
 letterforms
+luxon
+Menlo
+navigations
+powerselect
 preprocess
+Println
+rabbitmq
 radiocards
+recertification
+recertify
+rgba
 roadmap
+Segoe
+SideNav
 signup
 spacebar
 splattributes
 srollbar
+Stargate
+statuspage
 stickersheet
+subcomponent
+subcomponents
 subgrid
 sublist
+subnavigation
+subpages
 toggletip
+topbar
+Venafi
 viewports
 wcag
+wireframe
 wireframing
 workramp
-duplicative
-borderless
-datagrid
-affordance
 
 # Component-specific
 dont
@@ -41,14 +68,29 @@ callout
 callouts
 dismissable
 dismissibility
+distinguishability
+perceivability
 
 # Brands
-terraform
-packer
-vault
-vault-secrets
 boundary
 consul
+Hashi
 nomad
-waypoint
+packer
+terraform
 vagrant
+vault
+vault-secrets
+waypoint
+
+# Github usernames
+aklkv
+didoo
+dstaley
+dstaley
+fivetanley
+jorytindall
+meirish
+natmegs
+ruban
+valeriia

website/cspell.json

@@ -11,16 +11,23 @@
       "name": "dictionary-lorem",
       "path": "./cspell-config/dictionary-lorem.txt",
       "addWords": true
+    },
+    {
+      "name": "dictionary-docs-examples",
+      "path": "./cspell-config/dictionary-docs-examples.txt",
+      "addWords": true
     }
   ],
   "dictionaries": [
     "project-words",
-    "dictionary-lorem"
+    "dictionary-lorem",
+    "dictionary-docs-examples"
   ],
   "ignorePaths": [
     "node_modules",
     "project-words.txt",
     "dictionary-lorem.txt",
+    "dictionary-docs-examples.txt",
     "docs/testing"
   ]
 }

website/docs/components/app-header/partials/code/component-api.md

@@ -18,7 +18,7 @@
   <C.Property @name="hasA11yRefocus" @type="boolean" @default="true">
     Controls whether a "navigator narrator" and a "skip link" are added to the navigation (provided by the [`ember-a11y-refocus` Ember addon](https://github.com/ember-a11y/ember-a11y-refocus)). It can be programmatically turned off by passing `false`. Warning: if it is set to false, then it will fail Bypass Blocks, [Success Criteria 2.4.1](https://www.w3.org/WAI/WCAG22/Understanding/bypass-blocks.html). Since this component appears on every page, the application will not be considered conformant.
     <br><br>
-    <em>For details about the addon behaviour and functionality, refer to the [official documentation](https://github.com/ember-a11y/ember-a11y-refocus#readme).</em>
+    <em>For details about the addon behavior and functionality, refer to the [official documentation](https://github.com/ember-a11y/ember-a11y-refocus#readme).</em>
     <Doc::ComponentApi as |C|>
       <C.Property @name="a11yRefocusSkipTo" @type="string" @default='"#hds-main"'>
         Pass-through property for the `skipTo` argument - The element ID that should receive focus on skip. The default value matches the default id value on the [`AppFrame::Main` component](/layouts/app-frame#afmain).

website/docs/components/app-side-nav/partials/code/how-to-use.md

@@ -210,7 +210,7 @@ One possible way to do it is to use the **`hds-app-side-nav-hide-when-minimized`
 
 More specifically:
 
-- `minimized → maximized` transition: the content appears with a fade-in effect, when the width animation is already completed (the width is maximised)
+- `minimized → maximized` transition: the content appears with a fade-in effect, when the width animation is already completed (the width is maximized)
 - `maximized → minimized` transition: the content disappears at once with no transition, before the width animation starts
 
 Another option is to use the **`isMinimized` parameter**, which is useful in those cases where the content is so custom/specialized that it can’t just be faded in/out but needs to have a different kind of transition (eg. remain visible but change layout or respond to the width of the container). This value is passed down by the `<:header/body/footer>` named blocks as parameters, and can be used to build custom logic on the consumers’ side.

website/docs/components/app-side-nav/partials/guidelines/guidelines.md

@@ -88,7 +88,7 @@ The topGenericInstance and bottomGenericInstance properties support any addition
 
 ![Generic container within the App Side Nav body](/assets/components/app-side-nav/custom-content-body.png)
 
-## Positioning, and responsive behaviour
+## Positioning, and responsive behavior
 
 The App Side Nav should always be positioned on the left side of the viewport, occupying 100% of the viewport height to ensure that the navigation is always visible and accessible to the user.
 

website/docs/components/form/radio-card/partials/code/component-api.md

@@ -81,7 +81,7 @@
     Appends a `Required` indicator next to the legend text and sets the `required` attribute on the controls when user input is required.
   </C.Property>
   <C.Property @name="layout" @type="string" @values={{array "horizontal" "vertical" }} @default="horizontal">
-    By default, the Radio Cards will be layed out horizontally, one next to another. Set this property to `vertical` to stack them one underneath each other.
+    By default, the Radio Cards will be horizontal, one next to another. Set this property to `vertical` to stack them one underneath each other.
   </C.Property>
 </Doc::ComponentApi>
 

website/docs/components/form/radio-card/partials/code/how-to-use.md

@@ -77,7 +77,7 @@ Customizable options include:
 
 ### Layout and control position
 
-To change how the cards are layed out in a group set the `@layout` argument to `vertical`. To change the position of the control elements within a card set the `@controlPosition` argument to `left`.
+To change how the cards are laid out in a group set the `@layout` argument to `vertical`. To change the position of the control elements within a card set the `@controlPosition` argument to `left`.
 
 ```handlebars
 <Hds::Form::RadioCard::Group

website/docs/components/modal/partials/accessibility/accessibility.md

@@ -17,7 +17,7 @@ Given the Modal is triggered via a keyboard, the dismiss button is first in the
 
 ### Focus order within a complex Modal
 
-If the Modal body contains interactive content, such as input fields, the first element should receive focus first regardless of how the Modal is triggered; either via a mouse click or via the keyboard. This behaviour should be implemented by [setting the focus on the first element](/components/modal?tab=code#form-within-a-modal-dialog).
+If the Modal body contains interactive content, such as input fields, the first element should receive focus first regardless of how the Modal is triggered; either via a mouse click or via the keyboard. This behavior should be implemented by [setting the focus on the first element](/components/modal?tab=code#form-within-a-modal-dialog).
 
 ![Complex focus within a modal](/assets/components/modal/modal-focus-order-complex.png =1042x*)
 

website/docs/components/pagination/partials/code/how-to-use.md

@@ -219,7 +219,7 @@ It is also possible to show the SizeSelector (hidden by default):
 
 **Warning**
 
-When the "page size" is used in the context of a cursor-based pagination, it can lead to increased complexity and potential UX/usability issues (eg. when the cursor is `prev` and the page size is changed, the behaviour may different from what is expected by the user).
+When the "page size" is used in the context of a cursor-based pagination, it can lead to increased complexity and potential UX/usability issues (eg. when the cursor is `prev` and the page size is changed, the behavior may different from what is expected by the user).
 
 **Be mindful of this limitations and implement your code accordingly.**
 

website/docs/components/rich-tooltip/partials/code/how-to-use.md

@@ -173,7 +173,7 @@ The RichTooltip component automatically adapts its alignment depending on its po
 
 It's possible to disable this behavior by setting the `@enableCollisionDetection` argument to `false`.
 
-It's also possible to customize this behaviour using the values:
+It's also possible to customize this behavior using the values:
 - `flip` - adapts the position only along its [axis of alignment](https://floating-ui.com/docs/flip#mainaxis)
 - `shift` - adapts the position only along its [side axis](https://floating-ui.com/docs/shift#mainaxis)
 - `auto` - uses the side where there is [more space available](https://floating-ui.com/docs/autoPlacement) (in relation to the viewport)

website/docs/components/side-nav/partials/code/component-api.md

@@ -30,7 +30,7 @@ This is the full-fledged component (responsive and animated).
   <C.Property @name="hasA11yRefocus" @type="boolean" @default="true">
     Controls whether a "navigator narrator" and a "skip link" are added to the navigation (provided by the [`ember-a11y-refocus` Ember addon](https://github.com/ember-a11y/ember-a11y-refocus)). It can be programmatically turned off by passing `false`. Warning: if it is set to false, then it will fail Bypass Blocks, [Success Criteria 2.4.1](https://www.w3.org/WAI/WCAG22/Understanding/bypass-blocks.html). Since this component appears on every page, the application will not be considered conformant.
     <br><br>
-    <em>For details about the addon behaviour and functionality, refer to the [official documentation](https://github.com/ember-a11y/ember-a11y-refocus#readme).</em>
+    <em>For details about the addon behavior and functionality, refer to the [official documentation](https://github.com/ember-a11y/ember-a11y-refocus#readme).</em>
     <Doc::ComponentApi as |C|>
       <C.Property @name="a11yRefocusSkipTo" @type="string" @default='"#hds-main"'>
         Pass-through property for the `skipTo` argument - The element ID that should receive focus on skip. The default value matches the default id value on the [`AppFrame::Main` component](/layouts/app-frame#afmain).