Awesome
U.S. Web Design System documentation
This repo includes code and documentation for the U.S. Web Design System website. For information on the USWDS components and codebase, please visit our uswds Github repo.
Note that this README includes steps to pull the latest version of USWDS into your local instance of the documentation.
Running locally
The U.S. Web Design System documentation is built using Jekyll for the file framework, gulp for task management, and the node module for USWDS.
Before you start
Recommended before install:
- Ruby Version Manager - RVM Installation guides
- Node Version Manager - NVM Installation guides
You will need to have the following installed on your machine before following the commands below:
- Ruby (see .ruby-version or .tool-versions for version number), Installation guides
- Node (see .nvmrc or .tool-versions for version number), Installation guides
- Bundler (see .bundler-version for version number), Installation guides
- Chrome v59 or higher (v60 if on Windows)
- Python v2.7* (For node-gyp dependency)
⚠️ Potential issues and workarounds
- If you're running into node-gyp issues on
npm install
you'll need to install python v2.7, which is the recommended version as ofnode-gyp@3.8.0
. Once installed you can reference it vianpm config set python /usr/bin/python2.7
or wherever you have installed. You can find that withwhereis python
command. - Ubuntu 20.04 users might run into:
bundler: failed to load command: jekyll (/usr/share/rvm/gems/ruby-3.0.2/bin/jekyll)
. Install ffi with the following flag to work around itgem install ffi -- --disable-system-libffi
.
Building the documentation with gulp
Some parts of the documentation are built using gulp.
To work on the site, switch to your local copy of the repository in terminal then run the following commands to install project dependencies:
npm install
bundle install
Now that all of your dependencies are installed, you can run your local server by running the following command:
npm start
Go to 127.0.0.1:4000
in your browser — you should be viewing a local instance of designsystem.digital.gov.
Here are a few other utility commands you may find useful:
-
npm run clean
: Cleans out copied-over dependency assets. -
npm run lint
: Runseslint
andsass-lint
against JavaScript and Sass files. -
npm test
: Runs all tests and linters. -
npm run watch
: Runs a series of commands that watches for any changes in both USWDS node module and the root level asset folders in this repo. -
npm start -- --incremental
ornpm run serve
: Runs your local server with incremental regeneration enabled to greatly improve build time. Use instead ofnpm start
.
Using the latest version of the uswds
package
Sometimes you will want to use the latest version of the uswds
repo. Follow these steps to do so:
- Clone the latest version of the
uswds
repo. - Run
npm install
to install the dependencies required for the package in theuswds
directory. - Run
npm run build
to create the built version of USWDS in theuswds
directory. - Run
npm link
in the root level of theuswds
directory on your local machine. - Run
npm link uswds
in the root level of theuswds-site
directory on your local machine. - Run
npm start
in theuswds
directory, and make a note of theLocal URL
that is being served. - In another terminal window, set the
LIBRARY_BASE_URL
env var to the running instance ofuswds
. In your terminal window in theuswds-site
directory, enterexport LIBRARY_BASE_URL="http://127.0.0.1:6006"
(or theLocal URL
noted above). - In the
uswds-site
window, runnpm run serve
in theuswds-site
directory to start the Jekyll server. - Run
npm run watch
in theuswds-site
directory to have changes to that repo automatically built and compiled. Note:uswds-site
will not automatically rebuild when there are changes inuswds
, you'll need to trigger a site rebuild manually to reflect changes in theuswds
repo.
You are now linked and using the local version of USWDS. To unlink this version, type npm unlink uswds
from the root level of the uswds
directory.
Components
This documentation site showcases USWDS components by pulling in pre-built HTML from the USWDS html-templates
directory. This HTML is pulled in via a custom library_component
Jekyll tag, which takes the full name of the component as a parameter.
Deployment and previews
This site is deployed on cloud.gov Pages, which automatically builds the public site whenever commits are pushed to main
. Pages also builds public previews for each branch pushed to GitHub.
⚠️ When generating new sections, sometimes they fail to build on Pages. You can clear the cache by running a simple bundle update
, which will trigger a fresh build.
Updating the USWDS version
To update the version of USWDS being used, change the version that
package.json
specifies in its dependencies
section.
We currently pull USWDS via git rather than npm, as it allows us to use any tag or commit during development. To install a specific commit, you can use e.g.:
npm install --save "uswds/uswds#fb49e4f"
Alternatively, to use a specific version tag, use e.g.:
npm install --save "uswds/uswds#v1.3.1"
This version number or commit hash is automatically parsed when the site
is built and used for display on the site (see _plugins/uswds_version.rb
for details). Therefore, be sure to use an actual version tag on all
main
branch commits--otherwise a commit hash will show up as the
version on the production site, which would be confusing.
Adding content to the "Updates" section
See the _posts
directory for instructions on adding updates.
Dynamic content
Some of the content on the documentation site is dynamically fetched from
GitHub. If you want to ensure that its API won't rate-limit you, you
may want to
create an access token
and assign it to your GITHUB_ACCESS_TOKEN
environment variable.
The dynamic content is stored in the .jekyll_get_cache
directory and
won't be re-fetched once it's cached there. However, this means that your
data can get stale over time, so if you want to ensure that your site
is using the very latest data, you'll want to clear the cache by running:
rm -rf .jekyll_get_cache
Contributing
Please read through our contributing guidelines. These guidelines are directions for opening issues and submitting pull requests, and they also detail the coding and design standards we follow.