Add implementation plan and mobile requirements to design.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-14 12:24:09 +08:00
parent 198a321c51
commit a5bc95ce8c
2 changed files with 527 additions and 1 deletions
@@ -184,6 +184,13 @@ Errors: `413` too large, `429` rate limited, `403` banned IP (writes), `404` mis
 - Anonymous-first: landing page is immediately editable  
 - Clear toasts for size/rate/ban failures  
 - Friendly 404 for expired/burned content  
+- **Mobile-first responsive:** usable on phones (portrait); touch-friendly controls; composer / wall stack vertically on small screens; file pick works via mobile OS picker; no hover-only actions; Element Plus grid/breakpoints (`xs`/`sm`) for layout  
+
+### Mobile acceptance
+
+- Home / Detail / Admin usable at ~375px width without horizontal scroll of the main layout  
+- Create text, upload file, copy share link, open wall item on a phone browser  
+- Admin login and delete/ban actions work on touch devices  

 ## 7. Security & limits

@@ -230,7 +237,8 @@ Multi-stage Dockerfile: build frontend → copy `dist` into backend image → ru
 4. Markdown renders; images preview; other allowed types download.  
 5. Admin can log in with env password, delete items, ban/unban IPs.  
 6. Uploads over 200 MB rejected; more than 2 create/upload requests per second per IP get 429.  
-7. `docker compose up -d` brings up a working instance on port 8080.
+7. `docker compose up -d` brings up a working instance on port 8080.  
+8. Phone browsers (~375px) can create, upload, view, copy links, and use admin actions without broken layout.

 ## 11. Implementation order (for planning)