How raveen522/smart-architect---the-web-project works
Project Type & Purpose
• This is a full-stack website for an architecture portfolio. The project’s goal is to showcase the company’s projects, services, and team information while providing user interaction through contact forms, applications, and an admin (“super-user”) dashboard.
• Key indicators: Multiple static pages (index, about, projects, services, contact), PHP scripts for backend interactions (login, messaging, application loading/updating), and assets for images, fonts, and videos. The README specifies the use of HTML, CSS, JavaScript (front-end), PHP (back-end) with MySQL as the database engine.
Major Components
a. Client/Browser Layer:
• Browsers render the HTML pages (index.html, about.html, etc.) with styling (CSS) and dynamic behavior (JavaScript).
• The client sends requests to the server (e.g., form submissions on contact or job application pages).
b. Front-end Assets:
• HTML files (several pages including dashboard and public-facing ones).
• CSS files and JavaScript files (animations.js, main.js, dashboard.js) that handle the interactive UI.
• An assets folder containing fonts, images, and videos used to visually enhance the website.
c. Server/Backend Layer:
• PHP scripts (found in the “php” directory) handle core functionalities:
• User authentication (login.php, logout.php)
• Loading and updating messages and application statuses (loadMessage.php, updateMessageStatus.php, etc.)
• User settings management (changeUserSettings.php, loadUserSettings.php)
• Database connection management (connection.php)
• The “super-user” directory houses the admin-specific pages, including a dedicated dashboard.
d. Data Storage:
• A MySQL database (per README description) which stores application data such as user information, messages, project details, etc.
Relationships & Interactions
• Directional data flow from the Browser to the PHP Backend when a form is submitted (e.g., contact form, job application).
Architectural Patterns & Design Principles
• The project follows a separation-of-concerns principle: static content (HTML/CSS/JS) is handled separately from business logic (PHP scripts) and data persistence (MySQL).
• Even though no frameworks are used, the file structure implies a loose MVC style where different PHP files handle specific business logic tasks.
• The “super-user” directory clearly separates administrative functions from the public site.
Final Steps
• Related files where applicable (static pages together, PHP modules together) to visually reflect the file tree structure.
• Review the README and file tree one last time to check that all key functionalities and assets have been represented.