How sudoneoox/picton works
Based on our analysis of the file tree and README, this project is a full‐stack user management system with role‐based access control (RBAC). The backend is implemented in Django while the frontend is built with React (using Vite), and PostgreSQL is used for the primary database. Authentication is done via Office365, so that external integration should also be represented in the system design.
Main Components
• Frontend: Represent the React application (front-end) that handles routing and user interface. Indicate its directories (e.g., src, public, components, and styles).
• Backend: Illustrate the Django-based backend, which is divided into “api” and “config” components. Highlight important parts such as:
• API endpoints (URLs, views, serializers) for authentication, user management, forms, and admin functionalities.
• Management commands and migrations as part of operational or deployment tasks.
• Core functionality such as exception handling, permissions, and utility functions.
• External Authentication Service: Include Microsoft Office365 (Azure/Microsoft Graph) as an external authentication service. This should be connected to both the frontend and backend to indicate the integration.
Relationships and Interactions
• How the Frontend communicates with the Backend’s API endpoints (for user login, submission of forms, fetching dashboard data, etc.).
• How the Backend makes calls to the PostgreSQL database (for persistent user and form data).
• The callout from the Backend to Microsoft’s authentication service during the authentication flow.
• Separation of concerns:
• The frontend is responsible for presentation and client-side logic.
• The backend handles business logic, authentication, database interactions, and processing of forms.
• External services (Office365) are used for authentication and possibly user management.
Architectural Patterns and Design Principles
• Separation of Frontend and Backend layers (MVC-like pattern in Django, with clear distinctions between API, management, and configuration).
• Use of microservices or containerization patterns:
• Extensibility is suggested by the modular structure in both the backend (e.g., “api/core”, “api/views/forms”) and frontend (separated pages and components).
• Python and Django for the backend
• React (with Vite) for the frontend
• PostgreSQL for the database
• Microsoft Office365 integration for authentication (via Microsoft Graph)
• Docker (with provided Dockerfiles, docker-compose) for container orchestration