Re-enable Gutenberg block editor sidebar (v0.12)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript, webpack
- Domain
- api, build-system, frontend
Research direction
Start with the preserved src/extensions/editor.js and the git history for includes/class-editor-sidebar.php, then inspect webpack.config.js for the removed editor entry. Restore the editor integration and validate it in the Post editor, Page editor, and Site Editor against the listed acceptance criteria, including chat tools and post context.
Written by the indexing model from the issue text.
Description
Context
Block editor integration that added an Agentic Admin panel to the Gutenberg sidebar via `registerPlugin`. Removed in v0.11 alongside the wp-admin toolbar sidebar because the UI wasn't finished to the bar set by the main admin page.
Removal commit on `feat/220-wp-7-ui-overhaul` branch (this session) — sources preserved:
- `src/extensions/editor.js` (entry point)
- `includes/class-editor-sidebar.php` (deleted, recover via git history)
- `webpack.config.js` (`editor` entry removed)
What v0.12 needs
- Restore `Editor_Sidebar` class (`enqueue_block_editor_assets` hook, etc.)
- Restore webpack entry for `editor`
- Editor sidebar UI parity with the main admin page chat (model status, engine selector, tool-call rendering)
- Sensible content-aware behavior: when editing a post, the assistant should know the current post context (title, content, status)
- Test in Post editor, Page editor, and Site Editor
Acceptance
- Plugin icon visible in Gutenberg sidebar header
- Clicking opens the Agentic Admin panel
- Chat works with full tool-call UI
- Post context available to the assistant (so prompts like "summarize this post" work)
- Doesn't break the editor on activation/deactivation
Why deferred
WordPress.org submission for v0.11. Editor integration adds complexity (content context, REST nonce, block context) that wasn't fully solved.
- Dominant language
- JavaScript
- Stars
- 28
- Forks
- 6
- Avg merge
- 9h 16m
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pluginslab/wp-agentic-admin
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pluginslab/wp-agentic-admin#226 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
pluginslab/wp-agentic-admin#215 ·
-
WP.org submission: close out review T4 (17 Jun) and stop the review loopMay be free again @ivdimova claimed this 45 days ago, and no pull request is open. Openphp question wporg-submission
pluginslab/wp-agentic-admin#228 · 5 comments · 2 assignees ·
-
enhancement ux
Difficulty 4/5 3-5 days Newbie friendliness 48/100
pluginslab/wp-agentic-admin#223 ·
-
ai-ml enhancement react-js
Difficulty 4/5 3-5 days Newbie friendliness 45/100
pluginslab/wp-agentic-admin#221 ·
All issues in pluginslab/wp-agentic-admin
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
TheOdinProject/curriculum#31444 ·
Maintainers usually reply within 1 day
-
software-development-practices software-development-practices:nist-ssdf
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
githubnext/gh-aw-cao#15860 ·
Maintainers usually reply within 1 day
-
framework/gatsby help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 2 days
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
PedestrianDynamics/pyFDS-Evac#476 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
aiko-chan-ai/DiscordBotClient#380 ·