End-user

Overview

A panel discussion, that walks through the countries in the region and makes a short sum up of the current community status: the events that are being organized, the localized resources, the member bases and the events that will be hold in the near future.

Agenda

Goals

Get an overview of the "state of Drupal" in Central Europe. Open a dialog between the different communities that might lead to concerted efforts to grow Drupal.

Resources

An interest in growing Drupal.

If you are interested in being part of this panel, please send me a message using my contact form.

Overview

Everytime I work on a drupal based project, I am thinking about users how they are going to add content, set up taxonomy, maintain site and perform other tasks without getting lost on their site. This session will try to showcase best practices in admin interface and I will try to show where rootcandy (http://drupal.org/project/rootcandy) project is at the moment and where it is heading.

Agenda

* Several scenarios how to make administration easier
--* TBC
* RootCandy theme/module project
--* RootCandy for developers
--* RootCandy for users
* Available modules that can improve administration

Goals

By the end of this session, attendees will see more possibilities in improving admin section and benefits of making admin section userfriendlier.

Recap of the conference, farewell until the next Drupalcon.

Overview

There are numerous tools to help you translate the interface and content of your Drupal websites, and there are obviously (still) missing items in the implementation. This session will show off Drupal 6's capabilities and the latest developments with contributed modules, such as i18n module and l10n_client.

Agenda

* What do you need vs. what Drupal does
* How to get closer the two with core features and contributed modules
* Translating the interface live with l10n_client, contributing to an l10n_server
* Content translation, listing, filtering and administration
* What's missing, and where projects are going

Goals

I intend to provide you with an understanding on where Drupal core and the contributed modules fit with your needs and goals, and where should you still expect some custom coding required for your top-notch multilanguage site.

Some 40 Indymedia sites worldwide are now using Drupal, with different approaches to solve some of the general and specific requirements of their sites and collectives.
Other collectives are currently migrating their sites from other CMSs to Drupal.

Agenda:
* exchange ideas and updates face-to-face, sharing what's done
* Discuss and develop the survey
* discuss ideas for a basic install profile

http://docs.indymedia.org/view/Devel/ImcDrupalDevUsingList
http://docs.indymedia.org/view/Devel/ImcDrupalDevModules#How_IMCs_use_Dr...

This is a BoF for librarians and library technologists.

Agenda

* What libraries need from Drupal
* What libraries and librarians bring to Drupal
* Version migration issues and challenges
* Integrating with library systems

Fleshing out the plans is here: http://groups.drupal.org/node/12972

Looking for co-hosts!

example:
- do a card sort on the admin categories
- discuss the different 'dashboard' approaches people already use
- choose 2 options we want to compare / test

another example:
- let's pick a nice chunk of core interface text: labels, descriptions, help
- rework them for clarity, consistency and brevity.

BoF Usability Sprint Day 2

build prototypes: on paper, in photoshop and/or code
or: further work on interface copy, start documenting the copywriting guidelines we find.

BoF Usability Sprint Day 3

Test conceptcode with the Usability Testing Suite
Or work on concept some more, take it to the Code Sprint.
or: create patch for interface copy and start the guidelines handbook page on drupal.org

Fleshing out the plans is here: http://groups.drupal.org/node/12972

Looking for co-hosts!

example:
- do a card sort on the admin categories
- discuss the different 'dashboard' approaches people already use
- choose 2 options we want to compare / test

another example:
- let's pick a nice chunk of core interface text: labels, descriptions, help
- rework them for clarity, consistency and brevity.

BoF Usability Sprint Day 2

build prototypes: on paper, in photoshop and/or code
or: further work on interface copy, start documenting the copywriting guidelines we find.

Fleshing out the plans is here: http://groups.drupal.org/node/12972

BoF Usability Sprint Day 1

* zoom in on 1 or 2 issues we already decided upon before the conference
(redo admin categories, modules page, permissions page…)
* bring your ideas and proposals
* discuss the options, decide on 1 or 2 things we can work on.

example:
- do a card sort on the admin categories
- discuss the different 'dashboard' approaches people already use
- choose 2 options we want to compare / test

another example:
- let's pick a nice chunk of core interface text: labels, descriptions, help
- rework them for clarity, consistency and brevity.

Overview

This session, run by the authors of Organic Groups and Domain Access, will give an introduction to the workings of Drupal's node access system.

Agenda

* What is Node Access?
* How does it work?
* What modules provide node access?
* Exploring the current API
** Enabling node access
** Defining access realms
** Defining access grants
** hook_node_access_records()
** hook_node_grants()
** db_rewrite_sql()
** Changes from D5 to D6
* Common problems and issues
* Best practices for using node access

Goals

New users should come away with an understanding of the features and limitations of the node access system. Programmers should come away with the ability to write a node access module, using the existing API. Everyone should come away thinking about how to make the system better.

Resources

See the node acccess example module for background.