PROJECTS
Projects
A place for work I am willing to explain properly: why it began, how I shaped it, where it stands now, and what still needs care.
I want project pages to keep more than a list of things I built. Each one tries to leave some trace of the thinking too: why it began, what tradeoffs I made, what has already landed, and what I still want to improve.
Why it exists
Start with the problem, the motivation, and what the project is trying to solve.
What I did
Show the work I actually completed instead of only listing technology names.
What comes next
Keep the rough edges visible so the next step stays clear.
Status: site, Biying APIs, public knowledge, and mobile smoke tests are wired together
Personal Digital Garden + Biying
A bilingual personal website that brings public notes, project records, guestbook messages, public knowledge, and Biying into one long-term entrance.
Core
Bilingual content, public retrieval, guestbook flow, and Biying's answer boundary.
My part
Information architecture, frontend interaction, EdgeOne APIs, RAG retrieval, build checks, and deployment flow.
Next
Add more real project reflections, then handle npm dependency audit and production environment setup separately.
Future project pages will keep the same shape when possible: background, stack, what I did, results, limitations, and next steps. That makes them easier for me to revisit, and easier for visitors to understand quickly.