Designer, themer

UPDATE: Yes, I brought bribes! Themers, designers, coders, users: we want your feedback on our new book, "Front End Drupal." Bring your ideas, enter yourself in a draw for a copy of the book AND get a free flickr pro account. This BoF is on the THIRD FLOOR (stay on the lunch side and go up four levels) at 3PM TODAY (Friday).

Konstantin and Emma are writing a new book, "Front End Drupal" for Addison Wesley. We hope it will provide designers with a great dead-tree-media reference and inspiration on how to theme Drupal 6. We're very excited to be writing it! True to the open source ethos of, "release early, release often and listen to your customers" we'd like to give you a sneak peek at the book we're working on.

Come and give your two cents on our chapters to date, and throw some of your own ideas into the hat on what you think would make a great book!

PS By attending this session you will be eligible to WIN A FREE COPY of Front End Drupal! Yay! Winning! Free stuff!

Overview
This talk gives an introduction to Bazaar (bzr) - the distributed source code revision control system developed by Canonical Inc.

Agenda
In this session, Lenz will provide an overview about the general concepts of distributed source code revision control and how Bazaar (bzr) fits into this picture. The bzr terminology and most useful commands will be explained as well as examples on topics like:

• Creating a repository
• Adding files
• Editing files and commiting changes
• Branching
• Plugins and extensions, Interoperability with other SCM systems

Goals
Attendees will have a better understanding on how distributed revision control works in principle and how it can be utilized with Bazaar. The basic commands needed to get going will be covered, so users can get familiar with the concept by themselves.

Resources
Some basic understanding of source code revision control systems (e.g. CVS, Subversion) is probably required to make the most out of this session and to understand why Bazaar (or any other distributed revision control system) is superior to these.

Overview
It can be hard to look up from the daily work and se whats going on at the other side of the fence.

This will be a talk where themers can express their wishes for module developers and how it could be in ideal world, and vice versa
to give both parts a good understanding of the challenges that lies ahead in the day to day work.

It will be a round talk so come join and lets share our knowledge of both worlds

Agenda
* what makes a crappy module for a themer
* what makes a really cool module for a themer
* basic knowledge - what coders can expect a themer / designer knows - is it enough or?
* day to day problems in the theming world
* day to day problems in the coding world
* what "documentation" -cant you just read the code? its in line 1208

* come all together now... a even better tomorrow ;)

Goals
The goal of this session is to give module developers and theming-css geeks a better understanding of each others world.

Resources
some experience as a themer / module developer

Overview

Since the drupal world is constantly growing with more and more (non-)commercially oriented projects and people starting off, I thought it was time to come up with a platform that tries to connect projects (as well as staffing requests), people (drupalists) and knowledge. As of now I am in the final stage of launching this non-commercial platform, called drupaleo, as a beta version.

Agenda

Goals

Resources

clear mind required

A community effort to help a NGO get some ass-kicking internet presence

On the first weekend of October 2008, in only 2 days, the Drupal French Community will build a complete and live website for a selected NGO. All free. Free as in free beer, and free as in free speech.

A lot of the organizational details have been ironed out.

Though we have discussed a lot the question of "how the hell do we pull this off?" and have a detailed an action plan... there must be a million things we forgot.

Who should come?

So we are calling on all that have experience in organizing Codesprints/ Hackathons/ Mashpits and generally community events to join us and share their experience and thoughts.

What should come out of the session?

We would really like to hace constructive criticisms on our plan to adjust and augment it so we can put all the chances on our side to pull off this event.

Overview

What is 12seconds.tv?

12seconds lets you create and share short video updates with your friends and family.

Why Drupal for 12seconds?

Because it's a solid framework that just works well. Really.

What is the YUI?

The Yahoo User Interface (YUI) Library is a collection of JavaScript and CSS resources that make it easier to build richly interactive applications in web browsers.

Agenda

1. Using the YUI Grids
2. Compressing the CSS
3. ???
4. Q & A

Goals

• When building with the YUI it's important to know where to put it with all the other CSS files that Drupal spits out.
• Attendees ought to walk away knowing how to use and customise the YUI Grids for their Drupal sites.

Resources

1. http://developer.yahoo.com/yui/grids/

Overview

We'll discuss ways to develop reusable and flexible JavaScript components by leveraging JavaScript's full potential and using Drupal's lightweight JavaScript frameworks. We'll look at several JavaScript components and see how they were implemented and how they interact with each other.

Agenda

* The JavaScript widget skeleton
* Bootstrapping components with Drupal.behaviors
* Interaction with delegates
* Managing events
* Talking back home
* Making it themable and translatable

Goals

The session aims to create a better understanding of how JavaScript components can be built in a more modular and extensible way.

Resources

You should be familiar with JavaScript and jQuery.

SESSION OVERVIEW

This lecture-style session will present and discuss various approaches to improve front end performance. While server side performance has an impact on the speed websites are delivered, the vast par of loading time is spent on retrieving CSS, JavaScript and image files. For a truly zippy website, it is therefore vital to drastically lower the amount of time spent here. In his book “High performance websites”, Steve Souders discusses various ways to accomplish this. This session is based on that book but contains additional Drupal-related information and strategies.

AGENDA

* Anatomy of a web page
* Measuring the non-obvious and identifying bottlenecks
* The Hypertext transfer protocol
* Reducing HTTP requests
* Configuring Apache
* Additional optimizations
* Content delivery networks
* Related Drupal modules

GOALS

You should get a feeling for what “front end performance” actually means and where the main problems are located. You will also learn how to tackle these issues in a structured manner, measure the effects and get to know the basics of the foundation technology of the web, the Hypertext transfer protocol.

RESOURCES

You should be familiar with how a website is structured and know basic Apache configuration. Being familiar with HTTP is a bonus.

Overview

Analysts estimate that 75% of attacks against web servers enter at the application, not the network level. And as many as 15% of these attacks are due to poor coding practices. With the help of well known security firms, We'll discuss ways to secure your Drupal application.

Agenda

* See For Yourself - demonstrations of application attacks
* Case Study: Secrets to Securing a Social Network
* Key Habits of Secure Drupal Coding
* Vulnerability Detection to Remediation
* Security Resources for Drupal Applications
* Discussions

Goals

You will learn best practices you can employ right now to build secure Drupal Application code that meets security compliance standards and maintain customer confidence.

I want to open a discussion on how to use various components and sides of Drupal to enable us, Developers to improve usability in our projects. Le us discuss how to use Form Elements, Helper Libraries, Naming conventions and Insert Your Birght Idea Here to enable the community to improve Drupal's usability.

Overview
Improving usability for project Foo might make the same software horrible to use in project Bar. That is why we could look at improving usability in Drupal by not making Drupal core more usable. But by enabling the developers to make Their Drupal project more usable for Their users in Their specific cases: enabling the community to improve usability.

Looking at Drupal as a Framework (the CMF) gives us opportunities: We can improve usability by enabling Dan the Distro Builder to put together a Blog Install Profile that is very usable for Bob the Blogger.

Agenda
* Introduction on Usability in general: Why is it so hard to get right in Drupal?
* Short introduction on why this 'enable' route might work better then the oldfashioned 'make Drupal core more usable'.
* Open Discussion on ways to achieve this.
* Putting Money where Mouth is: create code, docs and projects after the outcome of the discussions. This should be the biggest part: we must avoid this becoming a vapourware project and start off with some Real Working Code and Good Resources.

Goals
Setting up and initial infrastructure that will help people who want to contribute to the usability of Drupal.
Get a message out about this initiative and to enthuse developers for this usability project.
And, in the very end: to allow you to build a perfect site for your specific users.

Resources
Please collect any nice code (form elements) nice ideas (the back of a beermat) or good designs (like That One CSS Trick to align forms) on your laptops or servers. So that we have some real working code and ideas to start off with.