Technical Documentation

Documentation

A practical record of how the portfolio was built, where each part is edited, which plugins were created and how the content governance works across the site.

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

The project is split between one custom theme, one toolkit plugin and two MU plugins. This keeps rendering code organized, content structured and runtime behavior explicit.

  • Theme: public pages, templates, layout, CSS, typography and render helpers.
  • Toolkit plugin: CPTs, project meta fields, special-page meta boxes and global site settings.
  • Runtime MU plugin: performance cleanup, delayed trackers, sitemap and frontend optimizations.
  • Page cache MU plugin: HTML caching for anonymous traffic with purge rules.

Editing Model

The site uses the classic editor and structured fields instead of a page builder-driven layout. That keeps the UI editable while preserving a stable front-end architecture.

  • Page body copy stays editable in the standard page editor.
  • Projects and brands use dedicated CPTs with typed meta fields.
  • Special pages expose dedicated field groups in wp-admin.
  • Shared labels, SEO defaults, header and footer live in Lago Portfolio > Site Settings.

CPTs and Field Architecture

The site is organized into real project categories so content, screenshots, stack descriptions and access notes remain structured and reusable.

  • Delivery Project
  • App Project
  • PMS Project
  • CRM Project
  • Fusion AI Project
  • Served Brand

Plugins Created for This Development

Custom plugins were created to avoid generic page-builder dependency and to document engineering practices directly in WordPress.

  • Lago Process Toolkit: registers CPTs, creates admin metaboxes, stores structured data and centralizes portfolio administration.
  • Lago Runtime Optimization: reduces WordPress noise, controls asset behavior, improves output markup and adds sitemap/runtime safeguards.
  • Lago Page Cache: handles full-page cache for anonymous traffic with conservative bypass rules and invalidation on content updates.

Guide to All Site Content

Everything visible on the site can now be managed from wp-admin through one of the channels below.

  • General WordPress settings and navigation menu.
  • Lago Portfolio > Site Settings for header, footer, SEO defaults and shared labels.
  • Each special Page for body copy and page-specific field groups.
  • Each CPT entry for project data, credentials, stack, evidence and featured images.

Practices and Evidence

The build reflects a production-minded WordPress approach, combining structured content, careful caching, explicit source control and documentation-first delivery.

  • Code-driven theme templates instead of layout-by-editor.
  • Structured meta fields for predictable content governance.
  • Custom runtime hardening and caching for performance.
  • Git rollback points and documentation pages for safer evolution.

Agenda técnica

Vamos revisar arquitetura, escopo e próximos passos.

Uma conversa curta para avaliar WordPress como camada de aplicação, integrações, infraestrutura e responsabilidade de produção.

Agendar