--Neu--- Mit bekannte Sponsoren und viel interesante Sessions !

The Design Initiatives main purpose is to build a new theme for Drupal 8 and as part of this initiative we are preparing a Design Brief. The brief will be part of a "Designers Toolkit" which also includes a set of wire-frames. The brief itself comprises of two parts - a set of documents outlining Drupal core output (to support and clarify the wire-frames) and a Use Case Brief. Its the last bit I want to talk about here and open up discussion on. In essence what should this use case be?

I'm hosting firstcongoappleton.org (Appleton, Wisconsin) using shared hosting offered by Time-Warner Business Class. The server runs FreeBSD. We have about 1,000 anonymous users per month. Max logged-in load is about 3 users. I have shell access, so can run Drush, which is definitely a plus. The systems is plenty responsive for our needs, and the admin interface is powerful. The main issue we're having - and it's almost a show-stopper - is that Drupal runs out of memory at around 37 MB. Clearing cache after updating core, contrib, etc. almost always results in WSOD. TWBC have provided this service to us at no cost as part of our Internet service. I would be interested in hearing about low-cost hosting options (<= 200ドル per year) that offer more working memory for Drupal processes.

The 2. European Design Camp is coming to berlin this sommer

more info will follow late may

After months of tinkering with our Drupal distro and the custom theme to go with it, I finally got a chance this weekend to run a user test. The subject, Diana is not computer savvy. For example, a link or button has to look click-able (shouldn't it always!) for her to click it. When I asked her to create a blog post, she clicked the blog navigation link and wondered why there was no form for her to complete. She did not immediately see the "Create content" link. Diana uses a Mac and admits she is right brain dominant.

Building a Drupal project using git is different than building Drupal itself, and requires its own workflow. I've been kicking ideas back and forth with Sam Boyer lately about how to make this process take advantage of all the Git power, but also be newbie-safe and as frictionless as possible. I think what we've come up with is pretty good: there's even code written! The process I am going to explain allows the following:

• Git-based updates for Drupal core and contrib
• The ability to patch/tweak core/contrib without the complexity of vendor-branches
• Portability for local development or Git-based deployment
• Unrestrained custom development: feature branches, tags, multiple repos
• Safe patterns that minimize conflicts and provide a clear resolution process

Pretty cool, eh? Expect a larger manifesto post from Sam in the near future, but for now here's where we are heading.

We did it! Auditing phase now over.

A Drupal.org content audit will help us determine what we content have, where it is, and what work it needs (whether it's redundant, outdated or just not worthy). I haven't determined if this project should exclude Documentation book nodes, which obviously add a lot more nodes to the mix!

This content audit will be the first step towards a content strategy for Drupal.org.

The 2nd DrupalCamp Edinburgh will take place in the Informatics Forum, University of Edinburgh on 21st May.

The day will features presentations and discussions for Drupal users and developers of all levels.

Register

Register for DrupalCamp Edinburgh at http://dcedinburgh.drupalscotland.org/.

Sessions

Proposed sessions include: Git, Unit Testing, D7 Themeing, Mapping in OpenLayers, Drupal Commerce, Module Builder, Views and Contributing back to Drupal.

TBA

Product/Module pages are the entry point to the issue queue for many people and one of our opportunties to both increase the quality of the additions to the queue (bug reports and feature requests), to direct support queries appropriately, and also to recruit new contributors and recognise existing contributors - to that end they definitely qualify for some Prairie Initiative attention.