1
Use Oxygen's Query Builder with ACF to build a dynamically-generated case results archive page that updates automatically every time you add a new result — eliminating the manual page editing that causes most firms' case results sections to go stale. Create a Case Results custom post type with ACF fields: case type, settlement amount, injury description, court/jurisdiction. Build one Oxygen template for the case result listing using the Query Builder. Add a new case result by publishing a new post — no page editing, no developer needed. The archive page automatically displays the newest results first. Firms that maintain current, frequently-updated case results pages consistently outrank firms whose results section was last updated when the site launched.
2
Take advantage of Oxygen's global CSS variables to implement a one-click color scheme change for seasonal campaigns — a capability that page builder-based sites can't easily replicate. In Oxygen → Global CSS, define your core palette as CSS custom properties: --color-primary, --color-accent, --color-cta. Reference these variables throughout your design. If you want to run a holiday campaign with a slightly different color treatment, change two variables and every button, accent, and highlight on the site updates instantly. Revert for the next campaign. This is what large-scale marketing organizations do on enterprise platforms; Oxygen makes it accessible to any firm with a developer who understands CSS variables.
3
Use Oxygen's PHP integration to dynamically inject schema markup on every attorney bio page, pulling data directly from ACF fields — this is faster and more reliable than any schema plugin. Create a code block in your attorney bio template that outputs JSON-LD using PHP variables pulled from ACF: attorney name, bar number, practice areas, and office address. The schema updates automatically whenever you update the ACF fields — no manual schema editing, no plugin conflicts, no outdated structured data. Clean Oxygen + ACF architecture produces schema that's more reliable than any plugin-based approach because there's no intermediary layer between your data and the output.
4
Document every custom component you build in Oxygen with inline comments in the code editor — your future developer will thank you, and your current developer will thank themselves in 6 months. Oxygen sites with undocumented custom PHP blocks and JavaScript are genuinely difficult to maintain. A comment like "// Pulls attorney ACF fields: attorney_name, bar_admission_date, practice_areas (multi-select). Must match slugs in ACF field group ID 342" takes 20 seconds to write and saves 2 hours of archeology for the next person who opens the file. The technical sophistication that makes Oxygen sites perform well is also what makes them opaque without documentation.
5
Combine Oxygen with a dedicated staging environment and atomic deploys to test major updates before they affect live traffic — Oxygen's tight integration between design and code means a bad update can break the entire site rather than just one page. Oxygen builds are more monolithic than page builder sites because the theme layer is fully replaced. A broken Oxygen update doesn't just break one landing page — it can break the entire front end.
WP Engine's staging,
Kinsta's staging, or WP Staging Pro (plugin) lets you test major updates in isolation. Always stage, verify on multiple devices and browsers, then deploy to live. This is especially critical for Oxygen because rollback is harder than on a standard
WordPress setup.