Who this is for
For repeat readers, keyboard-first visitors, and anyone who remembers a topic but not the page title where it lived.
Projects / Experience layer
Reader Loop
Reader tools that feel supportive instead of managerial.
A lot of personal sites are pleasant until you actually try to use them. Reader Loop is the layer that turns a nice surface into something a returning visitor can navigate comfortably. The reader layer now offers fast search, light persistence, and small quality-of-life tools that reward curiosity while keeping the main pages calm.
What needed solving
A writing-heavy site gets harder to use as soon as it has enough posts to matter. Search, continuity, and little navigation assists had to exist without making the site feel like a SaaS dashboard.
What changed after shipping
The reader layer now offers fast search, light persistence, and small quality-of-life tools that reward curiosity while keeping the main pages calm.
What changed for visitors
The site became easier to re-enter. Search no longer feels bolted on, resume reading gives visitors a memory, and the archive can grow without becoming a scavenger hunt.
Why this layer matters
Reader experience is where a lot of otherwise thoughtful sites fall apart. Good writing loses force when the supporting system makes it hard to return, skim, or share.
How it stays disciplined
Every utility in this layer had to earn its weight. If a feature did not make a meaningful reading path faster or calmer, it did not ship.
The rules that kept this project honest.
- Use JavaScript only where the payoff is obvious to a reader.
- Design utility surfaces as companions, not control panels.
- Make discovery feel lightweight even as the archive grows.
Concrete wins from the current version.
- Lets visitors jump directly to posts, pages, and projects with a lightweight search flow.
- Keeps reading continuity on the visitor's device instead of pushing data into a backend account system.
- Adds practical utility without breaking the site's editorial mood.
Stack and routes
The technical spine behind the project.
ReactStatic JSON indexLocalStorageAstro islands
Written trail
Open the archive Posts that explain the reasoning around this project.
Astro islands are a product choice, not just a framework feature
Treating hydration as a design constraint leads to cleaner reading experiences and a healthier performance budget.
A lot of technical work is really translation
The hard part is often not only building the system. It is helping different people understand the same system from where they stand.
Teaching changed how I design technical things
Trying to help other people learn made me much less interested in showing off and much more interested in clarity.
More projects
See the full index The rest of the site system is connected work, not filler.
Visitor Globe
A 3D globe that turns recent visits into ambient presence instead of analytics theater.
Open case studyJason Eran Site System
The broader personal site system: static-first, searchable, and public-safe by design.
Open case studyEdge Visitor Pipeline
A light edge data path that keeps the globe current without building a long-term reader profile.
Open case study