Initial commit

2026-04-27 18:40:30 +08:00
commit 2120774b05
112 changed files with 12308 additions and 0 deletions
@@ -0,0 +1,52 @@
+# Directory Structure
+
+> JSP page and static asset organization for the presentation layer.
+
+---
+
+## Overview
+
+Future frontend code should be JSP/CSS rendered by the Servlet/Tomcat
+application. There is no application source tree yet; the paths below are
+illustrative conventions for the first implementation.
+
+---
+
+## Suggested Layout
+
+```text
+src/main/webapp/
+  WEB-INF/jsp/
+    common/             Shared JSP fragments such as header.jspf
+    auth/               Login and permission pages
+    books/              Book list, form, detail, category pages
+    readers/            Reader list, form, detail pages
+    borrowing/          Borrow, return, renew, overdue pages
+    statistics/         Search, ranking, inventory, overdue reports
+    maintenance/        System logs, backup, exception trace pages
+  static/
+    css/                Page and shared styles
+    js/                 Small page scripts when needed
+    images/             Designed/generated UI images and static assets
+```
+
+JSPs that should not be accessed directly belong under `WEB-INF/jsp/` and are
+rendered through Servlet forwards. Public static files belong under `static/`.
+
+---
+
+## Page Naming
+
+Use module-oriented JSP names such as `books/list.jsp`, `books/form.jsp`,
+`readers/detail.jsp`, `borrowing/overdue.jsp`, and
+`maintenance/system-logs.jsp`. Match Servlet dispatch paths once controllers
+exist.
+
+---
+
+## Static Assets
+
+Keep CSS in `static/css/`, small browser scripts in `static/js/`, and
+image-first design references or exported assets in `static/images/` once the
+application tree exists. Do not create React/Vue component directories or SPA
+asset conventions unless the stack changes.