How cristianolivera1/cms-tienda-ropa works
Main Components
• Client-Facing Web Application ("cliente"):
– Contains pages to display products (e.g., producto/*), handle shopping cart activities (carrito_compras), contact forms, and category listings.
– Resources (CSS, JS, images) are organized under "cliente/recursos".
– Interaction with the database comes through PHP scripts like coneccionbd.php.
• Administrative Backend ("paneladministrador"):
– Used for managing products, categories, brands, stock, offers, users, and sales.
– Structured into many subdirectories (e.g., productos, detallesproducto, usuarios, reportes, and ventasclientes) for modular management.
– Incorporates third-party libraries like FPDF (located in paneladministrador/fpdf) for generating PDF reports.
• Database:
– Represented by the SQL dump file (tiendacms.sql) and various connection scripts (coneccionbd.php in both cliente and paneladministrador).
• External Libraries and Assets:
– FPDF for PDF generation.
– Various CSS, JS, and font libraries that serve both frontend and admin interface needs.
Relationships and Interactions Between Components
• The client side interacts with the backend through PHP and database calls:
– User requests from the client interface (e.g., viewing products, adding to cart, or contacting support) are processed by PHP scripts which query or update the database.
• The admin panel handles content management:
– Administrative users log in (via paneladministrador/login.php) and perform CRUD operations on products, categories, and sales, which in turn update the database.
• Shared Database Connections:
– Both the client and admin sides use connection scripts (coneccionbd.php) to communicate with the underlying database, ensuring data consistency.
• File and Resource Management:
Architectural Patterns and Design Principles
• Separation of Concerns:
– Clear physical separation between the public and administrative interfaces.
• Modular Design:
– Each functionality (e.g., product management, cart operations, reports) is contained within its subfolder.
• Reusability:
– Common functions and configurations (like database connections and file inclusions for headers/footers) are reused across the application.
• Integration of External Libraries:
– Integration of FPDF for PDF reporting and standardized front-end libraries ensures extended functionality without reinventing the wheel.
Technologies, Frameworks, or Libraries
• Server-Side: PHP (with occasional Hack code)
• Frontend: HTML, CSS, JavaScript
• PDF Generation: FPDF
• Database: Likely MySQL (inferred from tiendacms.sql) along with PHP-based connection scripts