PUBLIC SECTOR — SOUTH SUDAN
Government Website Development in South Sudan
A government website is judged on whether a citizen can find a service, a notice, or a form without calling anyone. That is a harder standard than it sounds, and it is the one I build to.
Public sector websites fail in predictable ways. The navigation reflects the ministry's org chart instead of what citizens are looking for. Documents are uploaded as scans that cannot be searched. Notices stay online years after the deadline. Contact pages list a switchboard that nobody answers.
Those are not design preferences. They are the difference between a citizen finding a service and giving up. I build around the tasks people actually come to the site to complete.
What a public institution actually needs
- Service directories. What the institution does, who it serves, what documents are required, and where to go — written for a citizen, not for an internal circular.
- Public notices and tenders. Dated listings with closing dates, downloadable terms, and a status that changes automatically when a deadline passes.
- Document libraries. Legislation, regulations, forms, strategies, and reports, organised by year and type, with file sizes shown so people on metered data can decide before downloading.
- Contact and office information. Physical addresses, opening hours, named directorates, and working phone numbers with the +211 country code.
- Accessibility. Readable type, keyboard navigation, sufficient contrast, meaningful link text, and alt text on images. Public information should not require perfect eyesight.
- Bilingual content. English and Arabic, with correct right-to-left layout and reviewed official terminology.
Accessibility is not optional for public sites
When a ministry publishes a policy, a citizen with a visual impairment, a slow connection, or an old phone has the same right to read it as anyone else. I test for:
- Keyboard access. Every menu, form, and document link reachable without a mouse.
- Contrast and text size. Body text that stays legible at default browser settings and on low-quality screens.
- Semantic structure. One H1 per page, a logical heading order, and landmarks that a screen reader can navigate.
- Document accessibility. Text-based PDFs where possible, with descriptive file names instead of scan_0042.pdf.
- Language attributes. Correctly marked English and Arabic sections so screen readers switch pronunciation.
Security and continuity
A government site that is defaced or offline is a credibility problem beyond the website. The basics I insist on:
- HTTPS everywhere with a managed certificate and automatic renewal.
- Secure headers — content security policy, frame protection, and strict transport security.
- Least-privilege admin. Separate accounts per editor, no shared passwords, and two-factor authentication where the CMS supports it.
- Backups and rollback. A tested restore process, not just a backup that has never been opened.
- Patching. A written schedule for CMS, dependency, and server updates, with someone named as responsible.
- Handover documentation. Credentials, architecture, and recovery steps in writing, held by the institution rather than by a contractor.
Procurement and how to start
Public procurement in South Sudan usually means a formal request for quotations or a tender, and often a requirement for registered suppliers. I can work in three ways:
- Direct contract where the institution can engage a sole supplier within its thresholds.
- Subcontract to a registered prime contractor, with me supplying design, build, and technical documentation.
- Technical support to an existing supplier or in-house team that needs accessibility, performance, or security work done properly.
In every case you get a written scope, a fixed price, and a delivery schedule before work begins. I do not ask for a deposit against an unsigned scope.
What it costs
A focused institutional site — services, notices, documents, contact, bilingual — usually sits in the $900 to $2,500 band. A larger portal with multiple directorates, a document management system, and role-based publishing starts around $2,500 and rises with scope.
The packages page covers the bands in detail. Hosting, domain, and maintenance are quoted separately so the institution can see the recurring cost before committing.
Related pages
QUESTIONS
Frequently asked questions
- Do you have government clients in South Sudan?
- I am not going to pretend to a portfolio I do not have. My client work in South Sudan is the Galtia SynergyTech corporate site. I have not delivered a government contract, and I do not have public-sector references to offer. What I do have is a build approach that meets public-sector expectations on accessibility, security, and document management. If a tender requires prior government contracts, I will say so rather than waste your time.
- Can you work as a subcontractor to a prime contractor?
- Yes. That is often the realistic route for a ministry procurement. I can supply the technical design and build under another supplier's contract, with clear scope and handover documentation.
- How do you handle content in English and Arabic?
- Bilingual sites are built with proper right-to-left layout for Arabic and separate content per language, not machine translation pasted into the same template. Ministry names and official titles need review by your communications team, not by me.
- What about security and hosting?
- SSL everywhere, secure headers, least-privilege admin accounts, and a patching routine. Hosting location is a policy decision the institution has to make; I will set out the trade-offs between regional hosting and international edge hosting rather than decide for you.
- Can the site handle tenders and public notices?
- Yes. Notices get their own dated archive with closing dates, downloadable documents, and clear status labels so an expired tender is obvious rather than misleading.
Let's talk about your project
Tell me what you are building. I usually reply within one business day.