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

Remove jekyll assets #314

Merged
merged 12 commits into from May 18, 2023
Merged

Remove jekyll assets #314

merged 12 commits into from May 18, 2023

Conversation

drewbo
Copy link
Contributor

@drewbo drewbo commented May 10, 2023

Changes proposed in this pull request:

Notes

  • To be documented in a post

Security considerations

Removes unmaintained software and allows for moving off EOL Ruby 2.7

@drewbo drewbo requested a review from a team May 11, 2023 14:17
@drewbo drewbo changed the title [WIP] remove jekyll assets Remove jekyll assets May 11, 2023
Copy link
Contributor

@svenaas svenaas left a comment

Choose a reason for hiding this comment

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

Added a couple of a suggestions.

README.md Outdated Show resolved Hide resolved
Copy link
Contributor

Choose a reason for hiding this comment

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

Do you think it's worth wrapping {{site.baseurl}}/assets/uswds/ in a utility of some sort? This gets repeated a lot.

Copy link
Contributor

Choose a reason for hiding this comment

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

Or at least {{site.baseurl}}/assets/, which gets repeated even more?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

the first tag can also be replaced with {{ 'assets/uswds/mypath.ext' | relative_url }} but that's not shorter (or for me any easier to read). I'll include this as an option when finishing the migration guide.

In general, I'd rather leave as is because it is the filepath, and making it shorter for DRY sake actually makes it harder to tell where the file is (which is part of the problem with jekyll-assets)

Copy link
Contributor

Choose a reason for hiding this comment

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

OK, that's fair. Thanks, Drew.

svenaas
svenaas previously approved these changes May 11, 2023
Copy link
Contributor

@svenaas svenaas left a comment

Choose a reason for hiding this comment

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

Looks good to me!

Copy link
Contributor

@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.

Looks like a lot of the asset images are broken in the preview build

@svenaas
Copy link
Contributor

svenaas commented May 11, 2023

Looks like a lot of the asset images are broken in the preview build

The asset paths are like {{site.baseurl}}/assets/etc/etc.

@drewbo, should site.baseurl account for /preview/cloud-gov/site/branch/ or is this unavoidable?

@drewbo drewbo force-pushed the remove-jekyll-assets branch 3 times, most recently from 2c9b83d to 10a193e Compare May 17, 2023 16:10
Co-authored-by: Sven Aas <12150+svenaas@users.noreply.github.com>
@drewbo drewbo force-pushed the remove-jekyll-assets branch 2 times, most recently from 431702e to 1054204 Compare May 17, 2023 20:57
@apburnes apburnes self-requested a review May 18, 2023 14:09
Copy link
Contributor

@svenaas svenaas left a comment

Choose a reason for hiding this comment

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

Changes look good, as does the preview build.

@drewbo drewbo merged commit d817524 into main May 18, 2023
3 checks passed
@drewbo drewbo deleted the remove-jekyll-assets branch May 18, 2023 14: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.

None yet

3 participants