Menu Area Migration #47
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This release migrates the custom menu area functionality from the Elayne theme to the Elayne Blocks plugin, completing a strategic separation of theme and plugin responsibilities. The version bump to 2.3.2 reflects this architectural change, which removes theme-level menu area registration while maintaining compatibility with sites that have the Navigation Extension plugin installed. This change streamlines the theme's codebase by delegating navigation customization features to the plugin layer, following WordPress best practices for theme/plugin separation.
Theme Architecture Changes:
functions.php, eliminating theelayne_register_menus()function that previously registered 'primary' and 'footer' navigation menuselayne_menus_initaction hook that attached menu registration to WordPress initializationVersion and Documentation Updates:
style.css,readme.txt, andCHANGELOG.mdto reflect the menu area migrationreadme.txtfor WordPress.org theme repository complianceFiles Changed:
CHANGELOG.md(Modified)functions.php(Modified)readme.txt(Modified)style.css(Modified)