Your current filters are…
Deploying your Drupal site, Upgrading your Drupal Site, Scaling, Clustering and Monitoring it ... all topics Developers are often not involved with ...
"Some call this phenomenon devops, others agile system administration Truth is that agile techniques used in development have an impact on the way operations organizes it work. Similar, operations and sysadmins are becoming programmers because of the virtualization and automation trend where everything is managed through an API. So if you are a developer with a interest for system administration, or a sysadmin interested in development."
That's how DevopsDays 09 was announced last summer.
Devops tries to close the gap between Developers and Operations, with both technology and best practices.
We're trying to solve a business problem here.
The department of Mathematics, Operational research, Statistics and Information Systems (MOSI - http://mosi.vub.ac.be/) is honored to host the Drupal Developers day.
MOSI would like to host another small event and is looking for Drupal people and/or academic people who would like or are using Drupal in research & education.
Open source software development has illustrated how a self-organizing peer-evaluation system is capable of opening up to volunteers and non-professional contributors, while maintaining a high quality of development.
We open our meeting room (B0.036) to discuss and plan any academic initiative related to Drupal.
Please use the comments if you like to join the discussion, have suggestions, would like to lead a discussion, etc.
It will not go over all the jQuery methods and plugins, but will rather provide you with the tools and knowledge to find what you need, evaluate plugins on their quality and perhaps write your own.
Hopefully, you will leave this session knowing how to write, debug and optimize jQuery code to create lean and mean front-end application interactions and animations.
This presentation will be largely based on sessions by people like Paul Irish (http://twitter.com/paul_irish), adam j. sontag (http://twitter.com/ajpiano) and Rebecca Murphey (http://twitter.com/rmurphey), so if you've attended their every session, you probably know more than I do ;)
Learn how to get custom functionality using Drupal’s hook system, as well as how to extend or alter contributed module functionality.
Participants in this course will have used CCK, Views and Panels to create websites but have never built their own module. Participants will start writing a simple module and end up being able to create more complex modules, using Forms API, Node API, adhering coding standards and with an eye on testing, security and performance.
Site building experience with Drupal 6. Understanding of and experience with PHP.
* Exercise 1: The Kickstart Module
The bare bones of a module. Coding standards. Reference materials
* Exercise 2: Extending the custom module
Implement Node API
* Exercise 3: Configuration settings
Permissions, hook_menu., Form API. Using the API docs
* Module development best practices
* Exercise 4: Hook_theme
Making your module easily themeable. Best practices
* Exercise 5: Simple test
* Exercise 6: Recap and review
Views to code. Exercise to make a module from exported Views. (module review from start to finish)
How to learn more
* Developer best practices
* Exercise 7: Best practices for development. Site Audit checklist Doing a site check during development to ensure it's running its best
* Exercise 8: Drupal Performance Optimization checklist
Steps to enable caching and optimization of a Drupal installation
* Exercise 9: Troubleshooting Poor Drupal Performance
Looking at front end performance and queries within Drupal to identify and fix problems
* Conclusion and Q + A
By the end of the training you will…
How do I get the most out of Drupal? How does it all work? What sessions should I go to at? What about this community thing?
We want you to be part of Drupal! In this session, we'll cover some of the most common questions that come up when choosing Drupal and how to get started once you've made that choice. Helping users with widely varying experience get the most out of Drupal at Acquia has given us some insights about getting to know Drupal and how it can best work for you.
Drupal is more than code. We'll show you some of the online and offline structures, customs and practices that make Drupal so much more than a bunch of code: resources, user groups, discussions, equality, acceptance, meeting other Drupalistas, hallway/session/online etiquette, "What is a BOF anyway?", what we mean by "the more you give, the more you get back", and more.
Make the most of your time at the Drupal Developer Days. We'll suggest other sessions you should see to get more in-depth knowledge about topics we touch on in our session.
Some of the things we'll cover:
Intended audience: Newcomers to Drupal - decision makers, designers, coders, and all others! We will focus on how to be part of Drupal: how not to be shy, how to find others who share your interests, and how you can get and give the most in the community.
All sites with more than modest traffic needs caching. However, time based caching poses problems – too long caching times causes content to become stale, too short caching times means heavy loads on the server.
With Cache Actions (http://drupal.org/project/cache_...) and Rules (http://drupal.org/project/rules) you can empty selected cache bins in Panels, Views and Varnish when relevant events take place. Invalidate your cache when stuff happens and your site will respond immediately to new changes. This session is about how you can set this up on your site and how much caching actually matters for the responsiveness of your site.
You've have heard talking about Drupal, you've heard about the buzz, heck.. you even plan to attend a DrupalCamp? But you have almost no clue what this 'geeky'-CMS can do for you?
Attend this introductionary session and get a quick overview of Drupal, its history, its community, the power of extra modules and themes and even learn to convert an exisiting HTML site into a decent CMS using stuff like 'fields', 'content types', 'image styles'
After this session you will be ready to enroll into a professional drupal training class featured in a classroom near you.
Note: This presentation will be loosely based on following slides : http://www.slideshare.net/develo...
The hangovers from the Drupal 7 release parties have just disappeared, but it is already time to start thinking of Drupal 8.
Because Drupal 7 is such a drastic fracture with the past, it now becomes clear how outdated many "good old" Drupal core modules are.
Drupal 8 should deal with leftovers from that distance past and rapidly adapt to the ever changin world of web.
This session will philosophy, among others, about the need to get rid of modules like profile, forum and blog and the need to include HTML5 and exportable settings in Drupal 8.
More information about the session will be added later.
See also: http://groups.drupal.org/node/11...
by Kristof Orts
From mobile browsers to netbooks and tablets, users are visiting your sites from an increasing array of devices and browsers. Are your designs ready? Learn how to think beyond the desktop and craft beautiful designs that anticipate and respond to your users’ needs.
Fluid grids, flexible images, and media queries are the three technical ingredients for adaptive and responsive web design, but it also requires a different way of thinking. Rather than quarantining our content into disparate, device-specific experiences, we can use media queries to progressively enhance our work within different viewing contexts.
The future is mobile.
I would like to share our experimental idea to create fingerprints (http://drupal.org/project/finger...) from Drupal sites, in a readable XML format.
This can be helpful at debugging, providing support in the issue queue, setting up a watchdog for certain changes and at professional Drupal support.
I'd love to discuss our experience with this idea, the future of the project and if you have new ideas.
You can dream PHPtemplate, you're the best theming ninja in your village and you scream VIEWS before the client even asked you about this News overview?
But as it is with Drupal: a module nearly does exactly what your client needs for his requirements and that leaves you (or the client) with two options: accept it as it is, or let some PHP guru develop a custom module that fulfills all needs.
But did you know that just knowing the basics of module development can help you save the day? Or at least, in many occasions?
In this session I'll show you some very basic hooks of the Drupal API:
* Use hook_form_alter to:
- add/change elements of a form
- change ID's and classes of forms
- write your own field validations
* Use hook_menu_alter to:
- Rename menu items
- Override an existing function that is not themable
- Delete items (even tabs!) from the navigation
* Use hook_link_alter to change the goal of an existing link
* Use hook_node_load to insert/change elements in a node teaser.
* And more
This training will NOT learn you how to develop custom modules. But I hope to give you some basic insight into the power of the Drupal API. And by doing so, minimizing frustrations and development time on your next projects.
Even a theming ninja can't do without some good old programming.
The long awaited Droopy App Store unveiled. You'll learn why the store is needed, what it does, the business model that makes it work, its risks, its rewards. This presentation will be specially geared towards developers familiar with module, theme, distribution and feature development on Drupal.org.
This session is a *thought exercise* aimed at challenging your beliefs and celebrating the character of the Drupal community.
Rotten tomatoes may be thrown, but only if you pay me for a license, first.
by Stella Power
Drupal has a number of coding standards that all contributed Drupal modules and themes should be using. Instead of each developer coding in their own preferred style, they are asked to write all code according to the standards outlined in the document. This ensures that all of Drupal's code is written to a consistent standard, making it easier to understand and modify. Drupal also provides its own set of API functions, and as the drop is always moving, a large number of these API functions can change between major releases of Drupal. This can cause hassle for contributed module and theme maintainers as they need to upgrade their code for newer releases.
This session will focus on the new Coder module for Drupal 7, which is a merger of the Code Review and Deadwood modules. This is a useful developer tool which allows developers to ensure that their code meets the Drupal coding standards and can also identify common security coding issues. In addition to providing a set of tests to assist developers when upgrading their modules to newer versions of Drupal, with the addition of the Deadwood module (aka Coder Upgrade) it will now also upgrade your code for you! If you write or maintain Drupal code, you should be using this module.
This session will allow you to see both Coder Review and Coder Upgrade modules in action. We'll run reviews on a module and discuss some of the common styling problems that it can identify for you. We'll also show you how Coder Upgrade can assist you in upgrading your modules to Drupal 7 and, if we have time, how you can help improve Coder by submitting new rules. By the end of this session, attendees will have a good grounding in what the Coder module does and how they can use it to improve their modules and themes.
In the summer of 2010, we started working on a cardgame engine for Drupal to power a Facebook Drupal Card Game. We finished the game, but after evaluation, we decided not to release the code, as it is right now not usable as a general purpose game engine. You can check out the game at http://cardgame.modulecraft.com but we have postponed releasing the game enginge as we ran out of the budget. Even if the project is not publicly available, we learned a lot, and it opened some amazing possibilities.
Have you ever wondered how other Drupal development companies work? What tools they use? How they structure their projects? This session is about finding that out.
Representatives from Krimson, NodeOne, Nuvole, Pronovix and Wunderkraut will be there to answer your questions.
ThemeKey (http://drupal.org/project/themekey) allows you to define simple or sophisticated theme-switching rules which allow automatic selection of a theme depending on current path, taxonomy terms, language, node-type, and many, many other properties. It can also be easily extended to support additional properties exposed by other modules. In combination with Drupal's theme inheritance, you can easily achieve features like:
After a short introduction about ThemeKey, I'll demonstrate some solutions for real-world problems of site builders which could be solved by ThemeKey.
This session will go over the differences between solving a task in Drupal 6 Vs. Drupal 7, and how this change led to the rewrite of Organic groups module.
I will probably also show some pictures of Anteaters!
The ability to extend existing module in a clean way is what makes the difference between a project that's 80% done and one that's 100% done. This was true for Drupal 6 and is still true for Drupal 7.
While the techniques are similar, a lot of things have changed. Between the confusing new possibilities and the things that used to work but don't anymore, the first Drupal 7 project can be a challenge even for experienced Drupal 6 developers.
There are a lot of information available about the new features of Drupal 7. This session will instead focus on practical examples that are representative of real-life projects.
Thinking about turning Drupal development into a professional activity? Come to this session to hear people who have made the leap talk about their experience.
This will be the occasion to ask questions about everything from "how to get clients?" to "how much do you work?", and to get answers from people who have been there before.
I this session I'd like to show a module that allows the integration of Sharepoint content into your Drupal website.
Sharepoint -> Drupal integration has been a topic that we've seen popping up on several occasions , and therefore we've implemented a module that does just that.
The session will cover an introduction on how Sharepoint organizes and stores it's data , and how we map this to Drupal.
A real-life example will be shown.
Drupal Commerce, now in alpha4 is the successor of Ubercart, but it’s actually a module written from scratch. We’ll see together all the new features of it, all we’ll discuss about the available options for e-commerce in Drupal in the near future.
by Denes Lados
DITA Integration for Drupal is a module which provides various tools to handle a DITA documentation. It's integrated with the popular DITA Open Toolkit.
Main features are:
You can upload dita tasks/concepts/documents.
You can use graphmind to build a DITA map from your uploaded topics.
You can convert your dita documentations into xhtml or pdf2, or you
can download them in tar.gz
You can schedule your conversions, and have them run on cron, or run
them immediately with a simple command in command line.
Create relation tables in the map with Drupal's taxonomy
With the Simple Dita Forms submodule, you can build simple tasks and
concepts with a form.
With the DITA feeds plugin, you can add a directory, from where any
new DITA topics will be crawled.
In this session I'll explain the concept of this module and what were the biggest challenges implementing an
integration module for the DITA XML format.
drupal project page: http://drupal.org/project/dita
Lately, there was much ado about this thing called the Semantic Web. Dries Buytaert put the topic on the forefront in his DrupalConSF Keynote earlier this year.
But what is the Semantic Web? Why is it important? And what's Drupals' role in this? Krimson has been part of a research project
sponsored by IWT called Archipel (http://www.archipel-project.be). Our role in the project is to publish Linked Open data, stored in a shared repository, in a consistent fashion. This means leveraging typical tools found on the Semantic Web like SPARQL and RDF.
In this session, I will:
You can write drupal code, but how to share it with the community?
You hacked a module and fixed some bugs, but how to get it into the next release?
You know how to improve the user interface, now how to convince the module maintainer?
You like to help others, can write better documentation, help to translate the interface?
There are many ways you can contribute and every drop counts. And above all, it's fun!
Learn how to contribute, where to go, which the 'procedures' to follow and which tools to use.
Installation profiles were designed as a tool create distributions, but there are many other ways to use them. It is possible to build a regular Drupal project as an installation profile, making deployment and team collaboration a lot easier.
This session will be a hands-on demonstration of how to start a new Drupal website using code only, making it possible to work with a team without needing a central development database.
By now you all know that Drupal 7 is awesome, and you know why it's awesome.
You also know that one of those reasons is RDFa support.
What you might not know is that there's a RDFa standard for ecommerce called GoodRelations, and that it's pretty awesome by itself. You should.
- What is GoodRelations, what it does, and how it's used today by search engines.
and then when you realize that you need to have it, we'll cover:
- How to enable GoodRelations support for Drupal Commerce, how it works, what it does and does not do, and how it compares to competition (integration modules for Joomla, WordPress, Magento)
This session will be about the changes to views in the views 3.x development cycle.
Beside the big improvement of pluggable query backends(query from flickr etc.) views supports
a bunch of more features of sql and has some more internal features.
A short list of changes
If you're a developer faced with the task of estimating development work based on a very loose specifications (or not), this is the session for you, regardless of your experience level.
Almost all clients who approach you about a project want to know up front what the total cost will be. They hand you some loose notes and expect a fixed number of hours or price. To many this presents an impossible task. What is often forgotten is that an exact estimate isn’t expected. What you need to produce is one that is accurate enough for the client to decide.
In this talk I will introduce an estimation method for these situations. Using this method you're able to tell a client early on the expected size of a project and making decisions regarding the scope and focus of the project.
In this session you will learn how to
Previously seen at DrupalCamp Austin and DrupalCon Copenhagen – now it's time for Brussels!
Said about the session
Presented by Jakob Persson, co-founder and lead solution architect at NodeOne.
by Ronald Ashri
One of the biggest "behind the scenes" changes in Drupal 7 is the shift from nodes as the "atom" of Drupal to entities. All the main aspects of Drupal, such as nodes, comments, taxonomy terms and users are now entities and there is a growing set of modules that allow you to manipulate entities. In addition, creating your own entities can bring great benefits to Drupal development since they can both benefit from being instantly fieldable but also as lightweight in terms of UI and/or additional functions as you need them to be.
However, as entities are a new element best practices have yet to spread widely. The aim of this session is to investigate how entities are being used so far in contrib modules and try to identify (with your help!) what are the emerging patterns.
4th–6th February 2011