Moon under Water is a website about good beer in great places, a collection of places and events to visit. Instead of reading a number of blogs, adding events to my calendar and book marking websites about places I could visit when I'm in the area, the site pulls in feeds from a number of sites. Where appropriate the nodes have dates and geo-locations to display them on maps and event listings.
But it's not only a tool for travelling to solve the question where to go when in London/Berlin/etc but also a place to try out OpenLayers, feeds and more in Drupal 7.
OpenLayers is currently still in alpha1 and the dev version works fine for what I need so far. (The latest dev version form 6 August somehow lost a save button, but I suppose that will be fixed.) However, I haven't yet fixed mapping geo-locations from feeds to OpenLayers. Using OpenLayers with Views 3 seem to work best with WTK, but the feeds I'm pulling offers geo:rss...
Reminder to myself: It is worth the effort of installing Drupal straight away in the language that the admin users later will be using. Even if you can change the default language straight away after installation it still leads to a weird mix of some modules taking the default language from what was default during installation and some of what currently is default.
And while it might be cumbersome for me to come up with the right words in other languages in menus, terms etc - it is those admins and editors who will spend much more time using the site than me in future.
For languages like Dutch, Spanish or French with more than 99% of core translated - there is a pretty good starting point. However, the Swahili and Creole translations which I just checked for some projects are still below 1%.
However - as others have pointed out before - while the installer gives instructions where to get the po-files to install Drupal 6 in another language, it doesn't explain...
I've just spend a day in Berlin at the Drupal Design Camp - a day packed with sessions on rendering APIs, the Drupal Design Initiative, on how and why to use Drush and Aegir and more.
Actually there was very little actual design sessions, but talking to Morten revealed that the whole event should better be called "Frontend" instead Design - an approach that makes sense to me. "Frontend" would include not only design and theme and potentially also Usability but also issues like what themers require from a theme and what not, instead of separating coding and design as two completely different things that need to be dealt with for a good website.
tweets
-
· 27 weeks 3 days ago
ifrik: Date changed so that Commonwealth leaders don't have to choose between Queen's jubliee and #Rio+20. http://t.co/wjjrYhmW
-
· 32 weeks 3 days ago
ifrik: ♺ @ekes: Human mic MT like how article about simple tech .. subverts usual prob of power/hierarchy @hamishcampbell http://t.co/i9Ric927
-
· 34 weeks 1 day ago
ifrik: microRNA from food can survive digestion and alter gene regulation: the links http://t.co/BxVXtwm9 and http://t.co/LBQ93TJa
-
· 34 weeks 3 days ago
ifrik: thanks to #dcb2011 for great event, a proper lounge to meet people and constant supply of sandwiches instead of lunch-break queues
-
· 34 weeks 5 days ago
ifrik: #wysiwyg at #dcb2011 - still no way of getting rid of all the unnecessary formatting of texts copied out of Word or OpenOffice
-
· 34 weeks 6 days ago
ifrik: Decent navigation: Can you explain all your navigation in 3 sentences? Than it's good. #dcb11
-
· 34 weeks 6 days ago
ifrik: interesting talk from @linclark about structured data at #dcb11
