The Web Chefs have taken over San Francisco this week and we’ve been having a blast! We’ve come for BADCamp, one of the biggest Drupal camps of the year, and certainly one of our favorites.
On Thursday Ian, Taylor, and Patrick led the Advanced Sass and Compass for RWD training with our good friend Sam Richard. We enjoyed a beautiful relaxing day at the Palace of Fine Arts and ended up at a secret rum bar sipping on tiki drinks that evening.
On Friday Web Chefs attended the Frontend Summit and the DevOps summit, while I held down the photo booth and handed out Four Kittens t-shirts to BADCampers. I snuck away for a while to shop in Union Square and enjoy a steaming bowl of ramen before meeting up with the team to head out for parties with Chapter Three and Commerce Guys. The big weekend has come and we are psyched to see BADCamp filling up with friendly faces! We hope to see you at one of our sessions or just stopping by to say hi!
Web Chef sessions
Getting content to a phone in less than 1000ms
We must get the content to the user, and we must do it fast. In a world constantly moving, getting a site loaded in under 1000ms is key to keeping users on your site, and engaged with your content. This is not a new idea, and the 1000ms barrier has been written about, presented, talked about in web circles for a while now— but how do we actually do it?
Working on a Drupal site, how can we decrease bloat on a page, to get our site delivered to the user quickly and efficiently. What steps can we take to decrease that first hit, so a page is available as soon as possible, especially for a mobile user.
This talk will go over the tech, and the basics of the TCP protocol so you understand where the lag is in presenting a web page. It will describe the modules any frontend developer can use to help in presenting their content, and frontend techniques that can be applied by advanced themes to make your site the fastest on the net.
Headless Drupal Reference Implementation: Lessons Learned
Mike Minecki and Matt Grill
We’ll show you how we designed and engineered a HATEOAS compliant API using Drupal 7, the awesome RESTful module, and a node.js client to interact with it. We’ll dig into this reference implementation and validate which best practices make things easier for the API Clients, and which ones are just hype. Thing’s we’ll discuss:
- What does it mean to be compliant with HATEOAS? What does this even mean?
- If your API is HATEOAS compliant are there libraries your clients can leverage, and what is that development experience like?
- Everything is a resource. Multiple endpoints to represent those resources, and actions attached to them.
- Do hypermedia best practices improve the client coding experience, and pay off long term?
- What API design decisions were the most important for good client coding experiences?
- How do you structure your API to provide compliant responses?
- What API design decisions are just hype and are things you shouldn’t worry about?
- API design tools.
Web Chef session recommendations
- Yo, CSS!
- Building a Modern Front-end with Drupal – Theme Structure, Useful Tools and Workflow Automation
- Beyond CSS: Design Logic for Dynamic Content
- Keeping It Simple
- RESTful Garage – Build your own API speedster
- Drupal in the Post-PHP-Renaissance World
- Protecting Sensitive Data in Drupal
- Using Grunt to Manage Drupal Build and Testing Tools
- Drupal 8 Console. If you’re even remotely thinking of doing Drupal 8 development, check it out. Jesus has been kicking butt working on this; he first showed at last year’s BADCamp and it’s come a LONG way.
- Another vote for Drupal in the Post-PHP-Renaissance World
Let us know what you’re excited to learn and do at BADCamp this year!
Making the web a better place to teach, learn, and advocate starts here...
When you subscribe to our newsletter!