Make our project websites work properly on phones and tablets, and bring every one of them up to the organisation's minimum IT security requirements.- Our reading of the brief handed to Milleniance at the start of the engagement
The centre ran several websites for its programmes. Two were static pages with no content management system, another was not built for mobile or tablet screens, and they did not share a design, menu or platform. Its digital resource centre could only be reached from the office network, and useful capacity-building content sat on a separate portal.
At the same time, the websites had to meet the security requirements set by the United Nations Secretariat. That meant defences against cross-site scripting and SQL injection, controlled access to back-end systems, protected logins, and audit logging - all written down as requirements the finished sites would be tested against.
The security controls were listed in the requirements up front, so they were built in as acceptance criteria rather than bolted on at the end. Delivery was split into two dated milestones: first, conversion of the static sites to the CMS with responsive layouts and the security controls in place; second, integration of the external content, the resource centre going online and hands-on training for staff.
Every requirement was tested across all the sites before sign-off. Staff who would manage the sites afterwards received training at the centre, along with manuals illustrated with screenshots and diagrams, so day-to-day content work did not depend on a developer.
"If your organisation's websites are still a set of separately built pages, a shared CMS and a written security baseline will save more time than another redesign."
No sales deck, no discovery call with someone who hands you off afterwards. We look at your websites, your security requirements and how your team publishes content today. We respond within one business day.
Talk to a Senior Web Architect →