How aditipatil38/shelforbit works
Project Type and Purpose
• This is a full-stack, interactive web application (“The ShelfOrbit”) for discovering, searching, and discussing books.
• It comprises three logically separated sub-systems:
a. A React.js single-page front end (book lists, details, and real-time chat)
b. A Django + Django REST Framework back end (serving book and library data via REST APIs, admin panel)
c. A Streamlit-based analytics module (in the analytics/ folder) for offline recommendation workflows
File Structure Analysis
• Top-level directories:
• frontend/ – React app with components Chat.js, SignIn.js, Room.js, etc.
• backend/ – Django project (booksproject) containing:
– firstbook/ app (models, serializers, views, templates for book & library)
– db.sqlite3 (primary relational store)
• analytics/ – Streamlit app (app.py) plus a local SQLite database (25k.db) and recommendation scripts.
• Key patterns:
• MVC on Django (models → serializers → views → templates)
• Component-based front end communicating via REST calls and Firebase real-time messaging
• Separate service for analytics recommendations
README Insights
• Tech stack: Python, Django, Django REST Framework, SQLite, Firebase (chat), React.js, Streamlit
• Features: personalized recommendations (genre/tag, author), search & similar books, real-time chat rooms, admin CMS