How drodriguez5503/conecta-daw-tfg works
Project Type and Purpose
• This is a full-stack web application for managing personal Markdown notes, inspired by Obsidian. The aim is to build a “second digital mind” where ideas are interlinked.
• The backend is a Django-powered API service, while the frontend is an Angular application.
Main Components
a. Frontend (Angular Application):
• Located under the “frontend” directory in the file tree.
• Contains a full Angular project with its own configuration files (angular.json, package.json) and numerous components (e.g., header, footer, home, sign-in, sign-up, backoffice with sub-components for connections, folder, note, settings, sidebar, user, etc.).
• This part is responsible for the user interface and interactions, sending requests to the backend and rendering data accordingly.
b. Backend (Django API):
• Found in the “backend” directory. The Django project is named “api_Conecta” and contains multiple Django apps such as api_notes, api_projects, api_themes, and api_users.
• Each app handles a specific domain of functionality (e.g., handling notes, projects, thematic connections, and user management).
• The backend includes standard Django components – settings, URL configuration, WSGI/ASGI entry points, and a manage.py script.
c. Database and Persistence Layer:
• Although not explicitly depicted in the file tree, a relational database (like PostgreSQL or MySQL) is implied as the data store for the Django models.
• This database holds persistent data for notes, projects, themes, and user information.
Relationships and Interactions
• The Django backend, in turn, interacts with the database to perform CRUD operations for the various apps (notes, projects, themes, users).
• Other integrations, such as authentication or external services (if any), can be added as separate nodes if they exist or are planned.
Architectural Patterns and Technologies
• The backend follows a modular Django structure, grouping functionality into separate apps (API endpoints for notes, projects, etc.), which can be visualized using containers or microservices patterns (if extended).
• The frontend uses Angular’s component-based architecture – different modules manage different parts of the UI and routing.
• The clear separation between the frontend and backend aligns with the modern web application pattern: a decoupled client-server architecture.