fix (marketing): blog take down to coming soon

[AviPeltz]

Description

Related Issues

Type of Change

• Bug fix
• New feature
• Documentation
• Refactor
• Other (please describe):

Testing

Screenshots (if applicable)

Additional Notes

Summary by CodeRabbit

• Documentation
  • Introduced a new blog post titled “Coming Soon” on the marketing site, indicating that updates from the team are on the way. The post includes standard metadata (title, description, author, date, category) and a placeholder message inviting readers to check back soon.
  • No functional changes to the application; this is a content addition visible on the blog.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a new static blog post file with frontmatter metadata and a placeholder message at apps/marketing/content/blog/coming-soon.mdx.

Changes

Cohort / File(s)	Summary
Marketing blog content apps/marketing/content/blog/coming-soon.mdx	New MDX post with frontmatter (title, description, author, date, category) and a placeholder body text.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

Thump-thump go my paws, I nibble on the news,
A sprout of posts soon breaking through the dews.
Blank page today, but oh what blooms!
Carrots of content in tidy rooms.
Stay tuned, friend—hop back soon! 🥕✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description uses the required template but all sections are left empty with placeholders.	Populate all template sections: provide a clear description of the changes, link related issues, select the type of change, describe testing steps, include screenshots if applicable, and add any additional notes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: taking down the blog and replacing it with a coming soon placeholder page.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@apps/marketing/content/blog/coming-soon.mdx`:
- Around line 1-7: The coming-soon.mdx file currently lives in the root blog
directory and will be picked up by getBlogPosts(), so either move this file into
the _archive/ directory to exclude it from getBlogPosts() and feeds/sitemaps, or
add a draft/published frontmatter field (e.g., draft: true or published: false)
to coming-soon.mdx and update getBlogPosts() to filter out posts with draft ===
true or published === false before returning results; modify the code path in
getBlogPosts() where frontmatter is read to apply this filter so drafts are
ignored by listings, RSS (/feed.xml), and sitemaps.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Find existing frontmatter flags used in other posts
echo "=== Checking for existing frontmatter flags in blog posts ==="
fd -e mdx -e md apps/marketing/content/blog \
  -x rg -n "^(draft|published|noindex|robots|hidden)\s*:" {}

echo -e "\n=== Checking blog post structure and frontmatter usage ==="
fd -e mdx -e md apps/marketing/content/blog | head -5 | xargs -I {} sh -c 'echo "File: {}"; head -15 {} | cat -n'

echo -e "\n=== Searching for MDX/frontmatter processing config ==="
rg -l "frontmatter|mdx|remark|rehype|blog" apps -g '*.{ts,tsx,js,jsx,json,yml,yaml}' | head -20

echo -e "\n=== Checking for gray-matter or similar frontmatter parsing ==="
rg -n "gray-matter|vfile|remark|rehype" apps/marketing -g '*.{ts,tsx,js,jsx,json,config}'

Repository: superset-sh/superset

Length of output: 2110

---

🏁 Script executed:

#!/bin/bash

echo "=== Sample blog posts structure (first 20 lines) ==="
fd . apps/marketing/content/blog -e mdx -e md | head -3 | xargs -I {} sh -c 'echo "File: {}"; head -20 {}'

echo -e "\n=== Checking blog.ts for frontmatter processing ==="
cat -n apps/marketing/src/lib/blog.ts | head -50

echo -e "\n=== Checking blog-utils.ts ==="
cat -n apps/marketing/src/lib/blog-utils.ts | head -50

echo -e "\n=== Checking blog/page.tsx for post filtering ==="
cat -n apps/marketing/src/app/blog/page.tsx

Repository: superset-sh/superset

Length of output: 8966

---

🏁 Script executed:

#!/bin/bash

echo "=== Checking feed.xml/route.ts ==="
cat -n apps/marketing/src/app/feed.xml/route.ts

echo -e "\n=== Full getBlogPosts() implementation ==="
cat -n apps/marketing/src/lib/blog.ts | tail -30

echo -e "\n=== Check if _archive is filtered ==="
fd . apps/marketing/content/blog --type d

echo -e "\n=== Checking sitemap.ts for blog post filtering ==="
cat -n apps/marketing/src/app/sitemap.ts | grep -A 10 -B 5 blog

Repository: superset-sh/superset

Length of output: 4140

---

🏁 Script executed:

#!/bin/bash

echo "=== Full getBlogPosts() implementation (lines 48-75) ==="
sed -n '48,75p' apps/marketing/src/lib/blog.ts | cat -n

echo -e "\n=== Check if files in _archive are included in getBlogPosts ==="
ls -la apps/marketing/content/blog/ | head -20

echo -e "\n=== Check directory structure ==="
tree -L 2 apps/marketing/content/blog 2>/dev/null || find apps/marketing/content/blog -type f -name "*.mdx" | head -10

Repository: superset-sh/superset

Length of output: 1525

---

Move to _archive/ directory or add draft/published frontmatter support.

The coming-soon.mdx file in the root blog directory will be picked up by getBlogPosts() (which only reads direct children) and will appear in blog listings, RSS feeds (/feed.xml), and sitemaps. The site does not currently support draft, published, noindex, or similar frontmatter flags.

To achieve a true "coming soon" placeholder without publication, either:

1. Move this file to _archive/ (which is effectively excluded from getBlogPosts()), or
2. Add support for a draft: true or published: false field and filter it in the blog query logic.

🤖 Prompt for AI Agents

In `@apps/marketing/content/blog/coming-soon.mdx` around lines 1 - 7, The
coming-soon.mdx file currently lives in the root blog directory and will be
picked up by getBlogPosts(), so either move this file into the _archive/
directory to exclude it from getBlogPosts() and feeds/sitemaps, or add a
draft/published frontmatter field (e.g., draft: true or published: false) to
coming-soon.mdx and update getBlogPosts() to filter out posts with draft ===
true or published === false before returning results; modify the code path in
getBlogPosts() where frontmatter is read to apply this filter so drafts are
ignored by listings, RSS (/feed.xml), and sitemaps.

[github-actions]

🧹 Preview Cleanup Complete

The following preview resources have been cleaned up:

• ✅ Neon database branch
• ✅ Electric Fly.io app

Thank you for your contribution! 🎉