How momen9sarsour/professional-portfolio-resume-platform works
1. Overall architecture
- This is a monolithic Laravel 10 application with a server-rendered UI. The main user-facing surfaces are:
- a public CV viewer/exporter
- an authenticated dashboard
- an admin-only management area
- Most behavior is implemented in Laravel controllers, Eloquent models, Blade templates, and database migrations.
2. Request entry points and route boundaries
- The app is split across routes/web.php, routes/auth.php, and a stray routes/web copy.php that looks like a duplicate or backup.
- Public routes expose CV pages like /cv/{username} and PDF download flows.
- Auth routes handle login, registration, password reset, and email verification.
- Dashboard routes group the CRUD modules for profile, projects, skills, experiences, education, social links, templates, messages, clients, and settings.
3. Presentation layer
- The UI is built with Blade views under resources/views.
- There are clear view boundaries:
- resources/views/layouts/* for application shells
- resources/views/components/* for reusable UI primitives
- resources/views/dashboard/* for authenticated/admin screens
- resources/views/auth/* for Breeze auth flows
- resources/views/cv/* and resources/views/dashboard/resume/templates/* for CV rendering
- The app uses a frontend asset pipeline (resources/js, resources/css, vite.config.js) for interactive behavior and styling.
4. Domain model
- The data model is centered on a User with profile and portfolio content attached.
- Core models include Profile, Project, Skill, Experience, Education, SocialLink, Conversation, Message, CvTemplate, and Setting.
- This shape strongly suggests a user-owned portfolio system where most content is scoped per user, while some data such as templates and settings are global or admin-managed.
5. CRUD module structure
- Most dashboard features are organized as one controller per entity under app/Http/Controllers/Dashboard.
- Each module has a matching Blade section under resources/views/dashboard/<module>/.
- Common patterns across modules:
- list/index pages
- create/edit/show flows
- status toggles for active/inactive records
- sort-order handling for content that appears in CVs or dashboards
- This makes the application diagram read as multiple CRUD subsystems hanging off a shared authenticated dashboard.
6. Admin vs. regular user boundary
- app/Http/Middleware/AdminMiddleware.php is the key authorization boundary.
- Dashboard/ClientController and Dashboard/SettingsController indicate admin-only control over users and global configuration.
- Regular users can manage their own portfolio data and CV presentation, while admins can view/manage all users and platform-level settings.
7. CV template and resume subsystem
- CV generation is a distinct subsystem rather than just another dashboard page.
- CvTemplate plus template-specific Blade views under dashboard/cv-templates and dashboard/resume/templates show that the app supports multiple CV layouts.
- The README indicates PDF export via DomPDF, so the CV flow is: user data + selected template → rendered Blade CV → browser preview or PDF download.
- CVController and Dashboard/ResumeController are the main controllers for this output pipeline.
8. Messaging subsystem
- Messaging is modeled explicitly with Conversation and Message.
- The dashboard has a dedicated messaging controller and view, and the README describes AJAX-driven operations for:
- loading conversations
- fetching messages
- sending messages
- unread counts
- deleting conversations
- Architecturally, this is the app’s most interactive subsystem, but it still remains server-backed rather than websocket-centric.
9. Settings and customization
- Setting and Dashboard/SettingsController provide a global configuration layer.
- The README points to support for site metadata, email/SMTP settings, theme colors, custom CSS/JS, and maintenance mode.
- This is effectively the platform’s control plane: it influences branding, email delivery, and runtime presentation.
10. Authentication and user lifecycle
- Authentication is based on Laravel Breeze, visible in the app/Http/Controllers/Auth folder and the corresponding resources/views/auth/* screens.
- app/Http/Requests/Auth/LoginRequest.php and ProfileUpdateRequest.php show Laravel form-request validation for critical user actions.
- The app supports email verification, password reset, and profile management, all within the standard Breeze lifecycle.
11. Persistence and bootstrapping
- Database structure is defined through migrations in database/migrations, with seeders for default admin/user and initial portfolio content.
- database/factories/UserFactory.php supports test and seed data generation.
- The app relies on MySQL per the README, and the storage tree indicates file-backed uploads and generated artifacts live in Laravel storage.
12. External/runtime dependencies that matter
- The README names the main supporting tools that affect architecture:
- DomPDF for CV/PDF generation
- Chart.js for analytics visualization
- Bootstrap for UI styling
- jQuery for dashboard interactivity
- CodeMirror for code-editing/custom CSS or JS experiences
- These are not separate services, but they shape the rendering and interaction model.
13. Operational shape
- The app is intended to run as a conventional Laravel deployment: PHP app server, MySQL database, filesystem-backed storage, and compiled frontend assets.
- public/index.php is the web entry point, while artisan and phpunit.xml show standard Laravel CLI and test automation support.
- Tests are split into feature tests for auth/profile flows and unit smoke tests, suggesting the most important behavior is at the HTTP/controller boundary.
Main entry points: web.php web routes · CVController.php cv viewer · SettingsController.php settings · User.php user
Components 22
Routing
HTTP entry points and route boundaries
- web routes · Public and dashboard HTTP routes
routes/web.php - auth routes · Laravel Breeze authentication routes
routes/auth.php - web backup · Stray copy of web routes
routes/web copy.php
Presentation
Blade views and layout shells
- dashboard shell · Authenticated application shell
resources/views/layouts/dashboard.blade.php - cv view · Public CV render and preview
resources/views/cv/index.blade.php - resume view · Dashboard resume rendering surface
resources/views/dashboard/resume/index.blade.php - messages view · Dashboard messaging interface
resources/views/dashboard/messages/index.blade.php - settings view · Global settings management screen
resources/views/dashboard/settings/index.blade.php
Application
Controllers and middleware that coordinate behavior
- home · Landing and public navigation
app/Http/Controllers/HomeController.php - cv viewer · Public CV preview and export flow
app/Http/Controllers/CVController.php - dashboard · Authenticated dashboard entry and overview
app/Http/Controllers/Dashboard/DashboardController.php - resume export · Resume and template rendering pipeline
app/Http/Controllers/Dashboard/ResumeController.php - messages · Conversation and message management
app/Http/Controllers/Dashboard/MessageController.php - settings · Global platform configuration
app/Http/Controllers/Dashboard/SettingsController.php - admin guard · Authorization boundary for admin-only actions
app/Http/Middleware/AdminMiddleware.php
Domain
Core persisted models and state
- user · Authenticated account and owner of portfolio data
app/Models/User.php - profile · User profile and CV identity data
app/Models/Profile.php - projects · Portfolio project records
app/Models/Project.php - templates · Selectable CV layout definitions
app/Models/CvTemplate.php - conversation · Messaging thread container
app/Models/Conversation.php - message · Conversation message records
app/Models/Message.php - settings · Global site and runtime configuration
app/Models/Setting.php
Connections 28
- web routes → home: public pages · Dispatches landing and public surfaces
- web routes → cv viewer: cv routes · Public CV viewer and export endpoints
- web routes → dashboard: dashboard routes · Authenticated dashboard entry
- web routes → resume export: resume routes · Resume preview and export actions
- web routes → messages: message routes · Dashboard messaging endpoints
- web routes → settings: settings routes · Admin configuration endpoints
- auth routes → web routes: auth boundary · Authentication routes support protected web flows
- web backup → web routes: duplicate · Backup copy of the web route file
- cv viewer → profile: reads · Loads user profile data for CV rendering
- cv viewer → projects: reads · Includes portfolio projects in CV output
- cv viewer → templates: uses template · Selects a CV template for preview or PDF
- cv viewer → cv view: renders · Produces the public CV page
- resume export → templates: uses template · Manages available resume layouts
- resume export → resume view: renders · Serves dashboard resume screens
- resume export → admin guard: protected by · Admin-only boundary for resume/template management
- messages → conversation: reads/writes · Manages conversation threads
- messages → message: reads/writes · Loads and sends messages
- messages → messages view: renders · Serves the messaging UI
- settings → settings: reads/writes · Updates global configuration
- settings → settings view: renders · Serves settings management UI
- settings → admin guard: protected by · Admin-only control plane
- dashboard → dashboard shell: uses layout · Dashboard screens share the authenticated shell
- dashboard → user: reads · Uses the authenticated user context
- user → profile: owns · User-owned profile records
- user → projects: owns · User-owned portfolio content
- user → conversation: owns · Conversation ownership and scope
- conversation → message: contains · Conversations group individual messages
- settings → user: admin-manages · Client/user management and platform oversight