All topics

Guide

Oxygen 6 Template Content Area: Setup & Troubleshooting

Set up an Oxygen 6 template with unique page content. See a tested two-page example and troubleshoot missing content, repeated text and template conditions.

7 min read · Updated 16 October 2026

What does Template Content Area do in Oxygen 6?

Template Content Area is the place in an Oxygen template where each page’s own content appears. The template controls the shared frame. Open an individual page in Oxygen to design the content that belongs inside that frame.

For example, a Web design page and a Website maintenance page can share the same service introduction strip and contact section, while keeping different headings and descriptions. Change a shared section in the template and both pages receive that change.

This is different from an Oxygen design set, which lets you import saved layouts into a project. A design set helps you start a layout; a template determines the frame used when a page is displayed.

Before you start

  • Use Oxygen 6, the new builder. Oxygen Classic has a different interface and workflow.
  • Work on a test website or staging copy. Create two test pages: Web design and Website maintenance.
  • Keep the new template’s conditions limited to those two pages while testing.
  • Decide which sections should be shared. Put page-specific service wording in the individual pages.

You can start with your own layout or the free service website kit. Its page, header and footer layouts are imported separately; adding a Design Set does not automatically create this template arrangement.

How to add Template Content Area to an Oxygen template

  1. Create the shared template. In WordPress, go to Oxygen → Templates, add a template for Pages and open it in Oxygen. Use a clear name such as Service pages.
  2. Build the shared frame. Add the service strip and shared next-step section. Put the unique page content between them. If your site already uses separate header and footer templates, keep those there so you do not add them twice.
  3. Add the content slot. While editing the template, open the Add panel, find the Dynamic category and add Template Content Area between the shared sections. It is available in a template, rather than in an ordinary page’s Add panel. Use one content area in this template.
  4. Check the structure. Use a div or section for the content area and inspect the finished page’s landmarks. Avoid nesting a main element inside another main. If the surrounding template already provides the main landmark, the content area does not need a second one.
  5. Choose the matching pages. Set the template to apply only to your two test pages. Check the template’s location, conditions and priority if another template also matches. Save it.
  6. Edit page A. Open Web design as an individual page in Oxygen. Add its own H1 and service description, then save. The shared sections belong to the template; the page’s own elements belong in its content area.
  7. Edit page B. Open Website maintenance in Oxygen. Add a different H1 and description and save. Do not duplicate page A’s service copy into the shared template.
  8. Open both saved frontend pages. Check that the same frame surrounds different content. Change one shared sentence in the template, save again and confirm that both pages update.

Where should I edit the content?

Edit the template when the change should be shared

Open the Service pages template to change the service strip, shared next step or surrounding layout. Review every page matched by its conditions after a shared change.

Edit the individual page when the content should be unique

Open Web design or Website maintenance to change that service’s heading, description, images and links. You do not type those service details into Template Content Area’s settings; it renders the page’s own content.

Use a Component for a reusable section

A Component is useful for a repeated section that you place in different layouts. Template Content Area has a different job: it reserves the page-specific region inside a template. You can use both in the same project.

Two pages, one shared template

The screenshots below come from two private test pages on this website. The blue sections belong to the same template; the white section contains each page’s own Oxygen content. The example is fictional.

Test page A: Web design content between the shared service template sections.
Page A: Web design has its own heading and description between the shared sections.
Test page B: Website maintenance content inside the same shared service template.
Page B: Website maintenance uses the same frame with different page content.

After changing the shared strip to “Shared service page layout”, the new wording appeared on both frontend pages. Their individual headings stayed different. The temporary template matched only the two test pages.

Oxygen template content not showing? Check these first

The page content is missing or blank

Confirm that the matching template contains Template Content Area. Then open the actual page in Oxygen and check that it has saved content of its own. Saving a shared template does not create the service text for each page.

Every page shows the same text

Check whether that text was added to the shared template. Move page-specific wording to the individual pages. Keep only the content that should repeat in the template.

The shared frame does not appear

Check the page’s actual URL against the template’s conditions. If several templates match, review their priority. Save the intended template and inspect the frontend rather than relying only on the editor preview.

I cannot find Template Content Area in the Add panel

Make sure you opened an Oxygen template, rather than a page, header or footer. Look in Dynamic. If you already have a content area in that template, use the existing one.

The page has duplicate headings or navigation

Look for the same content in both the template and page. Keep the page-specific H1 in one place. If your site already displays a header or footer through separate templates, avoid importing another copy into the page body.

Saved changes are not visible

First confirm that you saved the item you edited: the template for a shared change or the page for a unique change. Then check the correct frontend URL. If the saved version is still missing, investigate the relevant page or server cache and compare a fresh browser session.

Common Template Content Area questions

Can one template have two Template Content Areas?

No. Oxygen allows one per template. Add Containers inside the individual page when its unique content needs several sections.

Do I need custom PHP or CSS for this setup?

No custom PHP or CSS is needed to connect the template and page content. Use Oxygen’s template conditions and native elements. Styling still needs to be checked with your actual content.

Are Oxygen templates and design sets the same thing?

No. A template applies a shared structure to matching pages. A design set is a collection of layouts you import. You can adapt an imported layout into your own template, but importing it alone does not define where that template applies.

Check your finished service pages

  • Each page displays the intended shared frame and its own content.
  • A shared edit appears on both pages without replacing their unique text.
  • An unrelated page is unaffected by the template’s conditions.
  • Each page has one descriptive H1 and a sensible main-content landmark.
  • Long headings fit at narrow widths, and links lead to the correct destinations.
  • You have reviewed the saved frontend at desktop and phone widths.

Use the website launch checklist to record checks for the real project before it goes live.

Test scope and official references

Checked on 16 October 2026 with WordPress 7.1.3 and Oxygen 6.2.0-beta.9. Two private pages were rendered through one template restricted to their IDs. The check covered different page content, a shared text update, an unaffected About page, and horizontal fit at 390 and 1440 CSS pixels in desktop Chromium. This was a native-element and frontend test, rather than a complete manual walkthrough of every editor control.

The temporary test pages and template are not public resources. This example does not establish compatibility with every Oxygen version, third-party extension or site configuration, and does not replace checking your own project.

Independent, AI-assisted documentation by Benjamin Olsen. Interface labels can vary between releases; use the official references alongside the tested example.

Need more help with this guide? Contact Benjamin →

Explore more topics