# Building Digital Mapema on the current platform

## What digitalmapema.com runs on today

The public site points to **Rocket LMS v2**, a Laravel learning management script sold on CodeCanyon, with its Theme and Landing Page Builder add-on. This was read from the page's public assets, not confirmed against the server:

- Laravel CSRF token in the page head
- uploads under `/store/1/`
- theme and builder assets under `/assets/design_1/` and `/assets/design_1/landing_builder/`
- jQuery, Swiper and Plyr on the front end
- footer still reads "Creative Startup Academy", the builder's demo text

Confirm on the server: the Rocket LMS version, installed plugins, hosting location, PHP and MySQL versions, and the licence type.

## What Rocket LMS provides (vendor listing, v2.2, May 2026)

| Area | Detail |
| --- | --- |
| Stack | Laravel, PHP 8.1, MySQL 5.7+ or MariaDB 10.2+, ionCube loader; self-hosted, full source, some licence files encrypted |
| Licence | Regular licence where end users are not charged; Extended licence where they are |
| Roles | Students, instructors, organisations, staff with permissions. No parent or caregiver role |
| Learning | Courses, certificates, badges. Quizzes, forums, store, reward points and leaderboard are plugins |
| Payments | PayPal, Razorpay, PayU; Paystack and Flutterwave in a paid pack; no M-Pesa |
| API | No documented core REST API; mobile app sold separately |

## Role in the Digital Mapema platform

Rocket LMS carries the **teacher kit** and **teacher training** only. It does not carry the family channel, safeguarding desk, consent registry or evidence console.

| Requirement | On Rocket LMS | How |
| --- | --- | --- |
| TK-1 weekly pack | Yes | One course per season; one lesson per week; A4 PDFs as downloads |
| TK-2 offline | Partly | PDFs download for offline use; offline delivery logging needs TK-3 by SMS |
| TK-3 delivery log | Partly | Lesson completion in the LMS; SMS code fallback through the gateway |
| TK-4 protocol card | Yes | Attached to every lesson; referral goes to the safeguarding desk, never stored in the LMS |
| TK-5 training | Yes | Training course with quiz plugin and certificate |
| Teacher and focal point accounts | Yes | Instructor or student roles renamed; staff accounts for programme team |

## Configuration for children's safety

Turn these off or remove them before any school uses the platform:

1. Public self-registration. Teachers are invited by the programme team.
2. Store, product pages, cart and payment gateways.
3. Reward points, leaderboards and any public ranking.
4. Forums and any user-to-user messaging.
5. Demo testimonials, demo instructors and the "Creative Startup Academy" footer text.
6. Earnings claims on the landing page.
7. Any upload or field that could hold a child's name, photo or voice.

Set these:

1. Hosting in Kenya, or a serving copy in Kenya.
2. HTTPS everywhere, strong admin passwords and two-factor sign-in for staff.
3. Daily encrypted backups held in Kenya.
4. Brand tokens from `02-brand/tokens/tokens.css`; Fredoka and Andika from Google Fonts.
5. A separate subdomain or section for the children's programme, kept apart from the creator academy courses.

## Services to build beside it

| Service | Proposed build on | Covers |
| --- | --- | --- |
| Family channel | RapidPro with a Kenyan SMS and USSD gateway | FC-1 to FC-4 for the pilot; FC-5 and FC-6 for scale |
| Consent registry and surveys | Small registry service plus KoboToolbox for offline survey collection | EC-1 to EC-5 |
| Safeguarding desk | New, minimal, locked-down service | SD-1 to SD-5 |
| Studio workflow | New service or a configured workflow tool | ST-1 to ST-4 |

Integration: with no documented core API, connect these through a custom Laravel module (events on lesson completion, teacher roster export). Keep referral and consent data out of the LMS database entirely.

## Build order for the pilot

1. Server audit and the safety configuration above.
2. Teacher kit course structure with one sample lesson from the lesson card template.
3. Family channel flows for opt-in, the weekly challenge and the DONE, HELP and STOP keywords.
4. Consent registry and baseline survey.
5. Safeguarding desk with vetting register and referral log.
6. Integration module for delivery logs and the dosage view.
7. Security review before the first school goes live.

Full requirements: `05-backlog/requirements-backlog.csv`. Architecture: `01-docs/diagrams/platform-architecture.png`.