<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: CodeByAby</title>
    <description>The latest articles on DEV Community by CodeByAby (@codebyaby).</description>
    <link>https://dev.to/codebyaby</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3656992%2Fe4b51ffe-3ca2-424e-81a8-a3ed3a7206d3.png</url>
      <title>DEV Community: CodeByAby</title>
      <link>https://dev.to/codebyaby</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/codebyaby"/>
    <language>en</language>
    <item>
      <title>I built a fact-checked meme explainer site with Next.js static export (and structured data for LLMs)</title>
      <dc:creator>CodeByAby</dc:creator>
      <pubDate>Fri, 09 Oct 2026 13:17:21 +0000</pubDate>
      <link>https://dev.to/codebyaby/i-built-a-fact-checked-meme-explainer-site-with-nextjs-static-export-and-structured-data-for-llms-4c0e</link>
      <guid>https://dev.to/codebyaby/i-built-a-fact-checked-meme-explainer-site-with-nextjs-static-export-and-structured-data-for-llms-4c0e</guid>
      <description>&lt;p&gt;When a meme goes viral, the search intent is simple: what is this, where is it from, is it real? That’s an ideal case for a small static reference site. I built one for the Rumpelstiltskin AI meme, and here’s the setup.&lt;/p&gt;

&lt;p&gt;Stack: Next.js 15 App Router with output: "export", plain CSS, no database, deployed as static files.&lt;/p&gt;

&lt;p&gt;Page contract (one topic per page):&lt;/p&gt;

&lt;p&gt;A short answer band at the top, so the verdict is the first thing a crawler or an LLM reads.&lt;br&gt;
A facts list (&lt;/p&gt;
&lt;dl&gt;) with explicit “not disclosed” values instead of guesses.&lt;br&gt;
Sections, FAQ, and a sources block.

&lt;p&gt;Structured data: every page ships FAQPage and BreadcrumbList JSON-LD plus an article schema, generated from the same data that renders the visible FAQ so the two never drift.&lt;/p&gt;

&lt;p&gt;Meta consistency: a single pageMeta() helper sets canonical, OG and Twitter tags, and pages can’t ship without it.&lt;/p&gt;

&lt;p&gt;Citations as data: each fact maps to an entry in a SOURCES list, and off-site links go through one ExternalLink component (new tab, rel="noopener", no noreferrer, so cited sites can see the referrer).&lt;/p&gt;

&lt;p&gt;Live example, the &lt;a href="https://rumpelstiltskinmemes.com/" rel="noopener noreferrer"&gt;Rumpelstiltskin meme&lt;/a&gt; explained, with a &lt;a href="https://rumpelstiltskinmemes.com/rumpelstiltskin-meme-timeline" rel="noopener noreferrer"&gt;timeline page&lt;/a&gt; that sets sources side by side where they disagree.&lt;/p&gt;

&lt;p&gt;Happy to share the pageMeta() and JSON-LD components if useful. What do you use for keeping structured data in sync with visible content?&lt;/p&gt;


&lt;/dl&gt;

</description>
      <category>nextjs</category>
      <category>seo</category>
      <category>webdev</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
