Fix Bluesky author icon and regenerate stale assets - #64
Merged
Conversation
The author-links partial mapped `bluesky` to `fas fa-cloud`, rendering a generic cloud instead of the Bluesky logo. FontAwesome 6.7 ships a real `bluesky` brand glyph, so switch to `fab fa-bluesky` and regenerate the subset (also picks up pre-existing drift: fa-calendar-times + Tailwind). Also regenerate the purged CSS and FA subset at deploy time so the live site is never stale even if a PR merges (or the build guard is overridden) without the rebuilt assets committed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
✅ Deploy Preview for powershellorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
HeyItsGilbert
approved these changes
Aug 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
Fixes the Bluesky author icon showing as a generic cloud, and prevents stale generated assets from ever reaching production again.
Root cause
themes/powershell-community/layouts/partials/author-links.htmlmappedblueskytofas fa-cloud— a literal solid cloud, not the Bluesky logo. FontAwesome 6.7 (already a devDependency) ships a realblueskybrand glyph (\e671), so this switches tofab fa-bluesky.mainhad also drifted stale onfa-calendar-timesand a Tailwind change, which is what failed the build guard on Add Constantin Hager author page #62 (and shipped broken when that check was overridden).Changes
fas fa-cloud→fab fa-blueskyin the author-links partial.assets/css/fontawesome-subset.css(+fa-bluesky, +fa-calendar-times),assets/css/tailwind.css, and thefa-brands/fa-solidsubset woff2 fonts — vianpm run build:icons+npm run build:css.deploy.ymlnow regenerates the purged CSS and FA subset before the Hugo build. Deploy already runsnpm install, so this costs a few seconds and makes production the source of truth — a missednpm run build:*(or an overridden PR guard) can no longer ship a broken icon.Verification
npm run build:css+npm run build:iconsrun clean; the build guard (Verify generated assets are up to date) now passes with no diff..fa-bluesky:before{content:"\e671"}.🤖 Generated with Claude Code