{"id":86,"date":"2012-07-10T15:00:27","date_gmt":"2012-07-10T13:00:27","guid":{"rendered":"https:\/\/wprealm.com\/?p=86"},"modified":"2019-01-03T18:54:33","modified_gmt":"2019-01-03T17:54:33","slug":"wordpress-in-action-cgiar-ngo","status":"publish","type":"post","link":"http:\/\/wprealm.local\/wordpress-in-action-cgiar-ngo\/","title":{"rendered":"WordPress In-Action: CGIAR NGO"},"content":{"rendered":"\n
CGIAR<\/a><\/p>\n\n\n\n The website is designed to act as both the main site for the CGIAR NGO<\/a>, and as a hub for the huge range of content made available by all the consortium members.<\/p>\n\n\n\n The brief was, in effect, this list:<\/p>\n\n\n\n There was, of course, a lot more to it than that and in the meetings that followed we realised that a good responsive design was a must<\/strong> – even if it can be a massive challenge on a complex site. We also knew that widgets had to work flexible<\/strong> – if a widget space was small, the widget should respond to that – responsive within responsive, if you see what I mean. That means the chances of a user putting a widget somewhere and messing up a page is pretty slim, so long as it’s one of our widgets, that is – some plugins have their own ideas!<\/p>\n\n\n\n\n\n\n\n Restrictions were largely budget related. This wasn’t an infinite pot, even though the requirements were challenging. Time was ultra-critical. The primary elements had to be ready for the content team to get to work in time to be ready for Rio+20<\/a> that is running as I type this.<\/p>\n\n\n\n Well, WordPress<\/a>, of course!<\/p>\n\n\n\n The rest of the stack is conventional enough LAMP<\/a>, but that’s the client’s area in this project.<\/p>\n\n\n\n We have our own suite of WP plugins that we use, but we recommend W3 Total Cache<\/a> for performance and CDN management, and WordPress SEO<\/a> by Joost de Valk for SEO<\/p>\n\n\n\nWhat is the website for?<\/h3>\n\n\n\n
The Brief:<\/h3>\n\n\n\n
Restrictions:<\/h3>\n\n\n\n
Software:<\/h3>\n\n\n\n