Ability to lock specific editor items, elements, and components for Designer LifeLoop Branded Templates

A lot of organizations adhere strictly to brand standards and seek to prevent any unauthorized deviations or inconsistent modifications in their projects. This scenario pertains specifically to Designer Calendars, but it applies universally to all Designer Projects and Templates.

The communities often go off track from the official brand rules and the guidelines given by their head office. Right now, we can't lock things down while letting them change the font size, which is really important. As a result, sometimes the border and day number colors end up different from what was planned (bright colors not within brand standards). Also, stopping them from making two-page calendars, even though their corporate team has told them not to, is tough. They have communities that make the calendars the way they're supposed to, send them to the big bosses, and then sneak in extra two-page calendars, despite clear instructions not to do so.

Locking the Calendar stops the staff from changing the font size, but we need to keep it unlocked for that purpose. However, the communities can still make changes to the following items and more:

- Layout

- Text and day number colors

- Background and header colors

- Activity colors

- Font style

- Placement

- Duplication and addition of pages

Additionally, the communities are instructed not to incorporate elements such as squares, circles, lines, images, and components, though exceptions are made for text boxes in certain cases.

The current situation necessitates vigilant oversight from both myself and the corporate team. Nonetheless, this constant monitoring is cumbersome, and an ideal solution would involve the capability to selectively lock specific features within the editor.