7. User needs!
Information in one place
Less confusion
Reduced complexity…
UCD & usability-testing
Webguidelines/WCAG
Accessibility and
build quality
Open data/content
Social media/webX.0
9. Open Standards/Open Source?
• Future proof flow of information
• Open code, less vendor lock-in,
sharing components and code within
government
Taking but also giving; re-use
instead of re-inventing…
10. Your CMS MUST be able to separate
Website API’s
(X)HTML CSS Javascript Widgets
structure presentation behaviour Feeds
Repository
Database
content
External
CMS sources
11. 13 departments who are
different (are they?)
Challenges
How to organize this?
Migration: 16 websites,
15 years of content …
Scope, automatic and
by hand... know what
you want and need.
Project Management
Agile/SCRUM, multi-
disciplinary teams.
Gives interaction and
insight.
12.
13.
14.
15.
16. Thank you!
g.berkouwer@minaz.nl
Ministry of General Affairs
The Netherlands
twitter.com/Geebee
Photo credits: Crayon: http://www.flickr.com/photos/rednut/ Binnenhof: http://www.flickr.com/photos/roberts87/
India bus: http://www.flickr.com/photos/cumbers/ Crowd: http://www.flickr.com/photos/redjar/ User: David Vignoni
Confusion: http://www.flickr.com/photos/circulating/ Hippo: Hippo Challenge: http://www.flickr.com/photos/foxypar4/