Over 700 people have given talks at BADCamp. You could be next.
Whether you're a veteran presenter or brand new to speaking at Drupal events – if you have an idea to propose, a lesson learned, tips and tricks that could help others, or something beautiful you want to reveal, we invite you to propose a session at BADCamp and share your knowledge with us.
We welcome those from all levels of expertise, background, gender, ethnicity, sexual identity, religion, age, and ability. Our community is diverse and we know that Drupal can benefit when everyone is included.
To submit a session fill out the Session Form.
Get your mind-breaking session proposal in soon - CFPs close Thursday, August 1 at midnight PT.
What if you don't need to decouple, to have some fun?
What if you could make your CSS and JS over 90% more lean, with just a slice of opinion?
What if the theming layer, is actually in your way?
What if someone is going to tell you about a cutting-edge native Drupal frontend alternative?
Would you come?
Each iteration of Drupal introduces new and exciting ways to manage content. However, the display of content is even more important along with the knowledge of how to convert a design to a theme. While we have all read about, watched and even worked with Twig to create new themes in Drupal 8, the way we work with Twig has changed.
Backdrop CMS is now nearly 5 years old. Since its first release on Jan 15th, 2015, what has changed?
Is Backdrop substantially easier to use than the Drupal it was forked from? Is it more affordable to support? Are the apis you know and love, still stable and functioning as they were? Is the community growing and healthy, or better yet, is it thriving?
Come see Backdrop CMS in action.
This session will demonstrate some of the kinds of things you can do with Backdrop core alone. We'll walk through site-building tasks that showcase some of the differences between Backdrop and Drupal, but mostly you'll see how similar the two projects are.
Backdrop CMS is the Drupal fork. It is a faster and less-complex version of Drupal 7 with more features you want, and fewer you don't.
This session will highlight the Backdrop Mission, it's intended audience, and it's guiding principles.
We'll explain the decision making process, introduce the Project Management Committee, and expand on how the project's direction is set by the needs of the whole community.
We'll cover topics like how we handle Security and Stability, and talk about how we're trying to decrease the cost of long-term website ownership.
I was a self-taught Google Analytics user. I thought I was getting by OK.
But, since working with professional analysts, I’ve seen how my data wasn’t as complete or accurate as I thought I was. And with bad data, it’s easy to tell the wrong story.
I’m here to level you up, and share best practices for setting up your Google Analytics accounts.
In this talk, we will:
provide recommendations on best practices for setting up your views, filters, and goals
Drupal has leveraged Composer to manage its internal dependencies since version 8.0; however, the way that Drupal has been using Composer is unconventional. Our unconventional hybrid approach has allowed a loose continuity between managing codebases using Drupal 7 methods while simultaneously enabling more modern Composer based workflows. However, the modern Composer based approach was incomplete and unofficial, requiring third-party tools and examples such as drupal-composer/drupal-project.
Just as the design process should seek to create something perfect and useful for the users and the client, so should the documentation. Documentation can be the first set of deliverables within an agency process to become outdated, stale, or redundant—mainly because they are dismissed as unimportant or left to a lackluster team to plod through begrudgingly. This doesn't need to be the case if we throw out what we think documentation means and seek to find more meaningful ways to integrate the process of documentation.
The first couple of months of a Drupal 8 project usually set the tone for the entire development process. Making bad decisions (or creating bad habits) in the first phase of a project should be avoided at all costs. Using his almost 20 years(!) of web development experience as a resource, Mike Anello (@ultimike) provides 11 practical recommendations to help ensure your project gets started (and launches) on the right foot. Mike’s tips are accessible and suitable for developers, designers, and project managers.
I’m JD and I have mental illness. I’m also not alone. Every year, roughly 20% of the US adult population deals with some form of mental illness, however that number is MUCH higher in the tech community.
Passion. It’s what drives us and excites us. It’s the thing that makes us strive to be better, and work harder day after day. It’s the energy that makes a project exciting and energizes the team to deliver something never seen before. It connects people, and makes them more than just co-workers, but more like family. What happens though when that passion begins to dwindle? The days become longer, the project gets hard and burnout begins to set in. How do we push to deliver what we set out to do? How we do keep focused? How do we keep that passion?
As projects become larger and more complex, so too do the teams required to make them great. When the requirements seem to grow beyond reach we all need to be superheroes to keep up. Staying siloed into our individual roles is no longer viable. To keep up we all need to develop our own super powers by learning skills outside our role to become cross-functional and succeed both individually and as a team.
By learning to be more cross-functional and expanding knowledge into the other disciplines required to build and maintain a site, a developer can:
Local Drupal development can be tricky, especially with so many tooling choices. Having an environment that works for you is important whether you're a developer, tester, designer, or any sort of stakeholder. In this session, we'll review a few of the tools available (there are 37+ for Drupal at last count), their features, and meet some of the folks who build and use them.
This will be a panel discussion. Possible topics:
Configuration versus content has been a long-standing battle within the development process for Drupal. Managing content across environments or within the build process for a project is often a complex task that gets circumvented. What if there was a tool that let you create and maintain your content within the codebase for your site? What if this content could then be deployed and installed into another environment? That is exactly what the YAML Content module allows you to do.
Nearly every new project focuses heavily on the flashy design and fancy tools it'll make for its visitors. So much focus is driven into the site user's experience to make it intuitive and pleasant, but in many cases this ignores the users that will visit the site more than anybody else: the content editors.
So you learned the importance of tests. You also learned that they are made pretty simple with Drupal’s PHPUnit framework. You may have even invested some time to set up behavioral tests using Behat Drupal Extension. Now it’s time to bundle all the testing together in a nice automated pipeline.
In my session, I'll show the most common vulnerabilities that our drupal code can have and how we should be prepared to avoid such an insecure code to be released. I'll also speak about what we should do if we found any vulnerabilities on contributed solutions.
As we all love automated tests, I'll present some tools that can test our applications from a security perspective.
This will be the very first time in the United States to play Drupal Vulnerability Bingo and learn how to develop Drupal sites in a secure fashion.
In this talk, I'll go over:
In this session we are going to explore some advanced techniques for building and running migrations.
Sometimes you can define your migrations in a single file, run them, close your laptop and go grab a beer. But let’s face it, most other times things are bit more complicated. What we will talk about in this session are some of the cases in which you need to get a bit creative. Such as standardise your source data. Transform it before it gets imported. Or build dynamic migrations.
DevOps, CI, Build, Test, Deploy! There are a lot of different components flying around this buzzword-compliant practice. It’s hard to know where to start. (Spoiler: always start with low-hanging fruit!) But the promises are very attractive: Fewer bugs, faster deployment, greater confidence in your changes.
Learn practical tools and workflows from those of us already in the trenches. We will cover:
Identifying the areas where automation will make the biggest difference
Virtual. Remote. Distributed. Pick your label. This style of organization is becoming more popular and in-demand among many Drupal shops. While many folks have gone remote, some people find the experience quite isolating and disconnected.
Does remote work make people happier? Does it make them more productive? The answer is not really. It is not the act of working from home that creates employee happiness; it is creating a culture that fosters remote practices to develop meaning, collaboration, and happiness.
Don't you wish there was a way you could give each and every user of your module's admin experience a quick and easy way to learn what each setting really did and why it was there? Good news Drupal 8 users, this is actually in core. The Tour Module has been in core since the first release of Drupal 8 and is awaiting you to leverage it.
In a world of endlessly approaching deadlines and pressure for always better results, who has time to do a retrospective? It turns out, successful teams do. Undertaking the necessary discipline it takes to develop the habit of this part of the Agile process does take effort but the end results are well worth it.
For a lot of teams that try, these end of sprint meetings can quickly turn into personal anecdote sessions and become completely based on 'gut feel' that is just a painful step that does not feel like it accomplishes anything valuable.
When leveling up as a developer, one of the most intimidating aspects often is using the command line interface, or CLI. In fact, it might seem downright terrifying. The reality is: If you can type, you can use the command line.
Every senior level developer will remember a time when they got overwhelmed by opening the terminal. Those same people will tell you this is one of the most important capabilities they acquired.