Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1. Migration to 11ty, basic home page setup, broad strokes migrating styles. #2 #4

Merged
merged 3 commits into from
Oct 16, 2024

Conversation

jamesthebrooks
Copy link
Contributor

Changes proposed in this pull request:

  • init setup on 11ty pages template
  • init home page migration
  • init styles migration and setup

security considerations

n/a

@jamesthebrooks jamesthebrooks changed the title Migration to 11ty, basic home page setup, broad strokes migrating styles. #2 1. Migration to 11ty, basic home page setup, broad strokes migrating styles. #2 Oct 10, 2024
Copy link

@apburnes apburnes left a comment

Choose a reason for hiding this comment

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

Great start! Just two things of note to update.

<section class="usa-footer__primary-content usa-footer__primary-content--collapsible">
<h4 class="usa-footer__primary-link">Get in touch</h4>
<ul class="usa-list usa-list--unstyled">
<li class="usa-footer__secondary-link"><a href="/contact">Customer support</a></li>

Choose a reason for hiding this comment

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

For any relative links on the site, you will want to use 11ty's url filter to properly append a possible path prefix. For all of Pages site's preview deployments, the preview is at a subpath and this url filter will automatically append it to the path. We feed the path value at a site's preview build time.

Suggested change
<li class="usa-footer__secondary-link"><a href="/contact">Customer support</a></li>
<li class="usa-footer__secondary-link"><a href="{{ '/contact' | url }}">Customer support</a></li>

Look for any other relative links not using the url filter and update them to use it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It probably makes the most sense to address this on this request all at once since a lot more content has been migrated since this PR. #9

Choose a reason for hiding this comment

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

Updating any of the template or includes files now will be pick up in all of the following PR's once you rebase them.

if (process.env.BASEURL) {
pathPrefix = process.env.BASEURL
}
if (process.env.BASEURL) {

Choose a reason for hiding this comment

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

We don't have any documentation on it in this repo but our IDE's and linting processes are configured to save JS indents as spaces with the size of 2. Update your IDE and resave the JS files. Sorry for the confusion.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It probably makes the most sense to address this on this request all at once since a lot more content has been migrated since this PR. #9

@sknep
Copy link

sknep commented Oct 16, 2024

Would love to see these commits merged/squased/rebased so that we don't have "WIP" in the forever-history. Thanks!

========================================
========================================
----------------------------------------
USWDS 2.13.1
Copy link

Choose a reason for hiding this comment

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

I think I mentioned this on another PR but this settings file is for USWDS v2, but I think the package.json has USWDS v3. Can you make these match the same major version?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Update, good catch.

@jamesthebrooks
Copy link
Contributor Author

Would love to see these commits merged/squased/rebased so that we don't have "WIP" in the forever-history. Thanks!

Significantly decreased these except for the originating branch that's since been deleted (not using correct naming convention).

@jamesthebrooks
Copy link
Contributor Author

All feedback updated in the latest peer request: #9
Propose closing this and without merging. Delete the branch if desired.

Copy link

@sknep sknep left a comment

Choose a reason for hiding this comment

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

I'd like to still review/merge these PRs individually, thanks!

@jamesthebrooks jamesthebrooks merged commit 64fad35 into main Oct 16, 2024
3 checks passed
@jamesthebrooks jamesthebrooks deleted the chore-11ty-migration branch October 23, 2024 19:36
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.

3 participants