Rendering HTML with Drupal: Past, Present and Future

Comments

Comments are closed.

Rated 4

Anonymous at 10:36 on 23 Mar 2015

Thorough discussion, practical and thoughtful conclusions, maybe a little too much historical perspective. I would have liked to see the last third of the slide deck as its own presentation!

Rated 4

Anonymous at 13:22 on 23 Mar 2015

Like the other comment mentioning "I would have liked to see the last third of the slide deck as its own presentation!", I appreciated the history, but really wanted to hear more about the last third.

Yes on historical perspective...I love that shit! I see the other commenters are dissing that part of the talk, but if someone doesn't bring it up, how are new people supposed to know why things are the way they are. I mean, it was supposed to be 2/3rds of the talk anyway based on your title and description anyways.

The fact that you finally explained to me the reason behind Drupal's div-itus problem was magical. No other talk I've seen has come close to elucidating this for me and that designers/front-ends strictly using what CSS they were given was once a best practice as "sustainable theming".

The debate at the end was also great between whether Drupal should present shiny buttons to the end user for helping with design inherently coupling data to presentation or if more decoupling is needed where the truth is in the template and screw your shiny Quick Edit button. It still seems like a debate, but I don't see how the future will not look like what you presented as being in store for the future.

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.