davsclaus opened a new issue, #1609:
URL: https://github.com/apache/camel-website/issues/1609

   ## Summary
   
   The blog listing at camel.apache.org/blog currently mixes all categories 
together: how-tos, AI articles, community posts, tooling announcements, and 
release announcements. Release posts make up a large portion of the blog 
archive and push more substantive content (tutorials, deep-dives, community 
stories) further down.
   
   ## Proposal
   
   1. **Filter out the "Releases" category from the main blog listing** — the 
default blog page should show everything except release announcements
   2. **Add a dedicated "Releases" link/page** — a separate listing (e.g., 
`/blog/releases/`) where all release announcements live, easily accessible but 
not cluttering the main feed
   3. Keep the main blog focused on content that helps users learn, adopt, and 
get value from Apache Camel
   
   ## Why
   
   - The main blog should prioritize content that matters most to readers: 
how-tos, use cases, new features deep-dives, AI/integration articles, and 
community posts
   - Release announcements are important but formulaic — users looking for a 
specific release can find it in the dedicated releases section
   - This improves both the human browsing experience and the signal-to-noise 
ratio for search engines and AI crawlers indexing the site
   - The download page and release notes already serve as the primary reference 
for release information
   
   ## Implementation Notes
   
   - Hugo supports filtering by category in list templates — this should be 
achievable by modifying the blog list template to exclude the "Releases" 
category and creating a separate list template for releases
   - Existing URLs for individual release blog posts should continue to work 
(no breaking changes)


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