<?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: Perry Lei</title>
    <description>The latest articles on DEV Community by Perry Lei (@perry_lei_47d4f08a1ad4780).</description>
    <link>https://dev.to/perry_lei_47d4f08a1ad4780</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%2F3970116%2F77244b1f-738e-4a9e-b420-ff2d0a423a00.jpg</url>
      <title>DEV Community: Perry Lei</title>
      <link>https://dev.to/perry_lei_47d4f08a1ad4780</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/perry_lei_47d4f08a1ad4780"/>
    <language>en</language>
    <item>
      <title>How I built a one-page interactive journal generator for my kid</title>
      <dc:creator>Perry Lei</dc:creator>
      <pubDate>Tue, 17 Nov 2026 10:23:28 +0000</pubDate>
      <link>https://dev.to/perry_lei_47d4f08a1ad4780/how-i-built-a-one-page-interactive-journal-generator-for-my-kid-1c7l</link>
      <guid>https://dev.to/perry_lei_47d4f08a1ad4780/how-i-built-a-one-page-interactive-journal-generator-for-my-kid-1c7l</guid>
      <description>&lt;h1&gt;
  
  
  How I built a one-page interactive journal generator for my kid
&lt;/h1&gt;

&lt;p&gt;I built &lt;a href="https://shiye.leiping.dev/" rel="noopener noreferrer"&gt;Shiye&lt;/a&gt; for my own kid, because the review material we had at home wasn't working. A whole workbook is too big to start, and a pile of printed worksheets never gets finished. I wanted something smaller: one page, for one unit, that a kid can actually finish in one sitting.&lt;/p&gt;

&lt;p&gt;That constraint — one page — ended up deciding almost everything else.&lt;/p&gt;

&lt;h2&gt;
  
  
  One page as a design constraint
&lt;/h2&gt;

&lt;p&gt;A page covers the units a parent picks, nothing more. The parent chooses the school stage, subject, textbook version and volume, pastes or photographs the table of contents, ticks the chapters for this round, and gets a single interactive page in about three minutes. No prompt writing.&lt;/p&gt;

&lt;p&gt;The kid opens a link and starts. No login, no ads, no external links, no pop-ups. Finished work syncs back to the parent, and the same page prints cleanly on A4 if we want it on paper.&lt;/p&gt;

&lt;p&gt;The reason for the limit is not minimalism for its own sake. A page has a visible end. My kid can see the finish line before starting, and finishing means finishing — not "do two more pages tomorrow." Underneath that is a simple bet from cognitive psychology: testing effect (actively recalling beats re-reading) and generation effect (organising material yourself beats copying it). So the page is built around recall — flip cards, ordering, short quizzes — and ends with a stamp when it's done.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a page is made of
&lt;/h2&gt;

&lt;p&gt;A generated page is a set of interactive blocks, not a wall of text. Eight block types in total; the ones my kid actually uses most:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Read:&lt;/strong&gt; a short passage where underlined words open a small note when tapped.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Flip:&lt;/strong&gt; sticky-note cards — recall the point first, tap to check the exam-ready version.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hotspot diagram:&lt;/strong&gt; tap the red dots on a diagram to explore each part and what it does. The live example has seven hotspots.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Quiz:&lt;/strong&gt; a few questions where every option comes with a diagnosis, not just right or wrong. One asks which structure you definitely cannot see in an onion epidermis slide — the answer is chloroplast, because onion inner epidermis grows underground, out of light — and the explanation says so.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ordering:&lt;/strong&gt; drag items into the right sequence instead of reading a list.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You can try the real thing without logging in: a Grade 7 biology journal on cells, &lt;a href="https://shiye.leiping.dev/samples" rel="noopener noreferrer"&gt;live sample&lt;/a&gt;. It takes about twenty minutes and it is the actual output of the generator, not a mockup.&lt;/p&gt;

&lt;h2&gt;
  
  
  AI generates, gates decide
&lt;/h2&gt;

&lt;p&gt;The content is AI-generated, which is exactly why the generator does not serve raw model output to a kid. Every page has to pass a gate pipeline in the repo — G1 through G17 — before it becomes a journal page. The gates are the line between generated and shippable.&lt;/p&gt;

&lt;p&gt;I am deliberately vague about the model itself, because it is the least interesting part. The interesting part is the pipeline around it: generation is cheap, verification is the product. A wrong fact in a workbook is annoying; a wrong fact in something a kid memorises is worse. The gates exist because I do not trust the first draft, including my own generator's.&lt;/p&gt;

&lt;p&gt;That is also why the site tells parents to review a page before sending it to their kid. The gates catch a lot. They do not catch everything.&lt;/p&gt;

&lt;h2&gt;
  
  
  Kid-facing pages have to be safe to open
&lt;/h2&gt;

&lt;p&gt;A generated page can contain diagrams, and diagrams in this project are SVG. SVG is powerful and, for that reason, a bad thing to paste unchecked into a page a child opens: it can carry scripts, event handlers, and external references.&lt;/p&gt;

&lt;p&gt;So generated SVG goes through an allow-list sanitizer before it is rendered. Only allow-listed tags and attributes survive; everything else is stripped. No scripts, no event handlers, no external loads.&lt;/p&gt;

&lt;p&gt;The same thinking applies to the rest of the kid-facing page: it is a self-contained single page with no account information and no third-party tracking. If a page needs something from outside to work, that is a bug, not a feature.&lt;/p&gt;

&lt;h2&gt;
  
  
  The directory is private by design
&lt;/h2&gt;

&lt;p&gt;The table of contents a parent pastes in is their kid's curriculum, and it is stored encrypted per account, so it can be reused next time without retyping a whole volume. The repo uses envelope encryption for this: a data key encrypts the contents, and that key is itself stored wrapped.&lt;/p&gt;

&lt;p&gt;The practical effect a parent sees is simpler: enter a volume once, reuse it, and the kid's page never contains the directory or any account data.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is still rough
&lt;/h2&gt;

&lt;p&gt;Two honest limits. First, AI content is sometimes wrong, and a gate pipeline is not a guarantee — review before you hand it over, especially the quiz explanations. Second, the product is built around Chinese K–12 textbooks, in Chinese. That is the system my kid is in, and it is also the product's biggest limit right now.&lt;/p&gt;

&lt;p&gt;I am not trying to replace a teacher or a textbook. The question I am testing is narrower: can one finished page beat ten unfinished ones? So far, at home, the answer has been yes often enough to keep building.&lt;/p&gt;

&lt;p&gt;If you have tried something similar with your own kids — or if you spot a wrong fact in the sample — I would like to hear about it.&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>webdev</category>
      <category>ai</category>
      <category>javascript</category>
    </item>
    <item>
      <title>WordHub vs Google Dictionary Extension: quick lookup versus actual vocabulary growth</title>
      <dc:creator>Perry Lei</dc:creator>
      <pubDate>Fri, 05 Jun 2026 15:47:46 +0000</pubDate>
      <link>https://dev.to/perry_lei_47d4f08a1ad4780/wordhub-vs-google-dictionary-extension-quick-lookup-versus-actual-vocabulary-growth-3543</link>
      <guid>https://dev.to/perry_lei_47d4f08a1ad4780/wordhub-vs-google-dictionary-extension-quick-lookup-versus-actual-vocabulary-growth-3543</guid>
      <description>&lt;p&gt;I used Google Dictionary for a long time.&lt;/p&gt;

&lt;p&gt;It does one thing well: when I hit a word I do not know, it gives me a definition fast enough that I can keep reading. That matters more than people admit. A dictionary that gets in the way is not useful.&lt;/p&gt;

&lt;p&gt;But after reading enough English articles, papers, and docs, I started noticing a gap.&lt;/p&gt;

&lt;p&gt;I was looking up words correctly. I was not necessarily learning them.&lt;/p&gt;

&lt;p&gt;That is the difference between a quick lookup tool and a vocabulary workflow.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who this comparison is for
&lt;/h2&gt;

&lt;p&gt;This is for people who read English online every day, want a one-click definition, but also want the word to stick; save too many words and forget to review them; care about etymology, word families, and semantic relationships; and want a browser workflow instead of another tab-hopping habit.&lt;/p&gt;

&lt;p&gt;If you only need a definition once in a while, Google Dictionary is enough.&lt;br&gt;
If you want vocabulary to compound over time, WordHub is the more complete workflow.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Google Dictionary does well
&lt;/h2&gt;

&lt;p&gt;Google Dictionary is valuable because it stays out of the way.&lt;/p&gt;

&lt;p&gt;The extension gives you a straightforward definition popup, supports multiple dictionaries and languages, and can store lookup history if you opt in. That is a clean baseline. It is also a useful reminder that most learners do not need a complicated interface to understand a word in the moment.&lt;/p&gt;

&lt;p&gt;That is the core strength: speed.&lt;/p&gt;

&lt;p&gt;For a lot of reading sessions, that is all you need.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where Google Dictionary stops
&lt;/h2&gt;

&lt;p&gt;The problem is not the definition.&lt;/p&gt;

&lt;p&gt;The problem is everything that happens after the definition.&lt;/p&gt;

&lt;p&gt;If you are reading a serious article or a paper, a single gloss is often not enough. Words are easier to remember when you see how they relate to other words, where they came from, how they behave in context, and when you should review them again.&lt;/p&gt;

&lt;p&gt;Google Dictionary does not try to solve that broader problem. It is a fast lookup layer. WordHub is trying to be the next layer.&lt;/p&gt;

&lt;h2&gt;
  
  
  What WordHub adds
&lt;/h2&gt;

&lt;p&gt;WordHub combines four things that usually live in separate places:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Dictionary lookup with IPA, affixes, and multiple sources&lt;/li&gt;
&lt;li&gt;WordNet graphs that show synonyms, antonyms, hypernyms, hyponyms, and related words&lt;/li&gt;
&lt;li&gt;Etymology maps that show where a word came from and how it moved across languages&lt;/li&gt;
&lt;li&gt;Save-to-review and SM-2 spaced repetition so the word does not disappear after one lookup&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The browser extension adds another layer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;highlight, double-click, or press &lt;code&gt;Alt+X&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;get a definition in place&lt;/li&gt;
&lt;li&gt;see an AI explanation for the sentence you are reading&lt;/li&gt;
&lt;li&gt;save the word without leaving the page&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That is the part Google Dictionary does not attempt: turning lookup into retention.&lt;/p&gt;

&lt;h2&gt;
  
  
  A real example: &lt;code&gt;construct&lt;/code&gt;
&lt;/h2&gt;

&lt;p&gt;Take the word &lt;code&gt;construct&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Google Dictionary can tell you what it means.&lt;/p&gt;

&lt;p&gt;WordHub can do more:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;show related words like &lt;code&gt;structure&lt;/code&gt;, &lt;code&gt;destruction&lt;/code&gt;, and &lt;code&gt;infrastructure&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;show the semantic relationships around the word&lt;/li&gt;
&lt;li&gt;show the root story behind the word parts&lt;/li&gt;
&lt;li&gt;save the word together with the sentence you found it in&lt;/li&gt;
&lt;li&gt;put it into spaced review later&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That matters because vocabulary is rarely learned as isolated singletons.&lt;/p&gt;

&lt;p&gt;The brain tends to remember clusters better than loose entries. If you see a word as part of a family, it is easier to rebuild the meaning when you meet it again.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where WordHub fits in the reading workflow
&lt;/h2&gt;

&lt;p&gt;Here is the workflow I actually wanted:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;I am reading a page.&lt;/li&gt;
&lt;li&gt;I hit a word I do not know.&lt;/li&gt;
&lt;li&gt;I get a definition immediately.&lt;/li&gt;
&lt;li&gt;I see how the word works in this sentence.&lt;/li&gt;
&lt;li&gt;I decide whether this word is worth keeping.&lt;/li&gt;
&lt;li&gt;If yes, I save it.&lt;/li&gt;
&lt;li&gt;Later, the word comes back through review.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;That is the whole point.&lt;/p&gt;

&lt;p&gt;If step 5 never exists, the list grows and the learning does not.&lt;/p&gt;

&lt;p&gt;WordHub is built around that gap. Google Dictionary is not trying to solve that problem, and that is fine. It just means the tools serve different jobs.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I would use each tool for
&lt;/h2&gt;

&lt;p&gt;Use Google Dictionary if you want a fast popup definition, do not care about review, want something minimal, and mostly need a quick reading aid.&lt;/p&gt;

&lt;p&gt;Use WordHub if you want to actually build vocabulary, read English regularly, want etymology and semantic relationships, want review without moving words into another app, and want the browser to become the study surface.&lt;/p&gt;

&lt;h2&gt;
  
  
  Limitations, because they matter
&lt;/h2&gt;

&lt;p&gt;WordHub is not magic.&lt;/p&gt;

&lt;p&gt;Current limits:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Chrome is the most stable target right now&lt;/li&gt;
&lt;li&gt;dictionary data is English-first&lt;/li&gt;
&lt;li&gt;if you only need translation, a dedicated translation tool may still be better&lt;/li&gt;
&lt;li&gt;if you already live in Anki and like your workflow, WordHub is complementary rather than a replacement&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I prefer being explicit about that. It makes the comparison more useful.&lt;/p&gt;

&lt;h2&gt;
  
  
  Bottom line
&lt;/h2&gt;

&lt;p&gt;Google Dictionary is a good quick lookup tool.&lt;/p&gt;

&lt;p&gt;WordHub is for the moment after the lookup: understanding, saving, and remembering.&lt;/p&gt;

&lt;p&gt;If your workflow is just "what does this word mean right now?" Google Dictionary is enough.&lt;br&gt;
If your workflow is "I want this word to stay with me after I close the tab," WordHub is the better fit.&lt;/p&gt;

&lt;p&gt;WordHub is free and does not require an account to start.&lt;/p&gt;

&lt;p&gt;If you want to try it, use the browser extension on a real article, not a demo page. The value shows up when you read something you actually care about.&lt;/p&gt;

</description>
      <category>productivity</category>
    </item>
  </channel>
</rss>
