How dylandominguez/mesa-de-partes works
This repository implements an early-stage Mesa de Partes web app whose evidenced workflow is account registration, email confirmation, and account activation. Registration validates fields in the browser, submits to a PHP controller, checks for duplicate email, stores a user, and sends a confirmation link; visiting that link requests activation. A login screen exists, but its authentication behavior is not shown. The README is only a title, and the home view is empty, so document-handling capabilities or their wiring cannot be established from the sampled source.
Main entry points: Usuario.php User model · usuario.php User operations · Email.php Confirmation email · index.php Registration screen
Components 14
Web screens
- Login screen
index.php - Registration screen
view/registro/index.php - Registration validation
view/registro/registro.js - Confirmation screen
view/confirmar_correo/index.php - Confirmation request
view/confirmar_correo/confirmar.js - Home view
view/home/index.php
Account workflow
- User operations
controller/usuario.php - User model
model/Usuario.php
Persistence and email
- Database connection
config/conexion.php - User records
- Confirmation email
model/Email.php - Registration email template
assets/email/registrar.html
Other components
- Visitor
- Gmail SMTP
Connections 19
- Visitor → Login screen: opens
- Visitor → Registration screen: opens
- Registration screen → Registration validation: loads
- Registration validation → User operations: submits registration
- User operations → User model: checks email
- User operations → User model: creates user
- User model → Database connection: opens connection
- User model → User records: reads and writes
- User operations → Confirmation email: requests confirmation
- Confirmation email → User model: fetches user
- Confirmation email → Registration email template: reads template
- Confirmation email → Gmail SMTP: sends message
- Gmail SMTP → Visitor: delivers link
- Visitor → Confirmation screen: opens link
- Confirmation screen → Confirmation request: loads
- Confirmation request → User operations: requests activation
- User operations → User model: activates user
- User model → User records: updates status
- Visitor → Home view: opens