27 lines
1.3 KiB
Markdown
27 lines
1.3 KiB
Markdown
# Workspace Map
|
|
|
|
## Imported Source
|
|
|
|
| Area | New Path | Original GracePress Path |
|
|
| --- | --- | --- |
|
|
| WordPress plugin | `wordpress/plugins/mesh-press/` | `plugins/mesh-press/` |
|
|
| Bridge service | `bridge/meshpress-bridge/` | `tools/meshpress-bridge/` |
|
|
| Catalog connector | `meshcentral/plugins/gracepress/` | `meshcentral-plugins/gracepress/` |
|
|
| Theme Studio plugin | `meshcentral/plugins/gracepress-theme-studio/` | `meshcentral-plugins/gracepress-theme-studio/` |
|
|
| Current artifacts | `dist/current/` | `dist/` selected MeshPress and MeshCentral artifacts |
|
|
|
|
## Boundaries
|
|
|
|
- WordPress plugin code belongs under `wordpress/plugins/`.
|
|
- Node helper services belong under `bridge/`.
|
|
- MeshCentral runtime plugins belong under `meshcentral/plugins/`.
|
|
- Generated release evidence belongs under `dist/current/` until dedicated build output rules exist.
|
|
- Upstream MeshCentral source belongs outside the tracked repository by default.
|
|
|
|
## Follow-Up Work
|
|
|
|
- Port or rewrite the GracePress `mcplugin` build flow so this workspace can package MeshCentral plugins independently.
|
|
- Decide whether MeshPress should remain catalog-released through GracePress or gain a separate release channel.
|
|
- Normalize mojibake metadata in imported manifests and headers during the first real source change.
|
|
- Add smoke checks for the bridge service and MeshCentral plugin identity rules.
|