How ramazantoichuev/palliativ works
Palliativ is a Django web application for a palliative-care service. The principal workflow is a visitor or staff member reaching a routed page, using a care or information feature, and reading or updating PostgreSQL-backed records. Its documented capabilities also include news, events, resources, FAQs, multilingual content, and configurable analytics. The tree and excerpts establish these product areas, but sampled source does not show URL dispatch or most view-to-model wiring; those links are therefore represented only at the app boundary where appropriate.
Main entry points: urls.py Django routing · posts.py News posts · views.py Consultations and pages · models.py Event records
Components 32
Web entry
- Django routing
config/urls.py - Account routes
accounts/urls.py - Main routes
main/urls.py - Patient routes
patients/urls.py - Event routes
events/urls.py - News routes
news/urls.py - Resource routes
resources/urls.py - FAQ routes
faq/urls.py
Care services
- Accounts
accounts/views.py - Patient care
patients/views.py - Events
events/views.py - Consultations and pages
main/views.py - User profiles
accounts/models.py - Patient records
patients/models/patients.py - Consultation data
main/models/consultation.py - Event records
events/models.py
Public content
- News
news/views/posts.py - News posts
news/models/posts.py - Resources
resources/views.py - Resource files
resources/models/resources.py - FAQ
faq/views.py - FAQ entries
faq/models.py
Shared platform
- PostgreSQL
- Language settings
config/settings.py - News translations
news/translation.py - Event translations
events/translation.py - Analytics context
main/context_processors.py - Image compression
news/tasks.py - File compression
resources/tasks.py
Other components
- Visitor
- Care staff
- Analytics providers
Connections 40
- Visitor → Django routing: requests pages
- Care staff → Django routing: requests pages
- Django routing → Account routes: routes to
- Django routing → Main routes: routes to
- Django routing → Patient routes: routes to
- Django routing → Event routes: routes to
- Django routing → News routes: routes to
- Django routing → Resource routes: routes to
- Django routing → FAQ routes: routes to
- Account routes → Accounts: dispatches
- Main routes → Consultations and pages: dispatches
- Patient routes → Patient care: dispatches
- Event routes → Events: dispatches
- News routes → News: dispatches
- Resource routes → Resources: dispatches
- FAQ routes → FAQ: dispatches
- Accounts → User profiles: uses records
- Patient care → Patient records: uses records
- Consultations and pages → Consultation data: uses records
- Events → Event records: uses records
- News → News posts: uses records
- Resources → Resource files: uses records
- FAQ → FAQ entries: uses records
- User profiles → PostgreSQL: stores data
- Patient records → PostgreSQL: stores data
- Consultation data → PostgreSQL: stores data
- Event records → PostgreSQL: stores data
- News posts → PostgreSQL: stores data
- Resource files → PostgreSQL: stores data
- FAQ entries → PostgreSQL: stores data
- Language settings → News translations: configures
- Language settings → Event translations: configures
- News translations → News posts: translates fields
- Event translations → Event records: translates fields
- Consultations and pages → Analytics context: template context
- Analytics context → Analytics providers: configures snippets
- Image compression → News posts: updates status
- Image compression → PostgreSQL: reads and writes
- File compression → Resource files: updates status
- File compression → PostgreSQL: reads and writes