professional-work

10

Archon Admin

I built a personal magazine admin and API with custom dropdowns, tables and sortable lists. I revisit its shared UI alongside the questions left by complex screen logic and incomplete authorization.

preview
Archon Admin project preview / 프로젝트 미리보기

Building the management side of a magazine

Archon Admin is a personal admin app for a fictional architecture magazine. I wanted to practice React in a project with connected features, so I built both the management screens and an Express and MariaDB API. Archon v2 later used that same API for its public-facing screens.

Repeated inputs and list interactions led me to build custom dropdowns, tables and drag-and-drop lists. I alternated small implementation steps with manual checks. React Query handled server data, Zustand shared state, and React Hook Form and Zod supported forms. I used CKEditor5 for article editing and configured deployment with Oracle Cloud, Docker and Nginx.

What the custom UI still needed

Adding tools and screens did not make every interaction reliable. Responsive dropdowns and tables accumulated complex logic, image uploads and error handling remained unstable, and authorization was only partly implemented.

Reading this alongside the agricultural e-commerce project now, I see a question about treating shared UI and permission rules as separate concerns. This is a present-day comparison rather than a claim of direct code reuse.