WordPress Theme Rules Force Developers to Split Features Into Companion Plugins
A WordPress developer with ten years of experience had a block theme rejected by WordPress.org for including functionality that reviewers said belonged in plugins, not themes. The platform's long-standing policy separates presentation (themes) from functionality (plugins) to reduce ecosystem clutter, but the developer argues it now produces an unintended outcome. Most serious block themes today ship alongside companion plugins, meaning users must install multiple components to get a complete experience. The developer notes the end result mirrors the old lock-in problem, just spread across several admin panel entries instead of one. He plans to comply by moving flagged code into a companion plugin, calling the distinction a difference in folder location rather than actual user experience.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in