How muralidharan-k/travellerpage works
Travello is a Django travel-destination catalogue: a visitor reaches the destination view, which queries destination records and renders a page. The app also exposes destination management through Django admin. The repository includes page-specific browser scripts and visual-interaction libraries, but the templates and URL wiring were not excerpted, so their connections to the backend are not inferred. Database settings name a local MySQL database; ORM persistence is shown only as an unverified relationship.
Main entry points: views.py Catalogue view · models.py Destination model · custom.js Home interactions · urls.py Destination route
Components 15
Django catalogue
- Destination route
travello/urls.py - Catalogue view
travello/views.py - Destination model
travello/models.py - Admin registration
travello/admin.py
Browser experience
- Catalogue template
template/index.html - Home interactions
static/js/custom.js - Destination interactions
static/js/destinations.js - About interactions
static/js/about.js - Contact interactions
static/js/contact.js - News interactions
static/js/news.js - Page elements
static/js/elements.js
UI libraries
- Carousel engine
static/plugins/OwlCarousel2-2.2.1/owl.carousel.js - Grid filtering
static/plugins/Isotope
Other components
- Visitor
- MySQL database
Connections 8
- Visitor → Destination route: requests
- Destination route → Catalogue view: routes to
travello/urls.py - Catalogue view → Destination model: queries
travello/views.py - Catalogue view → Catalogue template: renders
travello/views.py - Admin registration → Destination model: registers
travello/admin.py - Destination model → MySQL database: persists via ORM
- Home interactions → Carousel engine: initializes
static/js/custom.js - Home interactions → Grid filtering: initializes
static/js/custom.js