Content updates sprint 13

[bonnieAcameron]

Content updates sprint 13

Description

This PR addresses several small but key clarifying points on the site. It will close:

• Documentation: Add ngx-uswds to implementations page #1494
• Migration guide links to v2.x theme tokens #1593
• Remove jekyll draft guidance #1584

Additional information

Include any of the following (as necessary):

• For Remove jekyll draft guidance #1584 Remove jekyll guidance, Dan and I reviewed that page together and he decided to delete it altogether.
• Type of content review needed: stylistic, copy editing, correct pull from implementations.yml to implementations.md

Before you hit Submit, make sure you’ve done whichever of these applies to you:

• Follow the 18F Front End Coding Style Guide and Accessibility Guide.
• Run npm test and make sure the tests for the files you have changed have passed.
• Run your code through HTML_CodeSniffer and make sure it’s error free.
• Title your pull request using this format: [Website] - [UI component]: Brief statement describing what this pull request solves.

[bonnieAcameron]

@amyleadem and @mejiaj, I'm not sure why I had so many failures on this. Several of them passed but now show failure again. Could it be because one of the pages is being deleted?

[amyleadem]

@amyleadem and @mejiaj, I'm not sure why I had so many failures on this. Several of them passed but now show failure again. Could it be because one of the pages is being deleted?

@bonnieAcameron This one seems to be a two-parter :)

1. .yml files are space sensitive, so removing the extra space in front of - name should resolve some errors.
2. We pushed some updates to the main branch this morning to repair some build errors. To get those changes integrated here, you'll need to update the base branch (main) in this PR. However, I am not seeing this option in GitHub (GitHub docs about syncing with base branch). For now, I can update the base branch for you and hopefully that will fix it. Fingers crossed!

Edit: I went ahead and did both updates so that I can confirm that this addresses all the errors.

Another edit: Build was successful! Tomorrow we can circle back and figure out how to update the base branch from the GitHub view. Here's hoping I just have EOD brain and it will be where I expect tomorrow morning :)

[mejiaj]

Thanks for submitting this PR, Bonnie! I've added some questions and some minor requests related to formatting.

[bonnieAcameron]

Applied all of these, thank you James!

[bonnieAcameron]

@mejiaj and @amyleadem , I'm a bit confused about where this PR stands. What are next steps?

[amyleadem]

@bonnieAcameron @mejiaj Got the build to work. I had one quick question, but other than that, looks good to me.

[thisisdano]

A couple very minor edits that I can commit!

Resolved issue