Come join the BADCamp organizing collective as we share why and how we plan, organize and deliver the camp. Expect an irreverent but honest discussion about the ins and outs of raising funds, securing facilities, building convention websites, organizing volunteers, eating tons of vegan Vietnamese food, designing things at absolute last minute, playing various board games both competitively and cooperatively, and most importantly achieving consensus among a diverse but friendly group of like-minded peers.
11:00am - 12:00pm
This presentation will start you on your journey into Drupal 8 module development. It will show you the steps you need to take to make a simple but useful Drupal module.
You can checkout the module now.
Drupal has a built in search module - but it's capabilities are limited. Apache Solr is the go-to solution for building advanced search engines within a Drupal site. It works by indexing your content in an efficient way for retrieval by keyword search. With a few modules, you can quickly build pages that let your users find content they want.
I'll talk about the concepts behind search indexes, and walk through the setup for building a robust search page.
Topics covered will include:
GraphQL has been deemed everything from the death knell of RESTful architectures to the query language of the future. Created by Facebook to power its data fetching and coming to Drupal 8 thanks to Sebastian Siemssen, GraphQL portends a dizzying shift in not only how client-side applications request and receive data but also how payloads are interpreted and formatted on the server side. What exactly is GraphQL, and what distinguishes it from the rest (no pun intended)?
Images have always been an especially tricky item in responsive designs. They need to look good in a variety of screen sizes, screen resolutions and minimally impact performance. HTML5 has solved that problem with the new <picture> element, but how do we use that in Drupal? Even trickier, how do we still maintain the level of control and consistency both clients and designers expect from Drupal.
Drupal is doing a great job of managing and organizing your content, but your content doesn't have to end at Drupal's front door; how do we get all of that juicy, structured data out of Drupal and into other websites, mobile apps, or other data stores?
Building a successful Drupal website or platform often involves a lot of configuration & modeling on the needs of the folks who will be using the site & how the content they are producing is exposed.
Who are these ‘end users’ we refer to? They are generally just good people who want to easily get work done & we’ve been those people - in Drupal 5, Drupal 6 & Drupal 7.
This session will focus on strategies & tips drawn from what ‘end users’ need & then explore some Drupal Examples of how to configure Drupal to be more end user focused:
PhpSpec is a toolset for building out testable pieces of functionality strictly designed to meet (and only meet) the project requirements that you have made explicit. Identify your inputs, test your expected outputs. That's it.
Wait! Don't go. This is not a look-at-this-cool-tool talk. This is a live identity crisis, with a demo. How do we as developers mature our skills and deliver testable, functional code while we continue to work on Drupal 7?
Talking through that question includes:
Your content creators are angry, your SEO's head-desking, and you're drowning in WYSIWYG buttons. Your site is full of blobby, inflexible pages. Chunk 'em up with content types!
Today we need to think beyond just pages. It's about discrete pieces of content that can be leveraged in a myriad of ways. In this session, you'll be introduced to how Drupal organizes content into types. You'll see how to use fields to break out of the WYSIWYG and build adaptable content packages that fit into your overall content strategy.