Technology in practice

CMS & Structured Content.

WordPress, ACF, Gutenberg, Joomla & OpenText

A content platform should make publishing manageable while supporting the structure a website needs. The work connects editable content, reusable layouts, relationships, and the experience visitors see.

How the pieces connectConceptual workflow
  1. Content modelTypes · Fields · Relationships
  2. Editorial workflowReusable blocks · Authoring
  3. Published experienceTemplates · Listings · Discovery
  • WordPress
  • Joomla
  • OpenText
The business context

Content that can be managed and reused.

A collection of pages often becomes a larger publishing system: resources, people, products, categories, and related content. Defining those concepts clearly helps editors work consistently and gives the frontend dependable information to display.

The layers of the stack

The tools and how I use them.

WordPressPublishing platform

WordPress

WordPress provides content management, templates, and an extension system. Custom development connects those capabilities to the website’s requirements. I consider the editor’s workflow alongside theme behavior, integrations, and the effort needed to maintain the result.

WordPressApplication functionality & service integration

Custom WordPress plugins

Custom plugins can carry business functionality beyond page templates and publishing. At Stack’s Bowers Galleries, I built complex, enterprise-level plugins that connected WordPress to backend business services through APIs. This brings application engineering and systems integration into the WordPress environment.

ACFDefined content fields

Advanced Custom Fields

ACF adds structured fields to WordPress editing screens. Fields can represent information that should be entered consistently and reused across templates. A useful field model gives editors clear choices and gives application code predictable values to work with.

GutenbergBlock-based editing

Gutenberg

The WordPress block editor composes content through reusable blocks. Blocks and patterns can balance editorial flexibility with a consistent design. I look at the choices editors actually need and how those choices affect layout, content structure, and future maintenance.

JoomlaWebsite content management

Joomla

Joomla is a content management system with its own extension and template conventions. Supporting a Joomla website starts with understanding its content organization, installed extensions, and publishing needs. That context matters when changing functionality or planning work across platforms.

OpenTextEnterprise content platforms

OpenText

OpenText includes enterprise content and web content management products. The implementation depends on the specific product and configuration. Content structures, publishing responsibilities, and integration points need to be understood within that environment before deciding how a change should be made.

WordfenceWordPress security

Wordfence

Maintaining a CMS includes its security configuration as well as the publishing experience. I have extensive experience configuring Wordfence, with hands-on use at Easy Breathe and Stack’s Bowers Galleries. I consider that configuration in the context of the WordPress application and the services supporting it.

PHPConnected content behavior

Custom PHP & content APIs

Templates, queries, and endpoints turn managed content into useful website behavior. A resource listing may depend on relationships and filters as well as the content itself. I work across those layers to connect the editorial model with the published experience.

My approach

Design for both the editor and the visitor.

I model the content editors need to maintain, where it will appear, and which layouts should be reusable. Changes are checked in both the editing interface and the published pages.

Experience in context

Related project work.

Get Network Visibility

My work includes custom WordPress/PHP development, content relationships, ACF/Gutenberg components, resource filtering, forms, and ongoing support within the FINNPartners-credited base theme and framework.

Read the case study

Stack’s Bowers Galleries

I developed sophisticated, enterprise-level custom WordPress plugins with API connections to backend business services, alongside WordPress/PHP website work and Wordfence configuration.

Explore enterprise WordPress plugins

Irdeto

I spent approximately six years building Irdeto’s website through Mimio Design, first in Joomla, then OpenText, and finally WordPress.

Explore the Irdeto case study

Corporate and healthcare websites

Other projects include the Miller Children’s Hospital Joomla website through Mimio Design, WordPress website development for Mission Valley Bank via Focus DMS, and WordPress development for Coast Produce.

View the career portfolio

Let’s talk about your project.

Tell me what you’re building or what needs fixing.

Start a conversation
Ascendo / Let’s connect

Let’s build
something great.

Start a conversation. Directly with Nick.

01 / Your project02 / Say hello
What can I help you with?

Choose what best describes your project.

Tell me a little about it.

What’s working, what’s not, and what would you like to improve?

Your details are used to respond to your inquiry. No account required.

Or email me directly: nlee@ascendosolutions.com