I caught the second half of this talk. Even though I'm not planning any projects that justify a headless approach, it was interesting to learn about use cases where it would be appropriate. Good discussion but difficult to hear.
It was nice to hear the real world examples of how a team was handling the issues, but I was expecting more depth on the subject. To be fair, the session was marked for a beginner audience.
Without a doubt the most entertaining technical talk I've ever seen. The videos of the code in action would have been perfect if they had only been larger. Small issue, since a presenter would be right to expect a larger screen.
Wow. This was even better than I was hoping it would be.
Accessible to non-technical people,
entertaining,
and yet, clearly given based on technical experience (and a deep familiarity with the books).
Some of the information from the Q&A could go into the presentation as it was a bit short, but ... this also would fit really nicely into session slots of different time lengths at other conferences.
Huge difference between 'reading from the speaker notes' voice and 'speaking candidly' voice. Wished to have seen more of the candid voice, than the robotic, official line. Candid voice feels like somebody with experience, knowledge, insight, and perspective. 'Note-reading voice' sounds forced, taking the party line.
Great presentation that did a fantastic job integrating the MADcamp theme into their presentation. Two things: one, and you may have done this at the end (I had to leave early), but it would've been great to see some examples of REAL eCommerce sites using Commerce. Also, I would capitalize the A in DrupAlice, because otherwise I read it as Drupal lice. :-)
This-- combined with Daniel Montgomery's presentation-- made a great argument for decoupling Drupal from the presentation and making Drupal output friendlier markup for non-Drupal FEDs. I appreciated the Palintirian history of sustainable theming. The more we can leverage the rapid developments in the front end world, the more palatable we make Drupal to work with other communities.
This was well presented, but I didn't feel that I took away anything that was very useful. That's probably largely because I don't work for a development company so I'm incredibly unlikely to run into a scenario where I need to justify what code our CMS runs on.