How nayara/bookworm works
Project type and purpose
• This is a single-page React front-end application.
– Evidence: presence of “public/index.html”, React-style “src/components”, “src/containers”, “src/pages”, and “src/router.js”.
– No backend directory or API service code, so this is purely a client-side SPA, possibly served as static assets.
File structure
• Top-level files
– .gitignore, .travis.yml → source control and CI hints
– package.json → dependencies and scripts (build, test, start)
• public/
– index.html → host page
– manifest.json → PWA metadata
• src/
– components/ → reusable UI pieces (Header, Footer, App)
– containers/ → stateful or data-driven components (Links)
– pages/ → route targets (Homepage, AboutUs)
– router.js → defines client-side routes
– index.js + index.css → application entry point and global styles
• src/test/ → unit tests for components
• Absence of src/services or src/api suggests API calls are embedded in containers or omitted.
README
• Empty—no extra architectural notes. We infer standard React/CRA conventions.