{"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\n On our laptop machines we use MS Project<\/a> for project management (how quaint!), Fireworks CS4<\/a> for mockups and early designs, Chrome<\/a> for design in the browser which is quite important with responsive websites. We use Komodo Edit<\/a> for code editing.<\/p>\n\n\n\n But everyone in the company<\/a>, even past members, has some effect because we’re all in this together, so a mention to Laurie, Barrie and Peter who taught us about tuning Apache for WP.<\/p>\n\n\n\n From a development perspective we’re all in one office, which helps. Each morning we have a team meeting where we catch up on the previous day’s events, what we’re doing today, and what blocks we have – others then help with blocks.<\/p>\n\n\n\n Code goes through the repository and can get peer-reviewed<\/strong> and for this project we tried out a degree of pair-programming that worked well.<\/p>\n\n\n\n Most of the plugins are our own: Events, Templates, Maps etc. We’re likely to start releasing some of these soon – we’ve kept out of the product marketplace for some time and sat on our IP because we know we did it wrong with Spectacu.la!<\/p>\n\n\n\n I don’t want to go into too much detail on the open source plugins used due to disclosure requirements, but the one worth noting is W3 Total Cache<\/a> for excellent performance and CDN management. We also use Gravity Forms<\/a> on most sites as it’s such a friendly end-user tool.<\/p>\n\n\n\n Lots and lots and lots of custom code was used. We tend to take on bigger projects as a rule, and that shows through on projects like this. The theme itself is a chunky 1.36MB and there aren’t many graphics in it! There’s a fair few includes, of course, but it’s still something of a beast.<\/p>\n\n\n\n Nothing too bad. The biggest problem was getting a handle on the real cost of building a project this complex<\/strong>. Because we tend to push the boundaries of what can be done WP wise, things often add up.<\/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
Who was on your team?<\/h3>\n\n\n\n
<\/figure>David Coveney<\/a> for project management.<\/li>
Workflow:<\/h3>\n\n\n\n
Plugins:<\/h3>\n\n\n\n
Custom Code:<\/h3>\n\n\n\n
Problems:<\/h3>\n\n\n\n
What did you learn?<\/h3>\n\n\n\n