Proposal: Dynamic Custom Fields Based on Theme Selection

[fxivaninfobae]

🎯 Objective

Implement the ability to conditionally display custom fields based on a value that defines the theme, with the following goals:

1. Avoid errors: Prevent editors from entering values that do not apply to the block they are inserting.
2. Improve editor UX: Make block configuration easier and faster.
3. Prevent design flaws: Avoid incorrect or inconsistent configurations.
4. Automation: Set default configurations based on the selected theme.

---

📝 Use Case Example

Currently, we have a custom field called "Theme", where the user can choose the style the component will have (e.g., "World Cup", "Special Events", "Academy Awards", etc.).

The idea is that upon selecting a theme, we use an object that makes the remaining custom fields dynamic. The goal is to hide fields from the editor that are irrelevant to the chosen theme.

The Current Problem:

If the editor selects "Mundial 2026":

• Custom fields that are not useful for that theme (such as 'Combined tag or keyword', 'Limit new', etc.) are still displayed.
• In the "Block one", "Block two", and "Block three" selectors, absolutely all global options for the site appear, instead of showing only the options relevant to that specific theme.

| Fields that should be hidden based on the selected theme |

This creates a highly complex configuration process, causing editors to make mistakes. As a result, the component is not used very much due to the poor user experience.

---

💡 Summary and Technical Limitation

We need the visibility and options of the custom fields to be dynamic rather than static.

We know there are plugins to solve this, but implementing an individual plugin for each custom field would negatively impact the bundle size and cause the project's codebase to grow disproportionately. We are looking for a centralized or more efficient solution.