If you've browsed AI concept learning sites over the past few years, the recipe is familiar: top nav bar + gradient hero + three tabs for "Core Capabilities / Use Cases / Learning Path," with cards under each tab. It's usable, but ten of these sites are indistinguishable from one.
easy-learn-ai recently did something drastic: rebuilt every sub-site from scratch. Not a reskin—a DNA change.
The Old Problem: Product Whitepaper Voice
The old ai-sites/* sub-sites shared common flaws:
- Multi-tab structure — read like product manuals, not learning material
- Gradients + emoji + framer-motion — decoration over information
- "Let's begin our journey into X" — every site opened the same way
- Templated sections — intro, core concepts, use cases, always in that order
- Data stuck in 2023-2024 — outdated model version numbers and benchmark scores
- Each section needs ≥ 2 interactive elements (hover doesn't count—that's basic courtesy)
- ≥ 3 sections per site at L3+ (drag-to-edit / real-time reflection)
- Adjacent sections can't share the same interaction type
- ≥ 5 distinct interaction forms per site
One-sentence summary: not teaching concepts, selling concepts.
The New Solution: Five Soul-Searching Questions
The first step wasn't writing code—it was answering five questions:
1. What is the most direct one-sentence definition of this concept? — Must be a complete declarative sentence as the hero's first line 2. How do you explain it in 30 seconds to someone who's never heard of it? — Two or three conversational sentences, no paragraph over two sentences 3. What's the most counterintuitive fact? — Not in the hero; it's the hook at the start of section two 4. If you could change only one thing, what must it be? — The core action, the site's visual anchor 5. What did the last site look like, and which two things must change? — The anti-template red line
For example, the Agent site's hero now reads:
> "What is an AI Agent?" > AI Agent = a program that perceives its environment, makes autonomous decisions, and calls tools to achieve goals.
No metaphors, no rhetorical questions, no "imagine this." First a completable equation, then the explanation.
New Disciplines: Plain Language + Interaction + Real Data
Plain-Language Discipline
Three self-checks: 1. Would you say this at a product launch? If yes → cut it 2. Does a big word explain a small thing? If yes → cut it 3. Does the conversational version differ much? If it differs a lot → use the conversational version
> "Empowering enterprise-level intelligent decision-making" → "so the company doesn't dig through docs every time" > "Exploring the core principles and application value of X" → "how X actually works"
Interaction Discipline
Data Discipline
All data must be real and verifiable for 2026. Model versions, benchmark scores, product release status → search before writing, and be able to cite a source for every data point.
What Was Rebuilt
This round of restructuring covered:
| Sub-site | Topic | New features | |---|---|---| | agent | AI Agent | Five building blocks, ReAct loop, evaluation | | llm | Large Language Models | In-context learning, emergent abilities, instruction-following animation | | rag | Retrieval-Augmented Generation | Building blocks, three-step flow, ecosystem | | distill | Knowledge Distillation | Dark knowledge, teacher perspective, distillation lineage | | moe | Mixture of Experts | Router, load balancing, cost gallery | | quantization | Quantization | Number-line journey, methods map, ecosystem fit | | function-calling | Function Calling | Schema editing, parallel calls, MCP comparison | | batch-size | Batch Size | Effective batch, one update, training vs inference | | bert | BERT | Bidirectional masking, multi-head attention, still alive in 2026 | | deepseek-r1 | DeepSeek-R1 | GRPO, distillation, Aha Moment | | deepspeed | DeepSpeed | ZeRO, Offload, 3D parallelism | | loss | Loss Functions | Curve doctor, regression, cross-entropy | | mcp | MCP Protocol | Pre-MCP era, basic primitives, triangle architecture | | nlp | NLP | Word embeddings, tokenizers, paradigm differences | | rlhf | RLHF | Reward hacking, KL tether, where do you rank |
Every site is a single-page vertical scroll—no tabs, no header/footer, no "module tour." One long page is everything.
The Harshest Rule
> If a site's structure is 70% similar to the previous site = red line. Restructure it.
Meaning: the BERT site and the loss site can't both be "intro → core → applications → summary." BERT might use a "timeline" narrative; loss might use "pain → solution → cost." Every concept must grow its own unique skeleton.
---
This brings to mind a design principle: good teaching isn't putting knowledge into a pretty container—it's making the container itself part of the knowledge. As you scroll a sub-site, the interaction rhythm, information density, and visual anchors you experience are themselves an answer to what the concept "looks like."
#easy-learn-ai #daily-updates #memory #xiaokai