How pabloc2a/cajalink works
Project type and purpose
• This is a Django‐based, full-stack web application (monolithic MVT pattern).
• It provides credit simulation features for end users, plus separate staff and user panels.
File structure
• Top-level “config” directory holds project settings, URL routing (ASGI/WSGI), and environment configs.
• Several Django apps each encapsulate a domain:
– core: shared functionality (middleware, context processors, common models/views)
– users: authentication, user services, email notifications
– credit_simulator: credit-simulation forms, services, views, templates
– staffpanel: staff-only CRUD and reporting interfaces
– userpanel: authenticated user dashboards and history pages
– legacy_models: wrappers over existing database tables/migrations
• Templates directory organizes HTML by app, plus global layouts and email templates.
• Manage.py and requirements.txt signal standard Django project management.
README (assumed typical Django setup)
• Likely describes Django version, Python requirements, database settings, and app overviews.
• Would reference external services (SMTP for emails) or caching if used.