Case study 01 / 08 · Public sector · E-government
SERVICES PUBLICS
The national portal for administrative procedures and non-tax revenue collection: user accounts with OTP, declarations with supporting documents, online payments.
Live≈ 900 commits
https://services-publics.cm/services/publics

01
Context
Administrative procedures and non-tax revenue collection span many ministries. SERVICES PUBLICS, a Ministry of Finance platform, brings them into a single portal where users create an account, build their file and pay their fees online.
02
My contribution
- Lead developer of the front office and back office — main contributor, with about 90% of the roughly 900 commits since 2023.
- End-to-end user journey: sign-up, OTP authentication, service catalogue, declarations with supporting documents, online or bank payment.
- Server-side rendering (SSR) for a fast first paint and good search visibility.
03
Architecture
BrowserVue 3 + Inertia, server-side rendered
RoutesSeparate areas: public, signed-in user, authentication, payments
Business logicSingle-responsibility Action classes · middleware for authentication, logging and upload checks
ServicesOnline and bank payment · document storage · real-time notifications
Key decision
Keep business logic in Action classes rather than controllers, so it can be tested and reused across user journeys.
04
Quality & evidence
- Commits since 2023
- ≈ 900
- Environments: test, pre-production, production
- 3
- Containerised environments
- Docker
05
Outcome
In production at services-publics.cm.