Schedule

Writing documentation is probably one of the least favorite things developers do, but If you don't do it, you end up spending your time giving support on ridiculously simple issues instead. When we do documentation most of us spend hours and hours pasting screenshots into Google docs, then the theme or pictures change...

With Walkthrough.it you can add a documentation layer on top of your website. You can play tutorials that guide people through your site, step by step. It's like a GPS for your website. And the best part is: you can use community tutorials and easily share and collaborate on common scenarios.

In this session you will learn how you can record Walkthrough tutorials using Selenium IDE, an open source plugin for Firefox. How you can then edit them, share them and incorporate them into your website.

Drupal 8 is just around the corner. And while everyone is anxiously waiting for the release, contrib land is catching up and preparing all their precious modules for the newest Drupal version.

In this session we will explain what has changed in Display Suite and how we used the brand new drupal 8 api's to increase the quality of the Display Suite code. "The future of your display" comes with a new api. Examples will be shown and there will be time to discuss the api so we can improve it if needed.

We will also talk about the functional differences of the Drupal 8 version of Display Suite.

Some keywords: config, plugins, twig, form modes, ...

JavaScript frameworks are fancy new tools on a cutting edge of technology and if used properly, they could bring order to our code, increase productivity and, in some cases, make coding pretty fun!

This session will start by giving a small retrospection to JavaScript evolution since Netscape days.

Main focus will be on four popular JS frameworks, each one with specific philosophy: Backbone.js, Ember.js, Angular.js and Meteor. We will cover basic syntax, sample applications using each of frameworks and possibility to use them in Drupal 7.

Special attention will be made to Backbone.js which found it's way to Drupal 8 core and its possibility to interact with other frameworks.

Analyzing design and creating a CSS strategy before the coding is started is always a good practice. Sass and Compass can enable us to integrate into that process even more tightly making a clearer connection between the design concept and the implemented CSS.

This presentation will show how to adjust your thinking and some processes when using Sass and Compass to maximize long-term efficiency and minimize the time it takes to reconnect with the project after a period of inactivity or for a new themer to get into the project details.

This presentation is focused on introductory concepts of how to approach coding with Sass efficiently, but it doesn't explain the basic Sass syntax, how to install and configure Sass and Compass nor how they are used in particular Drupal themes.

Even though knowledge of basic Sass concepts is useful it isn't required to follow the presentation. A lot of insights about coding CSS efficiently can be gained even by those who don't have any Sass experience, and they can also use this presentation as a research about Sass, whether it could bring benefits to their work and whether they would like to learn more about it.

Well all know, many times the first 90 percent of the task takes 90 percent of the time, and despite of this, the remaining 10 percent usually takes an other 90 percent…Maybe we’ll agree that, this is not an ideal project lifecycle.

The power of Drupal comes from the lego-like capability of, which makes it possible to build really fancy results within a short time. In the first part of the projects mostly we’ll face with a very smiley customer, with a fast growing level of trust. When it comes to refine the rugged surface of the project, the smiley will evaporate with the missed deadline, and the suddenly overgrown project scope…

Using Agile Development contracting and working methods, we can manage the classical problem of the time/cost/scope triangle. In the last years we designed and implemented many successful B2B projects using scrum. We have realized that besides the PM method, it is crutial to grow and sustain a trustful environment within the team, and with the customers. Trust is a catalyst. If there is trust, we have everything we need to work efficiently, to have great results, moreover to keep the well-being of our employees and clients.

But what are the pillars of building trust?

In my presentation I would like to present this approach via real life examples. I’ll show you a working model about building trust by using agile techniques and of course, well, with Drupal.

The Drupal ecosystem alongside with other open source technologies provides a toolset that is extremely valuable in the process of product development.

The best approach I've found to product development in Drupal is to build a Minimum Viable Product (MVP) in the shortest possible time and get feedback from potential users early in that process. Drupal gives us everything to follow this path. High-quality contributed modules, the development framework through both the contrib space and Drupal core itself, and the extremely helpful community behind this technology are all leading to success.

I had the opportunity to experience this power while I developed a product as a side-project over the past couple of months. The end result is a Drupal distribution, successfully delivered to customers in SaaS model.

Come to this session to hear about how Drupal helped me and my partners to form our product ideas, what architectural decisions have been made, what solutions and techniques have been chosen in and outside of Drupal and all the lessons have been learned.

Once upon a time there were Netscape Composer and FTP. Then came Adobe Dreamweaver and CVS. Now you are working with Drupal and Git...

The following topics will be covered during the session, giving, hopefully, comforting answers to these questions:
- How can we safely deploy various data (code, configuration and content) to different environments using tools like Git, Features, Feeds, etc.?
- What solutions are known to handle development/staging/production environments well, so that you will not be braindead after a deploy?
- What questions can be raised about a project with one developer working in the ivory tower?
- What questions can be raised about a project with multiple developers in the bazaar? i.e. how to handle conflicts without headache?
- How can different versions of the same Drupal 7 site be managed in a trackable, reasonable and feasible way in the midst of 2013?
- What are the bigger areas of such development that needs your attention, and what tools are available?

Being involved in Drupal development is a passion. A passion of coding, finding bugs, thinking about the workflow - and since all of these are constantly changing, the best way to keep up with the rest of the world is being part of it. As a lead developer, I am at least partially responsible for the overall client satisfaction - but for the satisfaction of my fellow developers as well. While one can use Drupal as a one-man-business, and may even be successful with this approach, it seems there is not a single person having all the talents that even a moderately big website needs. This is the point when we do have to work in a team.

Working in a team may be frustrating, especially if one comes from the world of an ivory tower using proprietary software. Working with Drupal is more close to the bazaar model: we have so many building blocks (call them modules, themes, jQuery plugins and whatsoever) that we cannot even know all of them, at least not as a single person. Part of the frustration may come from the unfamiliar workflow of a team that shares the work. Drupal is not only scalable by the means of web server load, but also scalable by development manpower. By the way, is there any other web tool with more than a hundred thousand developers, eagerly waiting for your issues to be solved? ;)

I was sucked in by this enthusiastic attitude of the Drupal community. We, as a company, are trying to utilize this wonderful experience - not only in-house, but also as a part of international and local Drupal communities. This continuous integration of the whole Drupal community is such an experience that allows me to sleep well, since about 9 out of 10 Drupal-related questions that I submit to Google are already answered. I want to share this knowledge with you, especially about the workflow we are following that allows even my boss to sleep well.

...so you will continue to develop happily ever after.

There are many cases where constraints and limitations make decision making process hard. In this presentation we will deal with a typical problem that many organizations need to address - optimizing funds distribution according to a set of rules including votes from decision makers. To help them overcome this problem Drupal is used to build a solution that handles reviewing proposals (about how to spend funds), recording votes and computing the best fitting solution.

Data is handled using Drupal Views and standard content types while voting is done using fivestar voting system. Discrete optimization algorithm methods are used to calculate funds distribution to satisfy geo-location and categories percentage constraints, overall budget amount constraints and votes. We will also see what the basic concepts of discrete optimization method are, what kind of problems it can solve and how it can be integrated into Drupal.