FoilAll posts
meta

Hello, Foil — what this blog is for

A short post to verify the MDX pipeline and explain the editorial premise: practical, evidence-driven posts on Pokémon card valuation.

title: "Hello, Foil — what this blog is for" description: "A short post to verify the MDX pipeline and explain the editorial premise: practical, evidence-driven posts on Pokémon card valuation." date: "2026-05-20" tags: ["meta"] pillar: "pokemon-card-value-calculator"

This is the first post on the Foil blog. It also doubles as a smoke test for the MDX pipeline — every custom component the blog supports renders below.

What this blog is for

The Foil scanner answers one question fast: what is this Pokémon card actually worth right now? This blog is for the questions that need more than a single number — how to read a Japanese set code, why a PSA 9 sometimes outsells a PSA 10, and how to spot the cards that are quietly worth more than the listing.

Things the components do

Below is the full set of MDX building blocks. If you're reading this on the live site, all three should be styled.

Inline scanner

When a post leads to a clear buying decision, the inline scanner is the call to action:

Foil scanner

Scan a card now

Snap one card. Foil reads the printed name, set code, and collector number — and returns eBay + TCGplayer + graded comps in under 10 seconds.

Try the scanner

You can also override the copy per-post, when the prompt should be more specific:

Foil scanner

Got a Japanese card you can't read?

Foil reads the set code and collector number — you don't need to translate the name.

Scan a Japanese card

Topic links

Cross-links between posts use TopicLink so the cluster graph is visually obvious:

Markdown still works

A regular bulleted list:

  • Charizard, Base Set, 4/102 — the obvious one.
  • Lugia, Neo Genesis, 9/111 — the underrated one.
  • Umbreon Gold Star, POP Series 5, 17/17 — the absurd one.

And a code block, for the rare times we need one:

const card = {
  name: "Charizard",
  setCode: "BS",
  collectorNumber: "4/102",
};

That's it. The pipeline works.