Skip to content

ServerKit is a lightweight, modern server control panel for managing web applications, databases, and services on your VPS or dedicated server. Built with Python/Flask backend and React frontend.

docs(wordpress): correct extraction audit — frontend not yet extracted

Juan Denisfb19778e7f55
diff --git a/docs/EXTRACTION_WORDPRESS_AUDIT.md b/docs/EXTRACTION_WORDPRESS_AUDIT.md
index 403cf6f6..b42f40b1 100644
--- a/docs/EXTRACTION_WORDPRESS_AUDIT.md
+++ b/docs/EXTRACTION_WORDPRESS_AUDIT.md
@@ -5,10 +5,15 @@ backend now lives in `builtin-extensions/serverkit-wordpress/` as a bundled,
default-installed flagship (D4), loaded via an importlib bridge. See the Phase 5
section of `docs/plans/12_EXTENSIONS_PLATFORM_PLAN.md` for the shipped scope and
deviations (models stay core; event-catalog + Fail2ban WP filter kept core as
-two-speed items). The **frontend UI is now contributed by the extension too** — a
-single `wordpress/*` splat route self-renders the whole WordPress sub-router (tab
-group + full-bleed detail), so the sidebar item, routes, palette, and page titles
-all come from the manifest. Largest single move in the plan; done after Email (#32).
+two-speed items). The **frontend UI is still core, NOT yet extracted** (corrected
+2026-07-22, plan 52 Phase 1 — an earlier revision of this doc overstated it as
+done): the extension's `index.jsx` is only a **re-export shell** that imports the
+real pages from `frontend/src/pages/WordPress*` (5 pages) and
+`frontend/src/components/wordpress/` (40 files), with the three `_wordpress*.scss`
+files still imported by `main.scss` and residual core wiring in `App.jsx`
+(title fallbacks) and `sidebarItems.js`. Only `WordPressSshImport.jsx` truly lives
+in the extension today. The physical frontend move is plan 52 Phase 4; leaving the
+tree entirely is Phase 5.
**Verdict:** extractable, but WordPress has **real core hooks** that must be
inverted/guarded first. WordPress ships as a bundled, default-installed,
uninstallable extension (D4) — never a marketplace hunt.