How alexanderthebored/backend-test works
Project type and purpose
• Type: Static, front-end–only web application with local CLI tools for asset ingestion
• Purpose: Display a grid of manga titles and serve a chapter-by-chapter reader in the browser, backed by local JSON metadata and image assets
Main components
a. Client (Browser)
• index.html (landing page)
• mangareader.html (reader UI)
• Components: book-card.js/css, logo.css
• styles/main.css
b. Static Files
• data/manga.json (metadata store)
• assets/covers (cover images)
• assets/manga (chapter images)
c. CLI Tools (Node scripts in tools/)
• batch-download-manga.js
• download-chapter.js
• generate-manga-json.js
• mangadex-link.js
d. External Service
• MangaDex API (source for images and metadata)
Relationships & data flows
• Browser loads index.html → fetches manga.json → renders book-card components → pulls cover images
• User clicks a card → mangareader.html → loads chapter images from assets
• CLI tools invoke the MangaDex API to populate assets/ and update data/manga.json