Skip to content

Add source-specific announcements for legacy blog redirects#178

Open
jeroenjanssens wants to merge 1 commit intomainfrom
blog-source-announcement
Open

Add source-specific announcements for legacy blog redirects#178
jeroenjanssens wants to merge 1 commit intomainfrom
blog-source-announcement

Conversation

@jeroenjanssens
Copy link
Copy Markdown
Collaborator

@jeroenjanssens jeroenjanssens commented Apr 15, 2026

Summary

  • Adds announcement banners for visitors arriving from legacy blogs (Quarto, Shiny, Tidyverse, etc.) informing them that posts have moved to the unified Posit Open Source blog
  • Announcements render on /blog/q/* pages for no-JS users and dynamically on /blog/?q=source:* for JS users
  • Announcement content lives in the _index.md body of each /content/blog/q/<source>/ section, making it easy to customize per source

Test plan

  • Visit /blog/?q=source:quarto and verify the Quarto announcement banner appears
  • Visit /blog/?q=source:shiny and verify the Shiny announcement banner appears
  • Verify the featured section is hidden when a source announcement is visible
  • Clear the search query and verify the announcement disappears and featured reappears
  • Disable JS and visit /blog/q/quarto/ directly to verify the no-JS fallback shows the announcement
  • Verify no announcement appears on the default /blog/ page (no source query)

Show a banner when visitors arrive from a legacy blog (e.g., the
Quarto or Shiny blog) informing them that posts have moved to the
unified Posit Open Source blog. Announcements appear on /blog/q/*
pages for no-JS users and dynamically on /blog/?q=source:* for JS
users.
@netlify
Copy link
Copy Markdown

netlify bot commented Apr 15, 2026

Deploy Preview for posit-open-source canceled.

Name Link
🔨 Latest commit 50e6777
🔍 Latest deploy log https://app.netlify.com/projects/posit-open-source/deploys/69df8b35a570cc0008346ad2

@github-actions
Copy link
Copy Markdown

Publishing checklist

  • Get a review — request at least one reviewer on this PR
  • Check your post — once the deploy preview is ready, a comment will appear with direct links to your post
  • Check the blog listing — confirm your post appears with the correct title, image, and description
  • Merge — once everything looks good and you have an approving review, merge to main

@github-actions
Copy link
Copy Markdown

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.

1 participant