Data Dots — Product Concept
A visual flashcard system for data/analytics concepts, inspired by [[06-reference/2026-04-04-authority-nathan-barry|Nathan Barry's Authority]] model of building authority through teaching, and Chris Albon's AI Flashcards.
The Concept
Data Dots are atomic, visual concept cards — one concept per card with a Memphis-style illustration generated via Grok Imagine API. Each card has: name, one-paragraph definition, why it matters, and connected dots.
Three Product Layers
Layer 1: Public Pages (SEO + Authority)
Individual concept pages on raydata.co. Each is a short, standalone page optimized for search. Builds organic traffic over time. Free, no paywall.
Layer 2: Downloadable Dictionary (Lead Magnet → Agent Knowledge Base)
The full collection as a structured download (markdown, JSON, or PDF). The novel angle: "Download this so you can blend it into your own AI knowledge base." You're not just selling flashcards — you're selling a structured knowledge artifact that agents can consume. The value proposition shifts from "learn these concepts" to "give your AI context about data engineering."
This is the [[06-reference/2026-04-04-karpathy-llm-wiki-idea-file|Karpathy LLM Wiki]] pattern applied as a product: share the "idea file" and let the buyer's agent build on it.
Layer 3: Winning Formations (Data Visualization Playbook)
A sub-collection applying the [[06-reference/concepts/systems-over-goals|systems-over-goals]] pattern to data visualization. Each card shows:
- A data shape (the "formation" — like Xs and Os on a coach's playbook)
- The chart type it produces
- When to use it
- The insight it reveals
Built on the Grammar of Graphics framework (Leland Wilkinson, 1999):
- Data → Aesthetics → Geometry → Facets → Statistics → Coordinates → Theme
- Implementations: ggplot2 (R), Vega-Lite, Observable Plot, Altair (Python)
The reframe: "If your data looks like THIS shape, use THIS geometry to produce THAT insight."
Recipe-Style Tutorials
Data Dots become ingredients for tutorials. Each tutorial opens with a "recipe card":
You will be applying these 4 concepts to achieve goal X:
- [[Data Dot: Surrogate Keys]]
- [[Data Dot: Slowly Changing Dimensions]]
- [[Data Dot: Referential Integrity]]
- [[Data Dot: Incremental Models]]
The framework is consistent. The data for your situation will be different. Once it goes through, you'll be able to decide Y or Z.
The framework is fixed, the application varies — same as [[06-reference/2026-04-03-shape-up-introduction|Shape Up's]] appetite model applied to content.
Pipeline
- Write the concept (definition + why it matters + connected dots)
- Generate Memphis-style visual via Grok Imagine API (consistent art style)
- Publish to raydata.co as individual page (SEO)
- Share on LinkedIn/X as social content (distribution via [[06-reference/2026-04-03-casual-contact-viral-loops|casual contact loop]])
- Bundle into downloadable collection at 50+ dots (lead magnet / small paywall)
Monetization Path
Per [[06-reference/2026-04-03-ladders-of-wealth-creation|Ladders of Wealth Creation]]:
- Free: individual pages (SEO traffic, brand building)
- Small paywall ($9-29): full dictionary download + agent-ready format
- Premium: tutorials/courses that use dots as building blocks
- Sponsorships: once traffic justifies it, sponsor individual dot categories
Art Style
Memphis design consistent with Ray Data Co brand:
- Electric blue primary accent
- Bold geometric shapes (zigzags, circles, dots, grids)
- Hand-drawn-feel but digitally generated
- One visual per concept, instantly recognizable style
Structured Prompt Spec (JSON aesthetic template)
Inspired by Rahul Chakraborty's JSON style prompts — define the visual style as structured data for reproducibility:
{
"styleAesthetic": {
"title": "Memphis Data Concept Card",
"overallVibe": "Bold geometric, educational, builder aesthetic with Memphis design accents",
"renderingStyle": "Clean digital illustration with hand-drawn energy",
"colorPalette": {
"baseTones": ["Electric blue #3B82F6", "White #FFFFFF", "Near-black #1a1a2e"],
"accents": ["Coral #FF6B6B", "Yellow #FBBF24", "Pink #EC4899"],
"gradientStyle": "Minimal, flat fills with occasional subtle gradient"
},
"geometricElements": ["Zigzags", "Dots", "Triangles", "Circles", "Grid patterns"],
"linework": {
"thickness": "Medium to bold, confident strokes",
"style": "Hand-drawn feel but digitally clean",
"color": "Near-black or dark blue"
},
"objectSurfaces": {
"type": "Flat with minimal shading",
"textureDetail": "Grid/dot patterns as backgrounds, not textures on objects"
},
"moodKeywords": ["Educational", "Playful", "Technical", "Memphis", "Builder"]
}
}
Use this spec in every Grok Imagine API call for consistent Data Dots visual identity.
Starting Point
Pick 5 foundational concepts, prototype the full pipeline:
- Write concept → 2. Generate visual → 3. Publish page → 4. Share socially → 5. Evaluate engagement
Suggested first 5:
- Star Schema
- ETL vs ELT
- Slowly Changing Dimensions
- Data Contract
- Semantic Layer
Open Questions
- Naming: "Data Dots" or something else? "Signal Cards"? "Data Deck"?
- Should winning formations be a separate product or a sub-section?
- What structured format works best for agent consumption? Markdown with frontmatter? JSON-LD?
- How do we measure which dots drive the most traffic/engagement?