How johngunji/software-component-catalogue works
ComponentHub is a web catalogue for reusable code and design components. Users sign in, then browse category trees, search and view components, and record reuse; cataloguers additionally manage catalogue content and inspect statistics and purge candidates. The browser UI uses a REST client to call the Express API, which owns authentication, validation, catalogue operations, search tracking, and statistics over SQLite. The graph covers documented API capabilities; some frontend page details are inferred from the README because their source was not sampled.
Main entry points: server.js API routes and middleware · db.js Schema and credentials · catalogue.js API client and session · login.js Sign-in page
Components 15
Browser application
- Sign-in page
frontend/js/login.js - Catalogue pages
frontend/js/app.js - API client and session
frontend/js/catalogue.js
REST API
- API routes and middleware
backend/src/server.js - Authentication
backend/src/server.js
Catalogue domain
- Category management
backend/src/server.js - Component management
backend/src/server.js - Search and query tracking
backend/src/server.js - Reuse tracking
backend/src/server.js - Statistics and candidates
backend/src/server.js
Persistence and seed
- Initial catalogue data
backend/src/catalogue-seed.js - Schema and credentials
backend/src/db.js - SQLite catalogue store
Other components
- User
- ComponentHub API
Connections 21
- User → Sign-in page: signs in
README.md - Sign-in page → API client and session: submits credentials
frontend/js/login.js - API client and session → ComponentHub API: sends REST requests
frontend/js/catalogue.js - ComponentHub API → API routes and middleware: routes requests
README.md - Catalogue pages → API client and session: uses catalogue client
README.md - User → Catalogue pages: browses and manages
README.md - API routes and middleware → Authentication: routes login and protects API
backend/src/server.js - API routes and middleware → Category management: handles category requests
backend/src/server.js - API routes and middleware → Component management: handles component requests
backend/src/server.js - API routes and middleware → Search and query tracking: handles search requests
backend/src/server.js - API routes and middleware → Reuse tracking: handles use requests
backend/src/server.js - API routes and middleware → Statistics and candidates: handles statistics requests
backend/src/server.js - API routes and middleware → Schema and credentials: uses database module
backend/src/server.js - Schema and credentials → SQLite catalogue store: reads and writes
backend/src/db.js - Schema and credentials → Initial catalogue data: seeds catalogue
backend/src/db.js - Category management → SQLite catalogue store: reads and writes
backend/src/server.js - Component management → SQLite catalogue store: reads and writes
backend/src/server.js - Search and query tracking → SQLite catalogue store: queries and logs searches
backend/src/server.js - Reuse tracking → SQLite catalogue store: updates usage counts
backend/src/server.js - Statistics and candidates → SQLite catalogue store: aggregates catalogue data
backend/src/server.js - Authentication → Schema and credentials: verifies account
README.md