How alexanderthebored/mangaview works
Project type and purpose
• MangaView (“Alexandria”) is a lightweight full-stack web application for browsing, reading, and managing manga.
• Frontend: vanilla HTML/CSS/JavaScript (multiple pages + JS modules).
• Backend: Node.js + Express (currently in progress) providing static‐file serving and REST style endpoints for authentication, sessions, and future manga APIs.
File structure
• Top-level static assets:
• CSS/ – layout & component styles (carousel.css, header.css, etc.)
• JS/ – modular scripts (auth.js, carousel.js, reader.js, session.js)
• HTML pages: index.html, home.html, browse.html, latest.html, reader.html, login.html, signup.html, admin.html, header.html
• Server:
• server.js – Express entry point
• package.json + package-lock.json – dependencies (express, express-session, bcrypt planned)
• structure.txt – potential notes on organization
• README.md – high-level overview & roadmap
Key insights from README
• Static/dynamic separation: vanilla frontend + Express backend
• Planned REST APIs under /api/manga/:id/chapter/:num for chapter data
• Authentication (bcrypt password hashing) & session management (express-session)
• Data storage: currently flat JSON, migrating to SQLite or MongoDB