Epic: Lamoi WaaS, white-label WordPress network built by TEKORI
Imported from GitHub issue El-SaMa/lamoi-waas#25 by @El-SaMa.
Lamoi WaaS: a fully white-label WordPress network on lamoi.fi (WordPress as a service, like WordPress.com). TEKORI builds and edits client sites only through OMA MCP tools and a secure connector plugin; clients never do a manual step. Shops use WooCommerce with the WoodMart-based shop theme; content sites use Lamoi Base (Astra fork). Licensing is handled by the operator.
Code lives here (network, connector, white-label, themes, infra). OMA owns billing, provisioning, MCP tools, Backsies and legal; TEKORI owns the WordPress output target.
Build order
M1 Foundation
- #1 ADR 0001: architecture and hosting (decide before building)
- #2 Production and staging servers
- #3 DNS and TLS for lamoi.fi (inventory existing subdomains first)
- #4 WordPress multisite install and hardening
- #5 Ultimate Multisite fork: keep, slim or replace
- #6 Custom domains
M2 Connector and MCP
- #15 Connector core: tokens, scopes, validation, snapshots, undo, audit
- #16 Connector ops: site, design, content, media, SEO, forms, users
- El-SaMa/oma#173 OMA MCP tools (staff + customer)
M3 White-label
- #7 White-label layer + fingerprint check
- #8 Client roles and trimmed admin
- #9 Client dashboard in OMA + single sign-on
M4 Themes and catalogue
- #10 Lamoi Base theme (Astra fork) with design tokens
- #12 Block patterns = TEKORI section library
- #13 Plugin catalogue (vetted and own only)
- #11 Shop theme (WoodMart child, white-label)
- #14 Update pipeline (staging first)
M5 TEKORI builder
- El-SaMa/tekori#18 TEKORI WordPress output target
M6 Commerce and billing
- #17 Connector ops: WooCommerce
- El-SaMa/oma#174 OMA products, provisioning, limits, lifecycle
- #24 Sign-up and onboarding flow
M7 Backups and migration
- El-SaMa/oma#175 Backsies multisite
- El-SaMa/oma#176 Migrator (out to own hosting, and in)
M8 Launch
- #18 Security and abuse (phishing on lamoi.fi)
- #19 Performance and caching
- #20 Email from subsites
- #21 Monitoring and operations
- El-SaMa/oma#178 Legal: terms, DPA, acceptable use, shop templates
- #22 Site Insights for subsites
- #23 Docs, tutorials, pricing page, launch bundle
Rules for whoever builds this (Claude or Cursor)
- Never touch production before the staging run passes. DNS only through OMA tools.
- Plugins and mu-plugins: PHPCS + Plugin Check zero issues and a security review before "done".
- A feature is done when staff and customer MCP tools cover it and the handbook has it.
- Customer-facing text fi + en, native; launch posts and emails are drafts until the operator approves.