01
What travels
Guide structures. Chapters. Translation and audio controls. Search and navigation. Map interactions. Campaign and podcast formats.
Existing frontend building blocksRomania × KenyaA conversation about preparedness
Preparedness
is local.
A good foundation
can be shared.
We built Fii Pregătit to help people in Romania prepare for emergencies. Its foundations can help a Kenyan team spend more time on what matters locally.
Explore what we built
Built around people.
Adapted with people.
Adapted with people.
A starting point for a Kenyan serviceLocal risks. Local knowledge. Local ownership.
01 / 07 ↓01 / The platform in useA practical route from
A practical route from
“What if?” to “What do I do?”
A website becomes useful when people can find a risk, understand the guidance and see how it applies to their own lives. Here is how Fii Pregătit connects those steps.
The flood guideThe right guidance,
The right guidance,
at the right stage.
One topic connects advice for before, during and after an emergency. Chapters help readers find a specific question. Language selection and audio, where recordings are available, give them other ways to engage.
What Kenya can reuse
See the Romanian example ↗The content structure and reading experience, with safety guidance authored or approved by Kenyan specialists.
English views of the Romanian platform, captured in October 2026.
02 / The value of a head startKeep the foundations.
Keep the foundations.
Make the service yours.
Many parts of a preparedness website solve the same problems across countries. The local decisions are where the service earns its relevance and trust.
→More effort on
More effort on
local knowledge.
Less repeated
product work.
This is an existing foundation for adaptation. A Kenyan implementation still needs its own content, data connections and operating team.
02
What belongs to Kenya
Priority risks and audiences. Approved advice. Languages and voices. Visual identity. Relevant services. The organisations people trust.
Locally led decisions and content03
What we develop together
Country configuration, local data connections and the publishing workflow. Additional formats or regional features where the pilot shows a need.
A jointly scoped implementation03 / An adaptation you can exploreThe structure can travel.
The structure can travel.
The answers come from here.
Take the flood guide. Its reading experience gives us a starting point. Each layer below shows a decision a Kenyan team would make before publishing.
Illustrative adaptation exercise
FLOOD PREPAREDNESSKenyan pilot
What do I need
at this stage?
BeforeDuringAfter
Reuse the reading structure
Keep clear sections and chapter navigation. Local specialists decide what each section should say for the selected community and its response arrangements.
Test with residents
Can someone find the relevant section without help?
Culture is part of the content.
Homes, livelihoods, household decisions, disability and access all affect what useful guidance looks like. Interviews and testing should shape the service from the beginning.
04 / Knowledge and trustThe people behind
The people behind
the platform matter.
Romania’s experience includes collaboration on audio, translations and guidance for young people. The transferable lesson is to involve people who understand the audience.
Expertise from
the audience.
Romania’s Association of the Blind contributes recordings of the guides, bringing specialist experience to audio access.
Guidance in
more languages.
IOM supports translation into minority and international languages, helping the platform address different audiences.
A voice that fits
the reader.
UNICEF Romania contributed to the first preparedness guide for teenagers, with communication adapted to young people.
Building on Kenyan knowledgeConnect people to the
Connect people to the
sources already here.
Kenya has existing information services to learn from and connect with. The opportunity is to help residents find relevant information and understand locally approved actions.
Kenya Meteorological DepartmentCounty forecasts↗National Drought Management AuthorityCounty drought bulletins↗
No partnership or data integration is implied. Sources, permissions and update responsibilities would be agreed locally.
05 / A practical route to adoptionStart with one community.
Start with one community.
Learn before expanding.
A focused pilot should be a complete, maintainable service. Each stage below ends with something a local team can review.
Proposed pilot1 community or county2 priority hazards6–10 approved guidesLanguages chosen locally
01UnderstandAgree the local brief
Identify the audience, priority hazards and existing guidance. Observe how people find information and which sources they trust.
What we leave with
A pilot brief, named local lead, content reviewers and an agreed language scope.
Ready to move on when
The local team agrees whose needs the first version will serve and what success will look like.
02AdaptBuild the first local journey
Configure the identity and content structures. Co-write priority guides. Review translations and any service data with local specialists.
What we leave with
A working prototype with approved pilot content and clear source attribution.
Ready to move on when
Reviewers approve the advice and a content owner takes responsibility for each published guide.
03TestWatch people use it
Test on residents’ own phones and connections. Ask them to find guidance, explain it in their own words and identify a feasible next action.
What we leave with
Observed results, a prioritised repair list and a revised pilot.
Ready to move on when
The team reviews findability, understanding and access against the targets agreed at kickoff.
04OperateHand over a service that can grow
Train editors, rehearse a correction and confirm support responsibilities. Expand to more audiences or locations when evidence supports it.
What we leave with
Deployment documentation, an editorial process, a review schedule and a support agreement.
Ready to move on when
The local team can update content and service information without relying on the original project team for every change.
Measure what matters
Can people find it? Can they understand it?
Can they act on it? Can the local team keep it current?
06 / Ownership beyond launchA local service.
A local service.
A shared foundation.
Kenyan partners should lead the content, identity and operational decisions. Common improvements can strengthen the foundation for Romania and future adopters.
Each implementation adds experience.
The foundation can improve together.
A named topic owner, specialist review, language checks and a process for corrections.
Deployment instructions, backups, data ownership and clear maintenance responsibilities.
Scope content production, adaptation, hosting and third-party services separately from ongoing support.
Agree how teams contribute useful component changes while keeping local content under local control.
For the technical teamWhat is ready to reuse, and what needs work?
The inspected frontend uses Next.js, React and TypeScript, with reusable content views and API clients. It has multilingual infrastructure, guide audio, map interactions and search and chat connections.
Adaptation work
Extract Romanian defaults into country configuration. Replace branding, map settings, contact information and service endpoints. Provide compatible content and media services.
Validate separately
Backend portability, publishing approvals, reuse rights, service costs, accessibility and security. A complete offline or multi-country distribution package has not been verified.
Optional extensions
Regional browsing, print or offline formats and additional channels should follow pilot evidence. AI requires local sources and evaluation before inclusion.
What would preparedness
look like for your community?
Let’s choose the first audience, the first risks and the people who should shape the service. Then we can turn an existing foundation into a concrete local pilot.
01Who should we serve first?
02Which risks matter most?
03Who will own and review the guidance?