Technical Documentation

Documentation

A practical record of how Lucas Bacellar's portfolio was built, where each part is edited, and which technical evidence should be reviewed.

EditorClassic WordPress
LayoutCustom PHP theme
FieldsACF-like plugin
PerformanceRuntime + page cache

This page documents the WordPress build used for Lucas Bacellar’s portfolio. The visible content is editable in the classic editor, while the sections below are rendered by the theme template.

The goal is to demonstrate custom WordPress architecture, marketing integrations, runtime optimization, a page cache layer and evidence-based project presentation.

Build Structure

  • wp-content/themes/lago-process: templates, visual layout, typography, grids and public pages.
  • wp-content/plugins/lago-process-toolkit: CPTs, editable fields, REST fields and the Lago Portfolio admin menu.
  • wp-content/mu-plugins/lago-runtime-optimization.php: runtime optimization, asset cleanup, sitemap and delayed trackers.
  • wp-content/mu-plugins/lago-page-cache.php: visitor page cache with safe bypass rules and automatic invalidation.
  • deployment/update-lagoprocess-project-fields.php: seed script for projects, brands, temporary credentials and documentation.

Classic Editor, Not Gutenberg

The toolkit plugin applies use_block_editor_for_post and use_block_editor_for_post_type filters returning false. Pages, brands and project CPTs open in the classic WordPress editor.

Content stays editable in the dashboard, while core layouts remain in the theme to avoid page-builder dependency.

CPTs and Custom Fields

The Lago Portfolio admin menu groups Delivery, App, PMS, CRM, Fusion AI and Served Brands. Each project includes fields for technology stack, integrated APIs, automations, evidence, project links and temporary access credentials.

Cache System

The site uses a custom MU plugin page cache to demonstrate production performance work without relying on a third-party cache plugin. It caches anonymous GET requests, bypasses admin/logged-in/POST/query-string traffic, sends cache headers and clears cached HTML when content changes.

Server Evidence

  • /var/www/delivery.fusioncore.com.br: Laravel, Filament, Sanctum, Guzzle, Vite and Tailwind.
  • /var/www/fusioncore.com.br: Astro, Node adapter, Tailwind and Nginx deployment.
  • /var/www/raizes.fusioncore.com.br/app: PMS, booking engine, channel manager, OpenAI, WhatsApp, revenue and OTA jobs.
  • /var/www/app.fusioncore.com.br: CRM, Google API Client, webhooks, email flows, cadences and internal scripts.