ACAPS
Drupal development on the website of ACAPS, the independent authority supervising Morocco's insurance and social welfare sectors — a regulatory portal serving professionals, supervised entities and the public.
- Redesign and migration from Drupal 7 to Drupal 10
- Portal for an independent regulatory authority
- Regulatory texts, circulars and supervised-entity registers
- Arabic, French and English
The site
ACAPS — the Autorité de Contrôle des Assurances et de la Prévoyance Sociale — is the independent authority that regulates Morocco's insurance and social welfare sectors. It supervises insurance and reinsurance companies, their distribution networks, and social welfare bodies.
Its website is where the authority publishes regulation and where the sector comes to comply with it. I worked on it as part of the team at FORNET.
What a regulator's site has to do
A regulatory portal is not a brochure. It's a reference system that people use to do their jobs, and it carries legal weight.
Regulatory content needs structure and history. Circulars, decisions and regulatory texts have dates of effect, references, and relationships to the texts they amend or replace. Modelling that as real entities rather than uploaded PDFs is the difference between a site people can search and a document dump.
Registers have to be accurate and findable. Supervised entities — companies, intermediaries, welfare bodies — form directories that the public and professionals both consult. That means filterable listings that stay fast as the data grows.
Two audiences, one site. A professional needs the regulatory corpus; a member of the public wants to check whether an intermediary is authorised or understand their rights. The information architecture has to serve both without either getting lost.
Publishing is controlled. When a published text is a regulatory act, the editorial workflow has to reflect who approves what, and the audit trail matters.
Where I spent the time
- Content modelling for regulatory texts, circulars and entity registers
- Filterable, performant listings over growing datasets
- Multilingual configuration across content, interface and configuration
- Editorial workflows and role-based permissions
- Custom modules for requirements no contributed module covered
- Performance work: caching strategy and query optimisation
Note
Agency work at FORNET, delivered by a team. This page describes the nature of the work and the parts I contributed to — not sole authorship, and nothing about the client's internal systems, data or infrastructure.