* Bootstrapping components with Drupal.behaviors
* Interaction with delegates
* Managing events
* Talking back home
* Making it themable and translatable
* 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
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.
You should be familiar with how a website is structured and know basic Apache configuration. Being familiar with HTTP is a bonus.
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.
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.
* 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.
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.
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.
Drupal theming isnt that hard (at first) - but after the first sweet feeling of geek stardom, the truth comes sneaking...
Some elements in a drupal sit can be a little tricky, unless you are willing to dig a bit deeper and get a little dirty.
so this one is all about pimping the crap outta your site, and in the process build up a libary of pure awesomeness
To show some of the possibilities that are hiding just under the hood of drupal, and a couple of approaches to sex up your drupal life, and give the universal answer to the question that more than once have been shouted out:
"How the F!"#" do i get this menu to look like that the designer gave me - why cant we just use plain text menus and be done!"
and go from : "aaaargh I hate designer I hate drupal I aaaaaargh" to
"woohoo Drupal is the sweatest system in the world - wheres Dries I wanna kiss that guy, and by beers for all in the community"
basic css ,html, some php & basic drupal theming knowledge, and not to offended by the words that start with F.
Usability is a big factor in the success of a website or a web
application. With some usability knowledge developers can improve their
I will show what changes have been made (and will be) to Simplenews and
Header Image modules (the modules I maintain). Along the way I will share
my thoughts and considerations regarding contributed module usability.
Usabiltiy is no rocket science, just applied common sense.
* What is usability and why do we need it
* Common mistakes
* Simplenews and Header Image usability past, present and future
To make module developers, users and decisionmakers aware of usability
aspects of module development.
* Common sense
* Books: Don't make me think by Steve Krug
Report as inappropriate:
Accessibility should not be considered an option or an add-on. It is the responsibility of the entire team, from the designer, to the coder, to the writer, to the themer, and even to the business development team.
Fortunately, Drupal has a solid foundation for coding standards and separating its data, logic, and presentation separate from each other. This has greatly contributed to the ease in which to make a Drupal site accessible. But is it enough and could it be better?
Link to the slide:
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.
* Several scenarios how to make administration easier
* RootCandy theme/module project
--* RootCandy for developers
--* RootCandy for users
* Available modules that can improve administration
By the end of this session, attendees will see more possibilities in improving admin section and benefits of making admin section userfriendlier.
The formal user tests at the University of Minnesota and Baltimore have got quite some attention. They also had a common bottom line: Drupal is quite hard to get into for novice users.
We want to improve this. But how can we make sure we really tackle the major issues? And how do we find out if improvements are really improvements?
Repeated testing is the answer. Make sure to find out how the user experiences Drupal for our own attitude cannot be but biased. How is someone who is not accustomed to the workflow and UI able to perform a given task?
And how to make user testing fun? I'll try to depict how this can be done utilizing the
Usability Testing Suite (UTS).
Find a way to make user testing an asset to Drupal. Just like code testing has got a key role in Code Quality.
The talk will have an ensuing BoF to discuss the further steps in user testing. If we could come up with a plan that feels feasible, this would be wonderful.
Usability Testing Suite
In dev state,
maintained by boombatower
Web design is hard. I am not at all a designer or graphic magician, but would like to see great themes on my Drupal sites, so I am continuously on the lookout for great templates to adapt to Drupal. Whoever professional you ask will tell you that building a website on an existing template is a bad idea and of course you should architect the look and feel and interaction of the website for the specific need at hand. Unfortunately lots of people just lack the professional resources. And starting from an existing template still allows you to tweak it further (if the license grants you to do so).
Therefore this session is about picking a template (the Modern World template from Solucija) and converting it to a fully functional Drupal 6 theme with blocks, menus, a screenshot for the theme selector and all live from the ground up in 45 minutes, instructions included. Make sure to drink some coffee so you can grok every part of this quick flowing live tutorial!
* Starting from template vs. custom research/process/architecture/design
* Template licensing, what should you consider
* Downloading and starting off with the theme
* Several steps, while the theme will be horribly broken, but we keep going
* A glamourous end result
* More on licensing, how to contribute the theme to drupal.org or elsewhere if drupal.org is not applicable
Attendees will leave with a recipe to port existing templates to Drupal 6 and hopefully even contributing them to Drupal.org (but this last item will not be obligatory).
Also check out my blog post: http://hojtsy.hu/blog/2008-jul-22/i-will-teach-you-port-templates-drupal...
Version 2 of the popular Views module was rewritten from scratch to make it even more flexible and powerful. With more flexibility comes more complexity and quite some time was spent working out a user interface that could expose all these powerful features without becoming an enormous scrolling form. This session retraces the process that led to the current interface, showcasing how developers and interface designers worked together to find a working solution to a complex problem.
- Views1 to Views 2: adding multiple dimensions of infinite flexibility.
- Concepts, wireframes, and other false starts.
- Two basic concepts: sentences and summaries.
- The end result. Do you like it? What could be better? How can we translate the good bits to other use cases?
First of all, this presentation wants to provide an overview of the design process for this particular user interface. The larger picture is that the web is rapidly evolving from websites into web applications. The Drupal UI toolkit has to be extended with smarter and more complex form widgets to build the interfaces for these web apps. Ideally the good stuff in Views 2 can find it's way into other Drupal applications as well.
Bring your own feedback on the new interface! What do you like, what do you think could be improved?