feat: add Introducing Volvox Bot blog post#232
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughAdds a new blog post MDX file with frontmatter, an introduction, setup instructions, feature sections, launch and FAQ content, and a closing community invitation. ChangesBlog post content
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
Claude finished @EleftheriaBatsou's task in 2m 47s —— View job PR Review: Add Introducing Volvox Bot Blog PostTasks
SummaryGreat blog post introducing Volvox.Bot! The content is well-structured with clear sections, helpful FAQs, and good SEO optimization for Discord-related keywords. I found and fixed two issues: Fixed issues (committed):
What looks good:
No additional changes needed. The blog post is ready to merge after the Vercel build completes successfully. | |
|
| Filename | Overview |
|---|---|
| content/blog/introducing-volvox-bot.mdx | New blog post for Volvox.Bot launch. Frontmatter is well-formed: slug matches the lowercase filename, authorId "2" matches existing convention, banner path aligns with the new image asset, and no unknown fields are present. |
| public/images/blog/volvox-bot-live.png | New banner image referenced correctly by the blog post frontmatter. No issues. |
Reviews (2): Last reviewed commit: "fix: rename blog file to lowercase and r..." | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| @@ -0,0 +1,153 @@ | |||
| --- | |||
There was a problem hiding this comment.
The file is named Introducing-volvox-bot.mdx (capital I), but every other blog post in content/blog/ uses an all-lowercase filename. getPostBySlug constructs the file path as `${validSlug}.mdx` where validSlug is always lowercased by normalizeSlug (see src/lib/validation.ts line 15). On a Linux production server the path introducing-volvox-bot.mdx will not match the actual file Introducing-volvox-bot.mdx, so the post returns a 404. Rename the file to introducing-volvox-bot.mdx to match the convention used by every other post.
Prompt To Fix With AI
This is a comment left during a code review.
Path: content/blog/Introducing-volvox-bot.mdx
Line: 1
Comment:
**Uppercase filename breaks post lookup on case-sensitive filesystems**
The file is named `Introducing-volvox-bot.mdx` (capital `I`), but every other blog post in `content/blog/` uses an all-lowercase filename. `getPostBySlug` constructs the file path as `` `${validSlug}.mdx` `` where `validSlug` is always lowercased by `normalizeSlug` (see `src/lib/validation.ts` line 15). On a Linux production server the path `introducing-volvox-bot.mdx` will not match the actual file `Introducing-volvox-bot.mdx`, so the post returns a 404. Rename the file to `introducing-volvox-bot.mdx` to match the convention used by every other post.
How can I resolve this? If you propose a fix, please make it concise.
| @@ -0,0 +1,153 @@ | |||
| --- | |||
| title: "Introducing Volvox.Bot: AI-Powered Discord Management, Free for Everyone" | |||
There was a problem hiding this comment.
description is not a recognized frontmatter field
BlogPostFrontmatterSchema in src/lib/schemas.ts does not include a description field, so this value is silently stripped by Zod on every parse and is never stored, rendered, or used anywhere in the app. No other blog post uses this field. Consider removing it or, if it was intended to replace excerpt for SEO meta tags, check whether the schema and rendering layer need to be updated to support it.
Prompt To Fix With AI
This is a comment left during a code review.
Path: content/blog/Introducing-volvox-bot.mdx
Line: 2
Comment:
**`description` is not a recognized frontmatter field**
`BlogPostFrontmatterSchema` in `src/lib/schemas.ts` does not include a `description` field, so this value is silently stripped by Zod on every parse and is never stored, rendered, or used anywhere in the app. No other blog post uses this field. Consider removing it or, if it was intended to replace `excerpt` for SEO meta tags, check whether the schema and rendering layer need to be updated to support it.
How can I resolve this? If you propose a fix, please make it concise.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
| @@ -0,0 +1,153 @@ | |||
| --- | |||
| title: "Introducing Volvox.Bot: AI-Powered Discord Management, Free for Everyone" | |||
| description: "Meet Volvox.Bot — a free, fully hosted AI Discord bot with chat, moderation, user memory, analytics, support tickets, leaderboards, and more. The easiest way to add a bot to your Discord server." | |||
There was a problem hiding this comment.
Remove unused field: The description field is not part of the BlogPostFrontmatterSchema and will be ignored. The excerpt field (line 5) serves this purpose.
| description: "Meet Volvox.Bot — a free, fully hosted AI Discord bot with chat, moderation, user memory, analytics, support tickets, leaderboards, and more. The easiest way to add a bot to your Discord server." |
- Rename Introducing-volvox-bot.mdx to introducing-volvox-bot.mdx to match slug convention and ensure getPostBySlug() works on Linux (case-sensitive) - Remove unused 'description' field from frontmatter (not in schema) Co-authored-by: Eleftheria Batsou <EleftheriaBatsou@users.noreply.github.com>
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@content/blog/Introducing-volvox-bot.mdx`:
- Line 15: The opening line in the blog post uses a relative launch reference
(“Today”) that will become stale over time. Update the intro text in the
Volvox.Bot announcement to use the explicit publish date or rephrase it to
remove the time-relative wording, keeping the rest of the introduction intact.
- Line 37: The CTAs in the blog post use a bare URL instead of descriptive link
text, which hurts readability; update the linked text in the relevant markdown
content (including the repeated CTA later in the file) to use labeled markdown
links instead of showing the raw URL, so the link destination remains the same
but the anchor text is descriptive.
- Around line 103-107: The competitor comparison copy in the blog post is
written as evergreen fact, so qualify the statements in the sections around
Volvox.Bot, MEE6, and Dyno with a time-bound phrase such as “as of June 26,
2026” or “at launch.” Update the affected marketing claims in the relevant prose
blocks so they read as current-context comparisons rather than permanent truths,
keeping the rest of the messaging intact.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: a7e5288d-f7f6-4022-aaca-929186928cf6
⛔ Files ignored due to path filters (1)
public/images/blog/volvox-bot-live.pngis excluded by!**/*.png
📒 Files selected for processing (1)
content/blog/Introducing-volvox-bot.mdx
|
|
||
| # Introducing Volvox.Bot: Our AI-Powered Discord Bot | ||
|
|
||
| Today, we're excited to officially introduce **Volvox.Bot** — our fully hosted AI-powered Discord bot built to make community management easier, smarter, and completely hassle-free. |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Replace the relative launch reference.
Line 15’s “Today” will read stale once the post is no longer new. Use the explicit publish date or remove the relative wording.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@content/blog/Introducing-volvox-bot.mdx` at line 15, The opening line in the
blog post uses a relative launch reference (“Today”) that will become stale over
time. Update the intro text in the Volvox.Bot announcement to use the explicit
publish date or rephrase it to remove the time-relative wording, keeping the
rest of the introduction intact.
|
|
||
| Adding Volvox.Bot takes just a few minutes. | ||
|
|
||
| 1. Visit **https://volvox.bot** |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Use descriptive links instead of bare URLs.
Bare URLs are harder to scan and give less context than labeled links. Turn both CTAs into markdown links.
Suggested edit
-1. Visit **https://volvox.bot**
+1. Visit [volvox.bot](https://volvox.bot)
-👉 https://www.producthunt.com/products/volvox-bot
+👉 [View Volvox.Bot on Product Hunt](https://www.producthunt.com/products/volvox-bot)Also applies to: 119-119
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@content/blog/Introducing-volvox-bot.mdx` at line 37, The CTAs in the blog
post use a bare URL instead of descriptive link text, which hurts readability;
update the linked text in the relevant markdown content (including the repeated
CTA later in the file) to use labeled markdown links instead of showing the raw
URL, so the link destination remains the same but the anchor text is
descriptive.
| Most server owners running **Discord server bots** end up with a stack — MEE6 for leveling, Dyno for moderation, a separate analytics bot, a ticketing bot. Each with its own dashboard and pricing. | ||
|
|
||
| MEE6 is great for leveling but locks AI chat and analytics behind a paid plan. Dyno is solid for moderation but has no AI capabilities at all. Neither offers user memory or conversation summaries. | ||
|
|
||
| [Volvox.Bot](https://volvox.bot/) brings all of it together — for free. |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Time-box the competitor comparisons.
These claims read as evergreen facts, but competitor pricing and feature sets can change. Qualify them with “at launch” / “as of June 26, 2026” so the post doesn’t age into inaccurate copy.
Also applies to: 131-135
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@content/blog/Introducing-volvox-bot.mdx` around lines 103 - 107, The
competitor comparison copy in the blog post is written as evergreen fact, so
qualify the statements in the sections around Volvox.Bot, MEE6, and Dyno with a
time-bound phrase such as “as of June 26, 2026” or “at launch.” Update the
affected marketing claims in the relevant prose blocks so they read as
current-context comparisons rather than permanent truths, keeping the rest of
the messaging intact.
🤖 Morph Preview TestPreview URL: https://volvox-website-3qttz20i4-volvox-llc.vercel.app AI SummaryIssues:
Verified:
RecordingAutomated testing by Morph |
2 participants
Added the new article for volvox bot