D8 core 8537 anchor nav full w

modules/jumpstart_ui/README.md

@@ -44,11 +44,14 @@ If you are experiencing issues with this module try reverting the feature first.
 Developer
 ---
 
-If you wish to develop on this module you will most likely need to compile some new css. Please use the sass structure provided and compile with the sass compiler packaged in this module. To install:
+If you wish to develop on this module you will most likely need to compile some new css. Please use the sass structure provided and compile with the sass compiler packaged in this module. 
+
+We use 'yarn' not 'npm'. 
+
+To rebuild css after scss changes:
 
 ```
-npm install
-npm run build
+yarn build
 ```
 
 Contribution / Collaboration
@@ -57,17 +60,17 @@ Contribution / Collaboration
 You are welcome to contribute functionality, bug fixes, or documentation to this module. If you would like to suggest a fix or new functionality you may add a new issue to the GitHub issue queue or you may fork this repository and submit a pull request. For more help please see [GitHub's article on fork, branch, and pull requests](https://help.github.com/articles/using-pull-requests)
 
 
-Releases
----
-
-Steps to build a new release:
-- Checkout the latest commit from the `8.x-1.x` branch.
-- Create a new branch for the release.
-- Commit any necessary changes to the release branch.
-  -  These may include, but are not necessarily limited to:
-    - Update the version in any `info.yml` files, including in any submodules.
-    - Update the CHANGELOG to reflect the changes made in the new release.
-- Make a PR to merge your release branch into `master`
-- Give the PR a semver-compliant label, e.g., (`patch`, `minor`, `major`).  This may happen automatically via Github actions (if a labeler action is configured).
-- When the PR is merged to `master`, a new tag will be created automatically, bumping the version by the semver label.
-- The github action is built from: [semver-release-action](https://github.com/K-Phoen/semver-release-action), and further documentation is available there.
+Releases
+---
+
+Steps to build a new release:
+- Checkout the latest commit from the `8.x-1.x` branch.
+- Create a new branch for the release.
+- Commit any necessary changes to the release branch.
+  -  These may include, but are not necessarily limited to:
+    - Update the version in any `info.yml` files, including in any submodules.
+    - Update the CHANGELOG to reflect the changes made in the new release.
+- Make a PR to merge your release branch into `master`
+- Give the PR a semver-compliant label, e.g., (`patch`, `minor`, `major`).  This may happen automatically via Github actions (if a labeler action is configured).
+- When the PR is merged to `master`, a new tag will be created automatically, bumping the version by the semver label.
+- The github action is built from: [semver-release-action](https://github.com/K-Phoen/semver-release-action), and further documentation is available there.