fix: add transparent favicon and apple-touch-icon (#103) #104
No reviewers
Labels
No labels
domain:backend
domain:devops
domain:frontend
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/westside-app!104
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix-favicon"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Changes
static/favicon.png— 32x32 transparent logo from MinIOassets/westside/branding/favicon-32x32-transparent.pngstatic/apple-touch-icon.png— 180x180 transparent logo from MinIOassets/westside/branding/apple-touch-icon-transparent.pngsrc/app.html— add apple-touch-icon link tagTest Plan
Review Checklist
Related Notes
project-westside-basketballPR #104 Review
DOMAIN REVIEW
Stack: SvelteKit (adapter-static) / HTML
The diff is clean and correct:
src/app.html-- Replaced a bare<link rel="icon">with a properly attributed<link rel="icon" type="image/png" sizes="32x32">. Added<link rel="apple-touch-icon" sizes="180x180">. Both follow standard HTML5 favicon best practices.static/favicon.png-- 32x32 transparent PNG added to the canonical SvelteKit static asset directory. Sourced from MinIO branding assets per the PR description.static/apple-touch-icon.png-- 180x180 transparent PNG. Correct size for iOS home screen icons.The
%sveltekit.assets%prefix is the correct SvelteKit pattern for referencing static assets inapp.html. No issues with asset paths.CI pipeline (
npm run check,npm run build,test -f build/index.html) will validate the build still succeeds with these changes.BLOCKERS
None.
Test coverage note: This PR adds two static image files and one HTML link tag. The repo has no test infrastructure. Requiring unit tests for a favicon/apple-touch-icon addition is not reasonable -- the CI build validation step and the manual Test Plan items in the PR body are sufficient for this scope.
NITS
fix-faviconrather than103-fix-faviconor103/fix-favicon. Convention is to name branches after the issue number for traceability. Minor.favicon.icofallback: Some older browsers and tools (bookmarklets, RSS readers) look forfavicon.icoat the root. Not critical for this audience, but worth noting for completeness.SOP COMPLIANCE
fix-favicon, not103-*project-westside-basketball)PROCESS OBSERVATIONS
VERDICT: APPROVED