An NGO website needs to explain its work, publish useful resources and help people reach the responsible team. Zoha can build those public journeys with a CMS and defined editing roles. The scope should include content approvals, document access, appropriate enquiry fields, training and ownership, so the organization can keep the site accurate after handover.
Updated
On this page
Organize around the people using the information
Community members, partners, prospective staff and donors may arrive with different questions. Identify the information each audience needs and the action it should be able to take. A program description should explain the activity and the contact route rather than assume visitors know the organization's internal structure.
Start with the public information you can maintain. A large resource library or several language versions require ongoing ownership. Choose a structure that can remain useful as programs and staff change.
Give publishing a simple approval route
| Content | Decision to record |
|---|---|
| Programs | Who approves descriptions, status and contact details? |
| News | Who can publish and who reviews sensitive material? |
| Reports and resources | Which version is public and who maintains it? |
| Images and stories | What publication permissions and review apply? |
| Enquiries | Who receives the message and what information is necessary? |
Editing tools can make routine work easier, but they do not replace publication judgment. Agree roles for contributors, reviewers and administrators where needed. Sensitive internal records should not enter a public resource collection by default.
A hypothetical resource publishing journey
Imagine an organization sharing guidance documents with local partners. A staff member uploads an approved document, adds a short description and selects its audience and language. A reviewer checks the version before publication. Visitors can find it through a relevant topic page.
The process also needs a way to replace an outdated document without leaving conflicting versions across the site. This is an illustrative workflow. The right approval steps depend on the organization's own responsibilities and the material it publishes.
Make access and enquiries understandable
- Use descriptive document titles and explain format or language where useful.
- Test navigation, forms and important content on small screens.
- Provide clear labels and helpful feedback for incomplete enquiries.
- Avoid asking for sensitive personal stories through a general-purpose form.
- Explain what happens after a message is submitted.
If an application or referral process requires confidential case information, define a separate scope with the responsible team. A public website should not accidentally become a case-management system because additional upload fields were easy to add.
Handover should support staff changes
Agree ownership of the domain, hosting, content and administrative accounts. Include a practical editing guide and training using the organization's own content types. Staff should be able to publish an ordinary update and understand when another reviewer is needed.
Record recurring charges, backup responsibilities and how support questions are raised. A final handover checklist helps when a communications officer or administrator changes. Keep future features separate from the initial release so the organization can maintain what it launches.