Content platforms and CMS
- Role-based editorial workflows
- Scheduled publishing
- Rich-text editing (TipTap)
- Newsroom sync
Loading
Capabilities
Every capability on this page is demonstrated in software SomaMe built — in production or in working development builds. Each links to where you can see it.
Layer 01
The layer users touch: web platforms, apps, the cloud behind them, and the hard parts — realtime, money, messaging, offline and AI.
Large public platforms and signed-in workspaces: server-rendered pages, multilingual content, structured data for search and AI answer engines, and redirects that carry legacy links forward.
Proven in: Global Platform · Workers Guild System
Cross-platform apps for Android and iOS, including devices without Google services, shipped to both stores and maintained through releases.
Proven in: Asori & Asori Admin · COP DWC Visit
Postgres and Firestore back ends with scheduled jobs, edge and cloud functions and private workers — authorisation enforced on the server.
Proven in: Asori platform · Workers Guild System
Group and direct chat with reactions, attachments and voice notes, live updates across devices, and push-driven workflows.
Proven in: Workers Guild System
Mobile Money collection, prepaid wallets and ledgers that reconcile — with idempotent settlement and costs shown up front.
Proven in: Asori SMS wallet
Targeted in-app messages, push with deep links, email, and personalised bulk SMS with audience rules and delivery tracking.
Proven in: Asori communication
Queues and outboxes for the actions that must never be lost, with permissions rechecked when devices reconnect.
Proven in: Resilient field workflows
On-device computer vision with consent and liveness checks, and integration with African-language speech APIs.
Proven in: Consent-aware computer vision · Khaya Demo
Layer 02
The layer organisations depend on: tenancy, roles and scopes, content governance, reporting, security and shipping reliably.
Tenant isolation, role and scope models tied to an organisation’s real structure, deny-wins overrides, and lifecycle states that never lose data.
Proven in: From one congregation to many · Workers Guild roles and scopes
Editorial systems with roles, approval queues, scheduled publishing, revision history, media libraries and audit logs — and content synced from existing sources.
Proven in: Global Platform CMS · General Secretary’s platform
Operational dashboards, custom report builders, report templates that roll up through an organisation, and spreadsheet exports for leadership.
Proven in: Asori reports
Server-side checks on sensitive actions, least-privilege scopes, database access rules tested in CI, strict security headers, audit trails and secrets kept off devices.
Proven in: Asori security
Signed builds, CI pipelines with release gates, store submissions, forced-update gates and test suites that exercise real devices and many viewports before release.
Proven in: Asori releases
How the capabilities connect
Read across a row to see where a capability is demonstrated. The Workers Guild System and the Global Platform are client work for The Church of Pentecost; Khaya Demo is an experiment.
| Capability | Workers Guildclient | Global Platformclient | Asori | Estorr | Oxie | Khaya Demoexperiment |
|---|---|---|---|---|---|---|
| Web platforms | — | — | — | |||
| Mobile product engineering | — | — | ||||
| Backend and cloud systems | — | |||||
| Multi-tenant architecture and permissions | — | — | ||||
| Content platforms and CMS | — | — | — | — | ||
| Realtime and messaging systems | — | — | — | — | ||
| Payments and money correctness | — | — | — | — | ||
| Messaging and notifications | — | — | — | |||
| Offline-tolerant workflows | — | — | — | |||
| Applied AI | — | — | — | — | ||
| Reporting and data | — | — | ||||
| Security-conscious product architecture | — | — | ||||
| Release engineering | — | — | — | |||
| Product UX and design systems | — | — |
Work with SomaMe