Oxygen Attributes (Premium)

A data- attribute repeated across a hundred elements is hidden debt

Your animation library, your slider or your analytics tool read HTML attributes that visitors never see. If Oxygen only lets you type them by hand, element by element, you end up with the same name copied dozens of times across the whole site. The day the library renames that attribute in a new version, or you decide to replace it with another one that uses a different name, nobody remembers where each one was, and the failure isn't obvious: something simply stops working.

Oxygen Attributes is a plugin for Oxygen Builder that takes those attributes out of each element and manages them from a single place. It's a tool for people who build sites with Oxygen and work with third-party scripts, not for those who just want a nice design.

Oxygen Attributes: define the name once and pick the value with controls

The idea is to separate two things that Oxygen mixes together: what the attribute is called and what value it takes on each element. Here is what it offers:

• Centralized manager: attributes are defined in the backend. If a library renames one, you change it in a single place instead of hunting down every use by hand.
• Field controls: besides the text field, the value can be a dropdown list, a button list, a checkbox or a color picker.
• Sub-elements as targets: with Oxygen's native attributes only the wrapper tag is marked. Here you can target child elements, such as the images in a gallery or the links of social icons.
• Dynamic values: the value can come from post data, from Advanced Custom Fields or from the result of your own PHP function.

What still depends on you

It requires Oxygen Builder, because it is an extension of it and doesn't work on its own. It also doesn't bring any JavaScript library: it adds attributes to the HTML, not behavior. You need to know which name and values the script you plan to use expects, because the plugin doesn't know them in advance. And if you rely on Advanced Custom Fields or a PHP function, those fields and that function must already exist on your site.

Children, ACF and libraries: the questions that usually come up first

Can I put the attribute on child elements and not only on the wrapper?

Yes. It's one of its main features: you can aim it, for example, at the images in a gallery or at the links of social icons.

Can values be filled in with custom fields?

Yes. Dynamic values support post data, Advanced Custom Fields fields and whatever your own PHP function returns.

Does it work without Oxygen Builder?

No. It extends Oxygen's HTML attribute options and depends on it.

Does it tell me which attributes my library needs?

No. It manages the attributes you define, but the right name and values come from each library's documentation.

Renaming an attribute in the backend saves you from reviewing every page

To get the most out of it from the start, don't begin with the elements, begin with a list: which libraries or services on your site read attributes and which ones they are. Define each attribute only once in the manager and choose the type of control that prevents typing mistakes: a dropdown if there are only a few valid values, a color picker if it's a color. Then apply them to the elements, to the children when needed, and check the resulting HTML on a test page before extending it to the whole site.

When a library renames an attribute, or you switch libraries, the change is made in the backend, at a single point, instead of opening page after page.