Skip to content

Improvements to migration guidance#1583

Merged
mejiaj merged 10 commits intomainfrom
dw-migration-updates
May 4, 2022
Merged

Improvements to migration guidance#1583
mejiaj merged 10 commits intomainfrom
dw-migration-updates

Conversation

@thisisdano
Copy link
Copy Markdown
Contributor

I've made some improvements to the migration guidance based on my experience migrating to USWDS 3.0 on the Public Sans website. Changes outlined in the comments.

Comment on lines 94 to +102
- name: "margin"
base: "margin-"
defaultSize: 47.9
defaultSize: 4.35
- name: "margin-horizontal"
base: "margin-"
defaultSize: 21.75
- name: "margin-vertical"
base: "margin-"
defaultSize: 21.75
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added new margin modules. margin is a quirky module that has -horizontal and -vertical options as well.

Comment on lines +10 to +13
- text: Using USWDS CSS and JavaScript in your project
href: '#using-uswds-css-and-javascript-in-your-project'
- text: Compiling USWDS Sass into CSS
href: '#compiling-uswds-sass-into-css'
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated the sidenav to match the new structure of the README

---

{% assign content = site.data.install-readme.decoded | markdownify | absolutify_links: 'https://github.com/uswds/uswds/blob/release-2.0/' | split: '<h2 id="using-the-design-system">Using the design system</h2>' | last | split: '<h2 id="reuse-of-open-source-style-guides">' | first %}
{% assign content = site.data.install-readme.decoded | markdownify | absolutify_links: 'https://github.com/uswds/uswds/blob/release-2.0/' | split: '<h2 id="installing-the-design-system">Installing the design system</h2>' | last | split: '<h2 id="reuse-of-open-source-style-guides">' | first %}
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed the README import to match the new format of the README.

- const sass = require("gulp-sass");
+ const sass = require("gulp-sass")(require("sass"));
{%- endhighlight %}
</li>
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added some more steps to outline how sass and gulp-sass need to be updated to compile our Sass properly

...
- const uswds = require("./node_modules/uswds-gulp/config/uswds");
+ const uswds = "node_modules/@uswds/uswds";
+ const uswds = "./node_modules/@uswds/uswds";
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use ./ consistently throughout

Comment on lines +515 to +516
1. Check your settings to see if they are set to either the **old** or the **new** default.
1. If they use either the **old** or the **new** default, delete the setting from your settings file so it uses the system default.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Delete the setting if it uses the old value or the new value.


###### What to do
1. Replace instances of `$theme-site-max-width` with `$theme-grid-container-max-width`
1. Replace instances of `$theme-site-max-width` with `$theme-grid-container-max-width`. If your layout is affected by this change, remove this setting from your settings file.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a note about checking to see if there are any regressions after replacing this setting

2. **Determine which packages your project needs.** The process of determining which packages your project needs is not automatic. Most projects will need to do a little work to identify the components their project uses.

A brute-force method to determine which packages your project uses is to search your codebase for use of a key class name associated with that component, like `usa-accordion` for accordions. All `usa-` prefixed packages use the same name as their CSS class. For reference, all the available packages in USWDS 3.0 are listed in the [table below](#available-packages).
A brute-force method to determine which packages your project uses is to search your codebase for use of a key class name associated with that component, like `usa-accordion` for accordions. All `usa-` prefixed packages use the same name as their CSS class. For reference, all the available packages in USWDS 3.0 are listed in the [table below](#available-packages). Search package-by-package for instances of the package or search your codebase for instances of `usa-` and make a running list of all the packages you use.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a hint about package usage and identification

Each package is smart enough to include any dependent package it needs to display properly.

4. **Remove your reference to the uswds bundle package.** Once all of your project's component packages are loaded, you can safely remove the `uswds` package reference from your entry point.
4. Many projects will need to use the utilities package (`uswds-utilities`) and the global package (`uswds-global`). If your site uses utilities, be sure to include the utilites package. The global package includes normalize. If you compile your styles and see improper spacing around many elements (like around the perimeter of the page), be sure to include `uswds-global`.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a note about using the utilities package and the global package

```

For each breakpoint set to true in your project, search for its usage in your codebase by searching for the **breakpoint name** + a colon (`:`). SO, to search for the `tablet-lg` breakpoint, search for `tablet-lg:`. If that breakpoint does not appear, you can set the value to `false`.
For each breakpoint set to true in your project, search for its usage in your codebase by searching for the **breakpoint name** + a colon (`:`). So, to search for the `tablet-lg` breakpoint, search for `tablet-lg:`. If that breakpoint does not appear, you can set the value to `false`.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix typo

@thisisdano thisisdano requested a review from mejiaj May 4, 2022 17:20
@mejiaj mejiaj merged commit bbc8365 into main May 4, 2022
@mejiaj mejiaj deleted the dw-migration-updates branch May 4, 2022 17:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants