How pulley71/master-andres-rocio works
Project type and purpose
• This is a PHP-based full-stack web application built on WordPress. It serves both public site rendering (index.php, themes in wp-content/themes) and an administrative back-end (wp-admin).
• The custom “asdrubal” theme under wp-content/themes/asdrubal provides presentation logic; the “classic-editor” plugin under wp-content/plugins extends editor behavior.
File structure
• Top-level entry points:
• index.php – front-door for all public HTTP requests.
• wp-config.php – database credentials and core configuration.
• wp-admin/ – admin UI code.
• wp-includes/ – core framework and library code.
• wp-content/ – user-generated content: themes, plugins, language files.
• Architectural patterns: WordPress’s pluggable hook/filter system (wp-includes/hooks), MVC-style separation:
• Presentation: theme templates (.php in asdrubal) and CSS/JS assets.
• Business logic: plugins and core functions.
• Data layer: MySQL accessed via wpdb and ORM‐style classes.
• Deployment artifacts: .htaccess for URL rewriting, SQL dump (ddbb.sql), language packs, license/readmes.
README for insights
• The README simply outputs get_template_directory_uri(), indicating focus on theme assets. No further architecture details provided.
Main components and interactions
a. Components:
• Client (browser or mobile app)
• Web server (Apache/Nginx + .htaccess rewrite rules)
• PHP runtime (mod_php or PHP-FPM) hosting:
– WordPress core (wp-includes, wp-admin)
– Custom theme (wp-content/themes/asdrubal)
– Plugin(s) (wp-content/plugins/classic-editor)
• Database server (MySQL/MariaDB)
• Optional external services: SMTP mail relay (via PHPMailer), CDN for static assets, cache layer (Redis/Memcached)
b. Relationships and data flow:
1. Client → HTTP request to index.php or wp-admin/*.php
2. Web server routes through .htaccess to index.php → WP bootstrap → load plugins/themes
3. WordPress loads hooks/filters and core functions (wp-includes) → queries the database via wpdb
4. Database returns result sets → core and plugin logic process data → theme templates render HTML/CSS/JS
5. PHP returns HTTP response; optional caches updated; emails sent via PHPMailer.
c. Architectural patterns:
• Monolithic PHP application with plugin-hook extension points
• Layered separation: routing (index.php/.htaccess) → core framework → business logic (plugins) → presentation (theme) → data (DB)
• Template hierarchy in the theme (page.php, single.php, etc.)
d. Key technologies: PHP 7+, MySQL, Apache or Nginx, SCSS/CSS (admin stylesheets), Vanilla JS (core), jQuery, TinyMCE (editor), get_template_directory_uri() for asset paths.