πΈ Rybbit - open-source and privacy-friendly alternative to Google Analytics that is 10x more intuitive.
blog2 (#545)
Bill Yang79135c08a47a
diff --git a/.claude/settings.local.json b/.claude/settings.local.jsonindex 0b1d97db0..fde262917 100644--- a/.claude/settings.local.json+++ b/.claude/settings.local.json@@ -32,7 +32,8 @@"Bash(npm init:*)","Bash(cp:*)","Bash(-print)",- "Bash(python3:*)"+ "Bash(python3:*)",+ "WebFetch(domain:github.com)"]},"enableAllProjectMcpServers": falsediff --git a/docs-v2/content/blog/5k-stars.mdx b/docs-v2/content/blog/5k-stars.mdxnew file mode 100644index 000000000..3232e14dc--- /dev/null+++ b/docs-v2/content/blog/5k-stars.mdx@@ -0,0 +1,56 @@+---+title: Getting 5,000 Stars in 9 days+date: 2025-05-26+description: How Rybbit got 5,000 Github stars in 9 days with zero marketing effort+tags: ['growth']+author: Bill Yang+---++# How my open source SaaS got 5,000 Github stars in 9 days with zero marketing effort++<img src="/blog/5kstars.png" alt="5k stars" />++## The backstory++I run an open source web analytics platform with a freemium hosted version. I have a gaming stats site that gets around 1.5 million visits a month, so I needed serious web analytics. The existing platforms were either too simple (just a basic dashboard) or too complicated and enterprisey, so I decided to build my own web analytics platform since I love stats anyway.++I started working on it in January 2025, and it took around 110 days for me to launch. Rybbit being open source made the distribution problem so much easier, as I could freely advertise it in many places since it was self-hostable and free to use.++## The launch strategy++I made posts on 2 major subreddits - r/SideProject and r/selfhosted, plus a few smaller subs. Pretty much every post reached #1 in hot and I probably got 150k free impressions from this.++**TL;DR** - all I did was make like 4 Reddit posts with the same headline, got 150k free impressions, and then proceeded to go viral on X, Hacker News, Bluesky, Mastodon, and some random Asian language sites from other people sharing my project.++## What I think I did right++### 1. Full iframe embed as hero section+I put a full iframe embed of my demo site as my hero section. A lot of analytics platforms have a demo site, but I went a step further by embedding the entire demo site into the landing page so any visitor is immediately greeted by a full demo of the product. I haven't ever seen anyone do this, but I think this is an insane hack if this suits your product.++### 2. Visual-first GitHub README+I included a ton of product screenshots on my GitHub README and kept the text content short since I had a landing and docs page. People have short attention spans and aren't gonna read a wall of text.++### 3. Catchy positioning+I used the post title "I built an open source Google Analytics replacement" - simple but effective positioning that immediately communicates the value.++### 4. Strong visual assets+I created a good OpenGraph image that showed the best features of the product, which helped with social sharing.++### 5. Polish matters+I had a genuinely good & polished product with a fully functional landing page, docs, self-hosting guide, and SaaS product that I personally use every single day. I doubt I would've gotten as much traction if I released a barely-working MVP after a few weeks.++## What didn't work++I made a couple launch posts from my X account, but I only had a couple hundred followers so nobody cared (though I didn't expect to go viral on X in the first place).++Some big Discord servers like the Next.js server have #showcase channels. Literally nobody reads these.++## The results and reality check++I optimized my launch for reach instead of revenue, so I wasn't surprised that I didn't get a huge surge of paid plan signups. The vast majority of people are self-hosting it since my most viral post was in r/selfhosted. I'm just playing the numbers game and hoping that a small single-digit percentage of people who see it will pay for the cloud version.++So far I have around 700 total signups and $900 in total revenue in 3 weeks - not life-changing money, but solid validation.++## What's next++The virality cooled down after the first week, but the organic growth is still going strong. I'm at 5.8k stars 3 weeks post-launch, so the daily gain is still around ~50 stars. I expect to hit 10k stars in around 3 months.\ No newline at end of filediff --git a/docs-v2/content/blog/_meta.js b/docs-v2/content/blog/_meta.jsnew file mode 100644index 000000000..97e9ea754--- /dev/null+++ b/docs-v2/content/blog/_meta.js@@ -0,0 +1,6 @@+export default {+ "5k-stars":+ "How my open source SaaS got 5,000 Github stars in 9 days with zero marketing effort",+ "website-traffic-drop":+ "Why did my website traffic drop?"+};\ No newline at end of filediff --git a/docs-v2/content/blog/website-traffic-drop.mdx b/docs-v2/content/blog/website-traffic-drop.mdxnew file mode 100644index 000000000..5a4c84ccf--- /dev/null+++ b/docs-v2/content/blog/website-traffic-drop.mdx@@ -0,0 +1,225 @@+---+title: Why did my website traffic drop?+date: 2025-06-08+description: Find out why your website traffic dropped using Rybbit+tags: ['traffic', 'analytics']+author: Bill Yang+---++If you are reading this article right now you are probably panicking about a recent drop in traffic, while this is a reasonable response, it is possible to reverse engineer why your traffic has dropped and to apply the correct measures to remediate the issue.++Don't panic just yet β traffic drops happen to literally every website owner at some point. Maybe you got hit by a Google algorithm update, something technical went wrong, your site is responding to seasonal trends, or maybe you just need to create better content. Whatever it is, we can figure it out.++To properly investigate what's going on, you'll need a solid analytics tool. We obviously recommend Rybbit (and we'll show you exactly how to use it), plus you'll want access to an SEO tool and Google Search Console. By walking through Rybbit's specific features, we'll show you how to diagnose what's actually causing your traffic to tank.++## **What Usually Causes Traffic Drops**++Before we dive into the detective work, let's talk about the usual suspects:++**Google Algorithm Updates** Google loves to shake things up with algorithm updates. Sometimes these hit like a truck β one day you're ranking great, the next day you've disappeared from page one. These updates can target specific types of content, keywords, or entire industries.++**Technical Website Problems** Maybe your site is loading slow, or maybe your ad network decided to put ads everywhere. Could be your server is having issues, or something broke during a recent update. Technical problems are actually pretty common reasons for traffic drops.++**Manual Penalties from Google** If you've been playing fast and loose with SEO β buying sketchy backlinks, keyword stuffing, or copying content β Google's manual review team might have slapped you with a penalty.++**Negative SEO Attacks** Sometimes competitors will try to hurt your rankings by pointing spammy backlinks at your site or other nasty tactics. It's not super common, but it happens.++## **Step 1: Is it really a traffic drop or just a trend?**++First things first β let's figure out if this is actually a sudden drop or if traffic has been slowly declining over time.++###### *Main:*++First, take a look at the amount of traffic that has dropped. You can use the main tab on Rybbit to find this information:++Head to your [main tab](https://demo.rybbit.io/1/main) in Rybbit and start looking at different time periods:++* Compare the last 7 days to the week before+* Look at the past 30 days versus the 30 days before that+* If you have the data, check year-over-year numbers++<img src="/blog/main.png" alt="Rybbit's main dashboard" />++What you're looking for here is patterns. Is this a sudden cliff where traffic just fell off overnight? Or has it been a gradual slide? If it's sudden, definitely check Google's Search Status page to see if they were having crawling or indexing issues around the same time.++## **Step 2: Which pages are getting affected?**++You should first ascertain which pages have seen drops in traffic, it's quite likely that not all of your pages have dropped in traffic. You can easily do this by clicking the pages tab on the left hand panel and you will see a list of pages on your website, you can view traffic over time using the graph that is embedded in the row, you can see any drops or any dips throughout a 24 hour period up until the current time.++**What to look for:**++* **Sitewide drops** β If every page's traffic trend is going down, you're probably dealing with a technical issue or algorithm update that hits your whole site.+* **Specific page problems** β If only certain pages are hurting, focus on those. Maybe the content is outdated, or there are page-specific technical issues.+* **Pattern recognition** β Are all your blog posts down? Product pages? Homepage traffic? The pattern tells you where to focus your efforts.++The embedded graphs make it super easy to spot which pages used to get steady traffic but suddenly tanked. Those are your priority pages to investigate further.++<img src="/blog/pages.png" alt="Rybbit's page tab" />++## **Step 3: Assessing Technical Performance**++If this is really the reason why your website dropped in traffic, then count yourself lucky. Oftentimes this is an easy problem to fix, your website might be slower than usual, or a component might not be working properly and this is causing your bounce rate to be higher than usual or is causing people to drop from your website due to poor performance.++#### Using Rybbit to investigate:++Rybbit has several great features that allow you to investigate potential technical issues that could be causing your website to drop in traffic:++###### *Performance:*++<img src="/blog/performancedashboard.png" alt="Rybbit's performance dashboard" />++If you notice that one of your pages has tanked in performance, you can use the performance tab to find the LCP (LCP measures loading performance. LCP marks the time when the largest content element becomes visible in the viewport.), if a page has a really high LCP, it's likely that people are simply deciding not to go on the page.++Once you recognize that a certain page has performance issues, you can begin the process of fixing the issue.++## **Step 4: Which channels have drops in traffic**++### **Identify Which Traffic Sources Are Affected**++Understanding which channels are contributing to your traffic decline is crucial for focusing your investigation efforts. You can use the filter function on each channel to look for trends:++<img src="/blog/channelfilter.png" alt="Rybbit's Channel Filter feature" />++(Example: I set the filter to use Channel is Organic Search to look for any drops, the graph shows that traffic has actually grown over the past 14 days).++Pay special attention to which sources show the steepest declines. Organic search drops are typically the most impactful and require the most thorough investigation.++### Filtering on referrers:++You can likely find even more actionable information if you filter on referrers as well, as you can see here we set the filter to only look for events that have Google as a referrer.+<img src="/blog/referrerfilter.png" alt="Rybbit's referrer filter" />++## **Step 5: Is the drop in certain geographies or devices or timeframes?**++Once you have identified if the drop is truly a drop and pages have been affected, you should start looking for any patterns in geographics or devices, use Rybbit's filter function to filter on device type as well as country:++<img src="/blog/countryfilter.png" alt="Rybbit's country filter" />+(Using Rybbit to filter for a specific country)++<img src="/blog/devicefilter.png" alt="Rybbit's device filter" />++(Using Rybbit to filter for a specific device type).+You can also use set time filter on custom range to compare different time frames:+<img src="/blog/customdaterange.png" alt="Rybbit's custom date range filter" />++## **Step 5: Digging Into Specific Scenarios**++## Google Algorithm Updates++Google rolls out algorithm updates silently many times a year, you probably won't notice most of them as they don't necessarily target all keywords or all topics. However, you might get unlucky and get hit by a drop in the SERPs due to an update that hits your particular topic or website particularly harshly.++You can monitor core updates in the [Google Search Status Dashboard](https://status.search.google.com/products/rGHU1u87FJnkP6W2GwMi/history) and see if it correlates with your website's drop in traffic, it might not be one to one, but it should be fairly close to the time of the traffic drop. You should read [Google core updates](https://developers.google.com/search/updates/core-updates) to understand better what a core update is and assess whether you think your traffic has dropped due to a core update or not.++#### How would you go about fixing this?++The simple truth is that fixing your website and content for a Google algorithm update is not going to have a one size fits all solution, in most cases you are probably going to notice that not all pages have had any drops in traffic. You will probably notice that traffic drops are a few pages that might be outdated or perhaps are slow or have too many ads, in that case it would be quite easy to fix. In other cases it will be more difficult to understand why certain pages are losing traffic or why you lost rankings in certain keywords you were trying to rank for.++##### Check using an SEO Tool of your choice++SEO tools can be a valuable resource to find which keywords in particular you have lost rankings in. You can use Ahrefs or a tool like SemRush to find keywords that have lost ranking.++## Website technical issues++If technical problems are behind your traffic drop, count yourself lucky. These are usually fixable.++**Common technical problems:**++* Site loading too slowly+* Pages returning error codes+* Mobile site not working properly+* Recent changes that broke something++**Using Rybbit to spot technical issues:**++* Performance tab shows you which pages are loading slowly+* Pages tab shows you if the drop happened right after you made changes to your site+* Main dashboard can show you if mobile vs desktop traffic patterns are different++## Manual Penalty++A manual penalty on Google is a manual action that reduces or demotes your website in Google Search Rankings (SERPs). These are pretty hard to get, and most if not all gray hat actions that people take such as buying backlinks or spamming won't cause a manual penalty at first. So you must have really screwed up to get to this point.++###### *What could be the cause (Be honest with yourself):*++- Backlink purchasing \- If you have ever bought a backlink from a shady website or Fiverr?+- Have you ever published a bunch of pages worth of spam?+- Keyword stuffing to rank for a keyword?+- Used a tool to spam the internet to increase the amount of backlinks?+- Stole content from another website?++If so, you could be facing a manual penalty.++###### *How do I go about fixing this?*++First, calm down and breathe.++Second, go ahead and understand what the cause is:++- Go to your Search console and open the manual action report to see what the issue is exactly.+- Find which pages the penalty applies to.+- Fix every single problem that Google has detected on your website:+ - Remove any suspicious backlinks+ - Remove stolen content.+ - Get rid of keywords you stuffed in the page.+ - Get rid of any spam.++- Next, click "Request review" on the console and spell out exactly what you did to fix the problem and be patient.++Google is strict, but fair, and most likely if you fix the issues correctly and do not engage in any Blackhat SEO again Google will give you a second chance. Be sure not to buy any more links on Fiverr or anything stupid again, or else Google might just permanently send your site to the bottom of the SERPs forever.++## Negative SEO++A competitor may be conducting a negative SEO campaign against you, usually by:++###### *Spamming bad backlinks towards your domain:*++If you noticed a huge increase in backlinks from random spammy domains, or perhaps see a huge surge in backlink count despite you not having done anything to get them. It's possible you might have been targeted by negative SEO.++**Warning signs:**++* Sudden spike in backlinks from sketchy sites+* Your link profile shows tons of links you never built+* The timing aligns with when a competitor might be motivated to hurt you++**What to do:**++* Use Google's Disavow Tool to tell Google to ignore the bad links+* Document everything in case you need to file a reconsideration request+* Be patient β it can take months for Google to process disavowed links++## **Making Sense of Your Traffic Numbers**++Not every traffic drop is worth panicking over. Here's how to tell if you should be worried:++**Small sites (under 10,000 monthly visitors):** A 10% drop might only mean 50-100 fewer visitors. That could just be normal fluctuation.++**Medium sites (10,000-100,000 monthly visitors):** Focus more on percentage changes and which pages are affected. A 20% drop here is worth investigating.++**Large sites (100,000+ monthly visitors):** Even small percentage drops represent thousands of visitors, so take any consistent decline seriously.++**Industry context matters too:** News sites naturally have more volatile traffic than, say, a local plumber's website. E-commerce sites have seasonal patterns. SaaS companies usually expect steady growth, so any drop is concerning.++## **Red Flags That Need Immediate Attention**++Drop everything and investigate immediately if you see:++* **More than 50% traffic drop** (unless you know there's a seasonal reason)+* **Complete disappearance** from Google for your main keywords+* **Week-over-week declines** for more than a month+* **Technical errors** that are affecting how your site works++## **Conclusion**++Traffic drops are a natural part of website ownership, but they don't have to be devastating. With the right investigative approach using tools like Rybbit, you can quickly identify the causes and take corrective action.++Remember that Rybbit's strength lies in its detailed page-level analytics and performance monitoring capabilities. The combination of traffic analysis through the Main dashboard, page-specific investigation through the Pages tab, and technical performance review through the Performance tab gives you a comprehensive toolkit for understanding and addressing traffic declines.++The key is to approach the investigation systematically:++1. **Don't panic** \- Traffic fluctuations are normal+2. **Use data** \- Let Rybbit's analytics guide your investigation rather than making assumptions+3. **Focus on the biggest impacts** \- Address the most significant issues first+4. **Monitor recovery** \- Track the effectiveness of your fixes+5. **Learn for the future** \- Use the experience to build better monitoring and prevention strategies++Most importantly, remember that while traffic drops can be concerning, they often provide valuable insights into how to improve your website's performance, content quality, and user experience. With Rybbit's detailed analytics at your disposal, you're well-equipped to not just recover from traffic drops, but to build a stronger, more resilient web presence.\ No newline at end of filediff --git a/docs-v2/public/blog/5kstars.png b/docs-v2/public/blog/5kstars.pngnew file mode 100644index 000000000..ae1e71a01Binary files /dev/null and b/docs-v2/public/blog/5kstars.png differdiff --git a/docs-v2/public/blog/channelfilter.png b/docs-v2/public/blog/channelfilter.pngnew file mode 100644index 000000000..b64b96d4aBinary files /dev/null and b/docs-v2/public/blog/channelfilter.png differdiff --git a/docs-v2/public/blog/countryfilter.png b/docs-v2/public/blog/countryfilter.pngnew file mode 100644index 000000000..96fcb345cBinary files /dev/null and b/docs-v2/public/blog/countryfilter.png differdiff --git a/docs-v2/public/blog/customdaterange.png b/docs-v2/public/blog/customdaterange.pngnew file mode 100644index 000000000..e6773be5aBinary files /dev/null and b/docs-v2/public/blog/customdaterange.png differdiff --git a/docs-v2/public/blog/devicefilter.png b/docs-v2/public/blog/devicefilter.pngnew file mode 100644index 000000000..c9a118a9eBinary files /dev/null and b/docs-v2/public/blog/devicefilter.png differdiff --git a/docs-v2/public/blog/main.png b/docs-v2/public/blog/main.pngnew file mode 100644index 000000000..002ea49b9Binary files /dev/null and b/docs-v2/public/blog/main.png differdiff --git a/docs-v2/public/blog/pages.png b/docs-v2/public/blog/pages.pngnew file mode 100644index 000000000..ae4d418ecBinary files /dev/null and b/docs-v2/public/blog/pages.png differdiff --git a/docs-v2/public/blog/performancedashboard.png b/docs-v2/public/blog/performancedashboard.pngnew file mode 100644index 000000000..4a82871f7Binary files /dev/null and b/docs-v2/public/blog/performancedashboard.png differdiff --git a/docs-v2/public/blog/referrerfilter.png b/docs-v2/public/blog/referrerfilter.pngnew file mode 100644index 000000000..bcccbd8a2Binary files /dev/null and b/docs-v2/public/blog/referrerfilter.png differdiff --git a/docs-v2/source.config.ts b/docs-v2/source.config.tsindex 866a32c72..22c9ddffb 100644--- a/docs-v2/source.config.ts+++ b/docs-v2/source.config.ts@@ -4,20 +4,23 @@ import {frontmatterSchema,metaSchema,} from 'fumadocs-mdx/config';+import { z } from 'zod';-// You can customise Zod schemas for frontmatter and `meta.json` here-// see https://fumadocs.vercel.app/docs/mdx/collections#define-docs-export const docs = defineDocs({- docs: {- schema: frontmatterSchema,- },- meta: {- schema: metaSchema,- },+export const { docs, meta } = defineDocs({+ dir: 'content/docs',});-export default defineConfig({- mdxOptions: {- // MDX options+// Blog collection - separate from docs+export const blog = defineDocs({+ dir: 'content/blog',+ docs: {+ schema: frontmatterSchema.extend({+ date: z.string().date().or(z.date()),+ author: z.string().optional(),+ image: z.string().optional(),+ tags: z.array(z.string()).optional(),+ }),},});++export default defineConfig();diff --git a/docs-v2/src/app/blog/[...slug]/page.tsx b/docs-v2/src/app/blog/[...slug]/page.tsxnew file mode 100644index 000000000..669e1a349--- /dev/null+++ b/docs-v2/src/app/blog/[...slug]/page.tsx@@ -0,0 +1,126 @@+import { notFound } from 'next/navigation';+import { blogSource } from '@/lib/blog-source';+import Link from 'next/link';+import Image from 'next/image';+import { ChevronLeft } from 'lucide-react';+import type { Metadata } from 'next';+import defaultMdxComponents from 'fumadocs-ui/mdx';+import { Pre } from 'fumadocs-ui/components/codeblock';++export function generateStaticParams() {+ return blogSource.getPages().map((page) => ({+ slug: page.slugs,+ }));+}++export async function generateMetadata(props: { params: Promise<{ slug: string[] }> }): Promise<Metadata> {+ const params = await props.params;+ const page = blogSource.getPage(params.slug);+ if (!page) return {};++ return {+ title: page.data.title,+ description: page.data.description,+ };+}++export default async function BlogPostPage(props: { params: Promise<{ slug: string[] }> }) {+ const params = await props.params;+ const page = blogSource.getPage(params.slug);++ if (!page) {+ notFound();+ }++ const MDXContent = page.data.body;+ const date = page.data.date ? new Date(page.data.date) : null;++ return (+ <article className="max-w-4xl mx-auto px-4 py-16">+ <Link+ href="/blog"+ className="inline-flex items-center text-neutral-400 hover:text-white transition-colors mb-8"+ >+ <ChevronLeft className="w-4 h-4 mr-1" />+ Back to Blog+ </Link>++ <header className="mb-12">+ <h1 className="text-4xl md:text-5xl font-bold mb-4">+ {page.data.title}+ </h1>++ {page.data.description && (+ <p className="text-xl text-neutral-400 mb-6">+ {page.data.description}+ </p>+ )}++ <div className="flex items-center gap-4 text-sm text-neutral-500 pb-6 border-b border-neutral-800">+ {date && (+ <time dateTime={date.toISOString()}>+ {date.toLocaleDateString('en-US', {+ year: 'numeric',+ month: 'long',+ day: 'numeric',+ })}+ </time>+ )}++ {page.data.author && (+ <>+ <span>β’</span>+ <span>By {page.data.author}</span>+ </>+ )}++ {page.data.tags && page.data.tags.length > 0 && (+ <>+ <span>β’</span>+ <div className="flex gap-2">+ {page.data.tags.map((tag: string) => (+ <span+ key={tag}+ className="px-2 py-1 text-xs rounded-full bg-neutral-800 text-neutral-300"+ >+ {tag}+ </span>+ ))}+ </div>+ </>+ )}+ </div>+ </header>++ {page.data.image && (+ <Image+ src={page.data.image}+ alt={page.data.title}+ width={1200}+ height={400}+ className="w-full h-96 object-cover rounded-lg mb-8"+ />+ )}++ <div className="prose prose-invert prose-lg max-w-none+ prose-code:before:content-none prose-code:after:content-none+ [&_pre]:my-4 [&_pre]:overflow-x-auto">+ <MDXContent components={{+ ...defaultMdxComponents,+ pre: (props: React.ComponentPropsWithoutRef<'pre'>) => (+ <Pre {...props} className="bg-neutral-900 border border-neutral-800 rounded-lg" />+ ),+ code: ({ className, ...props }: React.ComponentPropsWithoutRef<'code'>) => {+ // Check if this code is inside a pre tag (code block)+ const isCodeBlock = className?.includes('language-');+ if (isCodeBlock) {+ return <code className={className} {...props} />;+ }+ // Inline code+ return <code className="bg-neutral-900 px-1.5 py-0.5 rounded text-sm" {...props} />;+ },+ }} />+ </div>+ </article>+ );+}\ No newline at end of filediff --git a/docs-v2/src/app/blog/layout.tsx b/docs-v2/src/app/blog/layout.tsxnew file mode 100644index 000000000..02ca1338e--- /dev/null+++ b/docs-v2/src/app/blog/layout.tsx@@ -0,0 +1,15 @@+import type { ReactNode } from 'react';+import { CustomHeader } from '@/components/CustomHeader';+import { Footer } from '@/components/Footer';++export default function BlogLayout({ children }: { children: ReactNode }) {+ return (+ <>+ <CustomHeader />+ <main className="flex-1 min-h-screen">+ {children}+ </main>+ <Footer />+ </>+ );+}\ No newline at end of filediff --git a/docs-v2/src/app/blog/page.tsx b/docs-v2/src/app/blog/page.tsxnew file mode 100644index 000000000..a98cff271--- /dev/null+++ b/docs-v2/src/app/blog/page.tsx@@ -0,0 +1,101 @@+import Link from 'next/link';+import { blogSource } from '@/lib/blog-source';+import type { Metadata } from 'next';++export const metadata: Metadata = {+ title: 'Blog',+ description: 'Latest updates and insights from Rybbit',+};++export default function BlogPage() {+ const posts = [...blogSource.getPages()];++ // Sort posts by date (newest first)+ const sortedPosts = posts.sort((a, b) => {+ const dateA = new Date(a.data.date || 0);+ const dateB = new Date(b.data.date || 0);+ return dateB.getTime() - dateA.getTime();+ });++ return (+ <div className="max-w-6xl mx-auto px-4 py-16">+ <div className="mb-12">+ <h1 className="text-4xl font-bold mb-4">Blog</h1>+ <p className="text-xl text-neutral-400">+ Latest updates, tutorials, and insights from the Rybbit team+ </p>+ </div>++ <div className="grid gap-8 md:grid-cols-2 lg:grid-cols-3">+ {sortedPosts.map((post) => {+ const date = post.data.date ? new Date(post.data.date) : null;++ return (+ <Link+ key={post.slugs.join('/')}+ href={`/blog/${post.slugs.join('/')}`}+ className="group"+ >+ <article className="h-full bg-neutral-900 rounded-lg border border-neutral-800 p-6 hover:border-neutral-700 transition-all hover:-translate-y-1">+ {post.data.image && (+ <img+ src={post.data.image}+ alt={post.data.title}+ className="w-full h-48 object-cover rounded-lg mb-4"+ />+ )}++ <div className="flex flex-col h-full">+ <h2 className="text-xl font-semibold mb-2 group-hover:text-emerald-400 transition-colors">+ {post.data.title}+ </h2>++ {post.data.description && (+ <p className="text-neutral-400 mb-4 flex-grow">+ {post.data.description}+ </p>+ )}++ <div className="flex items-center justify-between text-sm text-neutral-500">+ {date && (+ <time dateTime={date.toISOString()}>+ {date.toLocaleDateString('en-US', {+ year: 'numeric',+ month: 'long',+ day: 'numeric',+ })}+ </time>+ )}++ {post.data.author && (+ <span>{post.data.author}</span>+ )}+ </div>++ {post.data.tags && post.data.tags.length > 0 && (+ <div className="flex flex-wrap gap-2 mt-4">+ {post.data.tags.map((tag: string) => (+ <span+ key={tag}+ className="px-2 py-1 text-xs rounded-full bg-neutral-800 text-neutral-300"+ >+ {tag}+ </span>+ ))}+ </div>+ )}+ </div>+ </article>+ </Link>+ );+ })}+ </div>++ {sortedPosts.length === 0 && (+ <div className="text-center py-12">+ <p className="text-neutral-400">No blog posts yet. Check back soon!</p>+ </div>+ )}+ </div>+ );+}\ No newline at end of filediff --git a/docs-v2/src/components/CustomHeader.tsx b/docs-v2/src/components/CustomHeader.tsxindex c41b64fe9..2ea999d34 100644--- a/docs-v2/src/components/CustomHeader.tsx+++ b/docs-v2/src/components/CustomHeader.tsx@@ -27,6 +27,9 @@ export function CustomHeader() {<Link href="/docs" className="text-sm font-base text-neutral-400 hover:text-white transition-colors">Docs</Link>+ <Link href="/blog" className="text-sm font-base text-neutral-400 hover:text-white transition-colors">+ Blog+ </Link><ahref="https://demo.rybbit.io/21"target="_blank"@@ -105,6 +108,13 @@ export function CustomHeader() {>Docs</Link>+ <Link+ href="/blog"+ className="block rounded-md px-3 py-2 text-base font-medium text-neutral-300 hover:bg-neutral-800 hover:text-white"+ onClick={() => setMobileMenuOpen(false)}+ >+ Blog+ </Link><ahref="https://demo.rybbit.io/21"target="_blank"diff --git a/docs-v2/src/components/mdx-content.tsx b/docs-v2/src/components/mdx-content.tsxnew file mode 100644index 000000000..640b0895e--- /dev/null+++ b/docs-v2/src/components/mdx-content.tsx@@ -0,0 +1,12 @@+'use client';++import { useMDXComponent } from 'fumadocs-ui/mdx/client';++interface MDXContentProps {+ children: string;+}++export function MDXContent({ children }: MDXContentProps) {+ const Component = useMDXComponent(children);+ return <Component />;+}\ No newline at end of filediff --git a/docs-v2/src/lib/blog-source.ts b/docs-v2/src/lib/blog-source.tsnew file mode 100644index 000000000..adfaa07a1--- /dev/null+++ b/docs-v2/src/lib/blog-source.ts@@ -0,0 +1,7 @@+import { loader } from "fumadocs-core/source";+import { blog } from "@/.source";++export const blogSource = loader({+ baseUrl: "/blog",+ source: blog.toFumadocsSource?.() ?? blog,+});diff --git a/docs-v2/src/lib/source.ts b/docs-v2/src/lib/source.tsindex dedc4be83..45991069e 100644--- a/docs-v2/src/lib/source.ts+++ b/docs-v2/src/lib/source.ts@@ -1,9 +1,10 @@-import { docs } from '@/.source';+import { docs, meta } from '@/.source';import { loader } from 'fumadocs-core/source';+import { createMDXSource } from 'fumadocs-mdx';// See https://fumadocs.vercel.app/docs/headless/source-api for more infoexport const source = loader({// it assigns a URL to your pagesbaseUrl: '/docs',- source: docs.toFumadocsSource(),+ source: createMDXSource(docs, meta),});