WOW Plugins is a staple of WordCamp UK. Each year Michael Kimb Jones gives a rundown of plugins that he’s using that he finds useful and wants to share. It’s always a really popular presentation, partly because of the content and partly because Kimb is so good at presenting it. Kimb has just announced that he’s launching WOW Plugins, which will be an archive of all of the plugins he has covered each year (and will in the future I assume). I covered Kimb’s WOW Plugins talk on WPMU.org, but now you can follow them all on wowplugins.com. ∞
Today I’m travelling home from my third WordCamp since March. As I write, the other WP Realmers are having transportation troubles. Noel Tock is stranded at Heathrow Airport, while Tammie Lister and BuddyPress Core Developer Paul Gibbs are stuck on a broken-down train between Edinburgh and London. The British transportation system is its usual reliable self. The weather is grey, it’s threatening to rain; I, and no doubt all of us, are suffering from post-WordCamp blues.
Sitting on a rattling train, I became aware that it’s my week to write an editorial for WP Realm. No doubt Zé, who is my own personal editor, will be grumbling about this, but it’s my prerogative to tell the
wise grumpy old man to stfu (love you! 🙂 ). I thought I’d use my slot to reflect not only on WordCamp Edinburgh, but the series of WordCamps I’ve visited over the past four months and on WordCamps more generally.
Brian Krogsgard does a good job explaining some quirky things about Jetpack – ∞
WordCamp UK just got kicked of by Tony Scott here in Edinburgh. I say here because a bunch of us from WP Realm are actually here for WordCamp UK speaking and attending. So if you see me, Siobhan, Noel or Tammie do say hi.
We’ll do some proper coverage after, so for now you’ll have to follow the twitter hashtag #wcuk.
More and more contributor groups are making the move to make.wordpress.org, with the Polyglots and Core groups recently being moved to .org, and the brand new Events group making an appearance. If you want to get involved with contributing to WordPress, make.wordpress.org is place to get started. The contributor groups currently living there are Core, Plugins, UI, Accessibility, Themes, Polyglots, Systems, and Events.
Only a few more to make the move: I’m looking forward to seeing the Codex team and support finding their own room in the make.WordPress.org home.
If you want to learn more about contributing to WordPress, check out the page on the Codex.
What is the website for?
The website is designed to act as both the main site for the CGIAR NGO, and as a hub for the huge range of content made available by all the consortium members.
The brief was, in effect, this list:
- Web design based on the new branding guidelines
- Designs for page layouts, style elements, typography, graphical elements
- Unify and clearly present the information generated by the various Centres and CRPs
- Create a central entry point for visitors to find the main governing bodies of CGIAR
- Shift the emphasis from ‘the institution’ to ‘content and research’
- Increase the unity of the Centres, CRPs, Fund and Consortium Office through consistent design and branding
- Communicate clearly what CGIAR is and what it does
There was, of course, a lot more to it than that and [Read more…] about WordPress In-Action: CGIAR NGO
In today’s software, the default language is usually English, which in turn encourages people outside English speaking countries to start using that software as-is, even when localized versions exist. They simply stick with the English version, since they themselves have grown used to it and the localized version ends up feeling “strange” to them. It comes as no surprise that this applies to WordPress as well. Many site administrators, even though English is not their native language nor do they publish in English, still use the default, English version.
However, a localized version of WordPress has a lot more than meets the eye, i.e. the translation of strings, such as local settings and formatting, a few of which I will present here: