Global Track Chairs

• Who is the global team and what do they do?
  Rick: The global team is our organizational memory in putting on DrupalCons. They have been local track chairs and they consult with the locals to guide us away from potholes and toward the best sessions. We have a North American and a European global track chair for our standing track: Coding & Development, Frontend, Site Building, Business and Strategy, and DevOps. Link: https://association.drupal.org/drupalcon/global-team

• Jozef, what is your role in DrupalCon Prague?
  Jozef: My role is to help the local track chair with anything he needs help with:) So mostly it is to support him, discuss various issues that arise during the whole preparation process and mostly during the session selection process.

Track

• Jozef, who do you work with on the Frontend track for Prague?
  Jozef: Together with my US global co-chair Ken Woodworth we work mostly with Jesper Woeldiche who is the local track chair and is doing an amazing job!

• What is the theme of the track?
  Jozef: This year we wanted to focus on implementing established best practices in both design, workflow and code and exploring cases that stretch the boundaries of what can be done with Drupal. Since building function able, usable, high-performing and beautiful websites requires you to go beyond the framework itself.

So the MAIN THEMES are
Twig!
De-druplifying the user and the editing experience
Mobile tools & techniques
Frontend performance
Interactive maps and visualizations

• What gets you excited about being a global track chair for Drupalcon Prague?
  Jozef: I am always excited when I see the amount of great session submissions that we have each year. It is always great to see how much wisdom and experience there is within our community and that these experts are willing to share it. To me this is the true flavour of an open source community.

• Rick, what are you excited about at DrupalCon Prague?
  Rick: I am excited about the innovations brought to DrupalCons by the local Prague team. The use of video on the site and for site submissions. From the popularity of the SASS/Compass triple BoF in Munich, I am very excited about the ½ day hands-on Labs sessions and I am excited at bringing that format to the North American DrupalCons.

aGov Distribution

• What is aGov?
• Previous next is the main driving force behind aGov
• Why did you create it?
• Features
  • Australian metadata standard
  • Workflow
  • Scheduled publishing
  • Site archiving
  • Integrating with an accessibility checker
  • Security features
  • Responsive

• Accessibility

  • WCAG 2 AA
  • Color contrast ratios

• What modules are you using?

  • Media
  • Blog
  • Honeypot
  • Panels in-place editor
  • Workbench

• Patched modules along the way to make them accessible

Use Cases

• Government Departments that want to get a site up quickly

• Is this only applicable to government in Australia?

  • Are there different standards for government agencies in Europe or America?

• Collaborating with Canadian distribution

  • Why can’t they just use aGov?

• Had an independent audit by Vision Australia

Future

• What’s in the future?
  • Shared infrastructure (taxonomy, etc.)
• Beta version of the accessibility checker is out, we’re going to improve that
• Possibly rebuild on Panopoly

DrupalCon Prague

• When is it?
• Where is it?
• Who are the keynote speakers, and what will they talk about?
• What tracks are available?
• Are there any featured sessions you’d like to point out?

Global team

• What is the DrupalCon global team?
  • Historians, consultants, volunteers who get no credit
• Who are the globals?
  • Standing tracks, North American and European leaders,
• What are the qualifications to be a global?
  • Previously a local track chair, content expert
• What do you do?
  • Herd cats, deal with problems

Kraftwagen

• On the kraftwagen.org it says that Kraftwagen is “Drupal for large (distributed) development teams and staged deployments.” Can you elaborate on what exactly that means?
  • (Rolf) pain of configuration in DB. Everything in code is essential. Standardized workflow
• What do you mean when you say “Drupal for developers”?
• It states that everything is in code. Does that include info from the database, like configuration?
• How does this compare to the configuration management initiative in Drupal 8?
• How does it integrate with multiple deployment targets like local, staging and live environments?
• It mentions skeletons, what are those?
  • (Rolf) start points. mention scaffolding
• So, how does this all work? What are the components of Kraftwagen?
  • (Rolf) kraftwagen (drush extension) and 2 important modules (kw-manifests and kw-itemnames). explain the workflow of Kraftwagen (setup, build, init db, update)
• On the site is says something about Environment awareness, and mentions that the Devel module shouldn’t be enabled on a live server, but should on a development environment. I get around this by using a global git ignore file on my local machine that ignores the devel module. So, when I spin up a new site on my local machine, part of that process is to install the Devel module, but my system prevents it from ever being pushed anywhere automatically. How does Kraftwagen deal with that?
  • (Rolf) builds are not environment aware, but dependencies and manifests are.

Use Cases

• Are you familiar with Aegir? How would you compare the two?