davsclaus opened a new pull request, #1639:
URL: https://github.com/apache/camel-website/pull/1639

   ## Summary
   
   Combined blog image optimization addressing CDN 404 issues (#1631). 
Supersedes #1637 and #1638.
   
   - **Shared default featured image**: add 88KB JPEG fallback in `assets/img/` 
so blog posts without a custom featured image get the default automatically via 
Hugo `resources.Get` fallback in `post.html` and `header.html`
   - **Delete 101 duplicate featured.png**: two sets of identical camel photos 
(48 × 3.8MB originals + 53 × 240KB karavan silhouettes) replaced by the shared 
fallback — saves ~195MB
   - **Resize all images to 800px max width**: blog CSS caps display at 
`max-width: 800px`, so wider images waste bandwidth without visual benefit
   - **Convert 99 photo-PNGs to JPEG** (quality 60): photographs and 
screenshots stored as PNG compress 5-10× better as JPEG. All markdown 
references updated from `.png` to `.jpg`
   
   **Total blog image size: ~440MB → ~202MB (54% reduction)**
   
   ## Details
   
   | Optimization | Files | Size saved |
   |---|---|---|
   | Delete duplicate featured.png (set 1: camel photo) | 48 deleted | ~182MB |
   | Delete duplicate featured.png (set 2: karavan silhouette) | 53 deleted | 
~12MB |
   | Resize images >800px to 800px | ~500 resized | variable |
   | Convert photo-PNGs to JPEG | 99 converted | ~80% per file |
   | Shared default featured image | 1 added (88KB) | enables dedup |
   
   ## Test plan
   
   - [ ] Verify blog posts render correctly — both posts with custom featured 
images and posts using the shared default
   - [ ] Check og:image meta tags work for social sharing
   - [ ] Spot-check image quality on a few converted PNG→JPEG images
   - [ ] Confirm no broken image links in markdown posts
   
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to