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

Restore the Blacklight logo for generated apps #3198

Open
wants to merge 16 commits into
base: main
Choose a base branch
from

Conversation

taylor-steve
Copy link
Contributor

The Blacklight default logo-image is currently using the sprockets image_url helper. This overrides logo-image using the propshaft url helper.

This is the same convention Geoblacklight is using.

@jcoyne
Copy link
Member

jcoyne commented Oct 16, 2024

@taylor-steve is it possible to fix this in Blacklight instead?

@taylor-steve
Copy link
Contributor Author

@jcoyne I haven't been able to think of a good method yet. Two separate SASS entry points could work? E.g., blacklight_sprockets.scss, blacklight_propshaft.scss. As far as I could tell this is the only use of image_url in Blacklight. I think changing the logo would be a very common first step for a new site, so this didn't feel like much of a workaround, more of an example.

@jcoyne
Copy link
Member

jcoyne commented Oct 16, 2024

@taylor-steve I don't think that blacklight really wants to continue supporting Sprockets primarily, so I think we could accept this change upstream. What about doing url(https://github.com/projectblacklight/blacklight/blob/main/app/assets/images/blacklight/logo.png?raw=true)? Would that work for both sprockets and propshaft?

@taylor-steve
Copy link
Contributor Author

@jcoyne yes, that definitely works with propshaft and I'd expect it to work with sprockets. I don't love that it would separate the logo from the release versions. Although maybe that's better for a logo anyway, defaulting to using the most current branding? I'll think on it a bit more, but you're probably right that it's the best solution.

@taylor-steve taylor-steve force-pushed the migrate-asset-pipeline branch from 64c0c4b to fbea85a Compare October 30, 2024 22:39
@taylor-steve taylor-steve force-pushed the migrate-asset-pipeline branch from ffea72a to 7e12176 Compare November 8, 2024 17:20
Base automatically changed from migrate-asset-pipeline to main November 8, 2024 18:48
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