01 — WhyWhy this site exists
I wanted a place I could keep learning and recording for the long haul: write down the real pitfalls of AI engineering and software building, and keep the reading notes and diary thoughts that are not yet full articles. The public site is for reading and tools; publishing, permissions, and data live in admin and the API — clear boundaries, fewer self-inflicted messes.
In short: put what can be explained in public here; keep what is still fermenting in the knowledge base and diary.
A personal site, split along maintainable product boundaries.
02 — MapWhat is on the site
The reader path is simple. You do not need to understand the monorepo to use the site:
- ArticlesSearchable, archivable essays and tutorials
- KnowledgeReading notes, book lists, daily essays, crystals
- AI DailyID photo, OCR, transcription, and other browser tools
public-webReading · knowledge · daily toolsadmin-webDraft · review · analyticsapiPersistence · auth · search03 — StackCore stack
The public site and admin app are Next.js / React; persistence and publishing go through a Spring API. Content only appears on the public side after review — by design, not laziness.
- Next.jsv16 · App Router
- Reactv19 · RSC
- TypeScriptstrict paths
- Spring Bootv3.4 · API
- MySQLFlyway migrations
- Markdownnotes & essays
04 — FlowHow writing gets published
Articles and knowledge entries are drafted and reviewed in admin, then published through the API. Diary leans toward write-and-ship; crystals are the sentences worth keeping from those essays. Readers see a stable version; I keep a path from draft to distillation.
05 — NextWhat comes next
Empty states and navigation will keep improving, the knowledge base will get more readable, and AI Daily tools will get sturdier. If you are building a personal site too, I hope this note helps you avoid glueing every boundary into one blob.