Drupal Lightning Talks

Have a neat tip, trick, hack, or solution for Drupal? We want to hear from you! You don't have to be a pro or an expert to share your favorite Drupal (or web) knowledge.

This series of five-minute lightning talks promises to be fun and informative for Drupalers of all levels. Learn more about this new event.

Lightning Talks

    1. Drupal & Bitcoin, jbrown
    2. Drupal 8 Console, jmolivas
    3. The Unforseen: A Healthy Attitude To Risk on Web Projects, steveparks
    4. Druphpet, k0teg
    5. Continuous Delivery as the Agile Successor, august1914
    6. #D8in8 initiative, stella
    7. Just a thought for discussion about security, amstercad
    8. Drupal as a Building Management System, idevit
Schedule info
Featured Event
Time slot: 
Thursday · 09:00-10:15
Auditorium · Wunderkraut


Organisations do so many seemingly sensible and smart things in the way they run their web projects that are actually counter productive. One of these things is the introduction of rules and practices in procurement and contracts, designed to address risk.

It gives a false feeling of reassurance at first, that quickly leads to chaos later. To make a web project succeed you need to embrace uncertainty and risk honestly and openly from the start.

k0teg’s picture

I'd like to give a lightning talk about the Druphpet project:
- https://github.com/alehkot/druphpet

It will be about setting of a Drupal-and-Windows-tuned Vagrant VM based on Puphpet (https://puphpet.com).
In addition to a time-lapsed demo I will tell about some pitfalls. and share tips and tricks.

Druphpet is used on a daily basis in a company I work to help projects newcomers be involved into the development as fast as possible.


August1914’s picture

Agile emerged a decade ago in response to the challenges of delivering software, and has gradually become the standard of practice today. Because of the success of Agile, and also because of the growing complexity of systems, the demands of delivering systems today has changed from the problems faced in 2004, when the Agile Manifesto was first published. Agile-mature teams today, many already practicing Continuous Integration, are developing capabilities in the relatively new practice of Continuous Delivery (CD), which emphasizes the early construction of delivery pipelines of constantly testable and deliverable software, even when feature incomplete, leading to new levels of productivity. CD practice is emerging as the successor to Agile.

Amstercad’s picture

I will not want to miss this discussion, and I'll to tell my friends! Agile causes stress, while CD is realistic stuff.

JohnAlbin’s picture

I was contemplating submitting a talk about Agile web dev, but I'm glad I didn't. This looks much more interesting!

Let's pretend you have built a wonderful e-commerce with Drupal and it's time to promote your items, which is one of the best way to do so?
If you are thinking of Google you are right. We have successfully used Google Shopping with our clients!

First of all you need to put the items into Google Merchant
You could do that in many ways: by hand, using views, using Google Shopping API or using Google Shopping Feed.

We have developed a module that produce a Google Shopping Feed with the items of your e-commerce, you don't have to bother with all the Google logic and rules, simply click a button!

We'd like to give a lightning talk about our module and its functionalities.
Then you can help us to make it even better ;)


Warning: It's a growing page so keep an eye on it!


Nicola Stocco
Studio Aqua

kvantomme’s picture

A lot of founders swear by NodeJS or Ruby to build their digital startup. We have chosen Drupal to build WalkHub, and that was the right choice not just because we are a Drupal consultancy company. In this lightening talk I will explain why.

WalkHub is an open SaaS Drupal distribution that you can use to build step by step tutorials, like the guided tours you can find on Facebook and Google maps.

Amstercad’s picture

There's nothing I'd like to stand up and speak about myself for five minutes, although I'd like to raise a discussion question about how Distributions are actually implemented. Why does it take so long for major Distributions like Panopoly, (which includes the OpenAtrium community as well) to update modules after security releases have been published? What can be done to push key security updates faster and with more reliability through the Distribution chain, and what should developers using these Distributions do?

Maybe someone else can speak on this topic that is more knowledgeable than me?

stella’s picture

As part of our efforts to enhance our Drupal 8 knowledge at Annertech, we ran an internal competition called #D8in8 (don't worry, you didn't miss it on Twitter; it wasn't trending). Basically, each Annertechie had eight weeks to “do something” with Drupal 8 – port a module, build a theme, migrate a database, anything. Come along to find out what we did, be inspired to run your own #D8in8 competition and let's get #D8in8 trending!

gabrielu’s picture

I would like to give a lightning talk about Drupal performance tuning. I wish to share my experience in optimising Drupal sites and servers hosting them.

idevit’s picture

As we all know Drupal is a great for building web platforms, now we can also manage real buildings with it. Not just facilitation management with modules as rooms, merci or Availability Calendars, but the actual building itself. This is done with a Building Information Model (BIM) in which all the geometry and relevant metadata for constructing the building is stored. We’ve been able to expose this information to Drupal and allowing to fully utilize its CMS capabilities.

This research initiated for the DDSS2014 (http://www.ddss.nl/) confrence in August 2014 at the Technical Univercity Eindhoven.
It contributes to the development of IFC based web applications in practice and demonstrates a way of linking machine to human readable data, thus making the data accessible to people without the knowledge of Computer Aided Design (CAD) software.

The next step is the mapping the building’s IFC data to the semantic web, Exposing the building’s by means of RDFx and SPARQL to search engines and other web systems.

We elaborate on several uses for this platform:
Applications for maintenance planning
Reuse of building materials
Management of buildings
Exploitation of large complexes of buildings

This way the world of the CMS meets 3D visualisation and real time monitoring.
Drupal will facilitate documents, discussions, calculations, calendars, workflows and other non geometry specific data. Other services are to exposed in the same user interface.

We envision this application as the central point where all data about the building is being stored, used, structured and updated, through the entire lifecycle from first concept to demolition and recycle.

This presentation will show the human perspective of this ongoing research at its most progressed state. The demo will focus on the Drupal parts of the code and how Backbone manages the front- and backend of the platform.

Dave Reid’s picture

There are three common problems I've encountered when working on a Drupal project:

* How do I know which patches have been applied to a project?
* How do I reliably know what patches are applied or not without manually checking every single one?
* How can I be reminded that I need to reapply a patch after downloading a module update?

The drush-patchfile extension aims to solve all of these questions and make maintaining a Drupal site that has patches applied an easier process. I'll show the basics and work through the simple workflows LIVE!