How iqgor/studie_salon works
Project type and purpose
• From the file tree and the minimal README (“studie_salon”), we see a classic full-stack web application:
• A “frontend” directory housing a Vue 3/Vite single-page application (SPA)
• A “backend” directory with PHP entry point (index.php), configuration (config.php), and PHPMailer for outbound mail
• Purpose inference: a “study salon” platform where users can view content, log in, subscribe, receive notifications or password resets via email.
File structure
• Top-level separation:
• frontend/ : Vue-based UI
• backend/ : PHP API & mailer
• frontend/ patterns:
• src/components, src/views → MVVM component and view structure
• src/router/index.js → client-side routing
• src/services/toastService.js → UI notification service
• assets/ → static JSON for quotes, subjects, carousel; CSS and audio assets
• vite.config.js, package.json → build tooling and dependencies
• backend/ patterns:
• index.php → request entry point (likely acts as a simple router or API handler)
• config.php → connection parameters (DB credentials, SMTP settings)
• PHPMailer library → encapsulates SMTP/OAuth email functionality
• .htaccess → URL rewriting or access control
README for architecture hints
• README only defines project name; no additional architecture notes.
• Rely on file structure to infer layers: UI (Vue), API (PHP), persistence (DB?), email service (SMTP).