Documentation

This page documents the WordPress build used for this 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 site is split into a custom theme, one toolkit plugin for content architecture and two MU plugins for runtime behavior and page cache. This keeps editing simple in wp-admin while preserving code ownership, content modeling and special-page workflows in the repository.

• wp-content/themes/lago-process: custom portfolio theme templates, layout, CSS, navigation and page rendering.
• wp-content/plugins/lucas-portfolio-toolkit: CPTs, custom field architecture, admin menus, options and page-specific editable fields.
• wp-content/mu-plugins/portfolio-runtime-optimization.php: runtime cleanup, delayed trackers, image handling, sitemap and frontend hardening.
• wp-content/mu-plugins/portfolio-page-cache.php: anonymous visitor page cache with bypass rules and invalidation.

Editing Model

The project intentionally disables Gutenberg and works with the classic editor plus structured meta fields. The goal is to show a disciplined WordPress build that is editable in admin without relying on page builders for the core portfolio layout.

• Pages keep long-form body content in the classic editor.
• Projects, brands and assessment visuals use dedicated post types with structured meta fields.
• Special templates such as home, documentation, plugin-code, rollout, versioning, projects, brands, resume/CV, schedule, assessment and bonus assessment expose dedicated wp-admin fields.
• Global header, footer, SEO defaults and shared labels are managed in the portfolio Site Settings screen.

Content Types and What They Control

The portfolio is organized around real content models so the public site, admin workflow and REST output stay aligned. The CPT layer handles repeatable entities while page field groups handle one-off presentation flows like resume and assessment pages.

• App Projects: product sites, marketing apps and web application cases.
• CRM Projects: lead capture, cadences, integrations and automation layers.
• Delivery Projects: operational commerce and ordering/admin systems.
• PMS Projects: hospitality systems, booking, operations and hotel flows.
• Fusion AI Projects: assistants, chatbot and OpenAI-related cases.
• Served Brands: hospitality websites and brand-level delivery evidence.
• Assessment Visuals: reusable visual entries used by the Verdian take-home template galleries.
• Resume / CV: special page field group for summary, experience timeline, skills, infrastructure and languages.
• Assessment pages: special page field groups for the Verdian take-home and bonus assessment flows.

Custom Field Groups

Custom fields are split by editing context so each screen exposes only the data it needs. This keeps the admin lean while preserving a structured content contract for the theme.

• Project CPT fields: summary, client type, stack, stack-used list, integrated APIs, integrations, automation flow, admin features, code evidence, source path, URLs, temporary credentials, results, icon and flexible JSON sections.
• Brand CPT fields: brand summary, brand URL, scope, stack, client type, source path, access details, integrations, results and flexible JSON sections.
• Documentation page fields: hero eyebrow, lede, summary cards JSON, navigation JSON and section blocks JSON.
• Resume / CV page fields: meta description, badge, role, location, contact details, summary, experience JSON, skills JSON, infrastructure JSON and languages JSON.
• Verdian assessment fields: bilingual hero copy, competency assessment items, analytics sections, architecture sections, growth questions, visual reference blocks, AI disclosure blocks and closing CTA/content.
• Bonus assessment fields: bilingual intro, environment, implementation, plugin explanation and closing sections.
• Assessment visual fields: target section, public label, caption, alt override, external image URL and featured image.

Plugin Summary and Implemented Features

Three custom plugins/modules organize the portfolio build.

• Lucas Portfolio Toolkit: registers CPTs, exposes structured custom fields for projects, brands, assessment visuals and special pages, groups portfolio screens in the admin, adds page-specific meta boxes and provides global site settings.
• Portfolio Runtime Optimization: removes unnecessary WordPress noise, optimizes asset output, delays trackers, improves image markup and serves a lightweight sitemap.
• Portfolio Page Cache: stores generated HTML for anonymous GET traffic, bypasses sessions/admin/unsafe requests and purges cached files when content changes.

Admin Operations and Cache Control

The WordPress admin now includes explicit controls for code-evidence sourcing and cache invalidation so the published site can be refreshed without shell access.

• Plugin Code page: the admin metabox includes lp_plugin_code_paths, one real server path per line, already prefilled with the current plugin, MU plugins and theme files.
• Code page rendering: the public template reads those paths directly, resolves labels from the registry when possible and falls back to inferred title/description for unknown files.
• WordPress top bar: a Clear Portfolio Cache action is available for admins and purges the full-page cache before redirecting back with a success notice.
• Menu mobile: the header now uses explicit open/close state plus collapsible submenus on mobile, reducing overflow and ensuring internal pages behave the same as the homepage.

Content Guide

Everything visible on the site should be updated through one of four places in wp-admin.

• Settings > General and Menus: site title and primary navigation.
• Lucas Portfolio > Site Settings: header mark/subtitle, CTA, footer text, SEO defaults, archive labels and shared single-project labels.
• Pages: body copy and page-specific template fields for documentation, projects, brands, schedule, versioning, Zapier, plugin-code, home, rollout, resume/CV, assessment and bonus assessment.
• Plugin Code admin fields: use the real path list to decide exactly which files appear on the public code evidence page.
• Lucas Portfolio CPTs: project summaries, stacks, integrations, credentials, evidence, icons and featured images.
• Assessment Visuals CPT: gallery images and captions used inside the assessment page.

Server Evidence and Good Practices

The site itself documents both implementation and operational thinking.

• Projects reference real systems hosted on this server and expose controlled assessment details through CPT fields.
• The theme preserves semantic templates instead of embedding presentation logic into the editor.
• Structured fields reduce accidental layout breakage and make content governance easier.
• Performance is handled conservatively with MU plugins instead of relying only on third-party optimization plugins.
• Versioning, rollback points and documentation pages make the build easier to review and safer to evolve.