It would be very helpful for organization purposes if Oxygen templates and reusable parts were separated in the backend. As of right now, Oxygen groups them all into the same page:
Which is highly confusing on websites with many templates and reusable parts.
The main reason I see a need for this is that the marketing agency I work for uses six different page templates for every client site so that we all are on the same page and use the same workflow. But naturally, each website has a different number of reusable parts based on the size and complexity of the project, but since they get grouped with templates, it can make it a challenge to stay organized.
If templates and reusable parts were separated in the backend, it would be much simpler and quicker to find what we are looking for.
I can't think of other page builders that use a similar structure for their templates and reusable parts. Still, again, for internal organizational purposes in agencies, this feature would be well-received.
It would be very helpful for organization purposes if Oxygen templates and reusable parts were separated in the backend. As of right now, Oxygen groups them all into the same page:
Which is highly confusing on websites with many templates and reusable parts.
The main reason I see a need for this is that the marketing agency I work for uses six different page templates for every client site so that we all are on the same page and use the same workflow. But naturally, each website has a different number of reusable parts based on the size and complexity of the project, but since they get grouped with templates, it can make it a challenge to stay organized.
If templates and reusable parts were separated in the backend, it would be much simpler and quicker to find what we are looking for.
I can't think of other page builders that use a similar structure for their templates and reusable parts. Still, again, for internal organizational purposes in agencies, this feature would be well-received.