Decouple the themer

lakshminp

How many times have you faced these problems?

  • Delay in theming due to backend dependency

  • The backend or frontend developer spend a lot of time to investigate the issues that crop up because of changes by each other

  • The themer has to wade through the sea of divs and classes and make changes so that the theme is consistent as before.

  • QA team has to regress multiple times due to changes that are incomplete from either backend or frontend

  • Delay in overall project due to all of the above

How do we ensure that this does not happen? How can we avoid all the extra work that goes into this?

We decouple the themer from the developer. We define a process where a functional HTML file acts as a contract between the backend developer and themer. The backend developer needs to implement the functionality and make sure that the DOM spit out by Drupal matches the exact functional HTML given to them. The themer writes CSS and js to make the HTML work seamlessly on all the 150 odd devices and 5 browsers. This also creates a clear separation of concerns between the developer and themer, offering other advantages like semantic HTML and curing the famous “Drupal Divitis”.

In this session, we present techniques to decouple the themer and the developer so that they work independently of each other while adhering to their “responsibility zones”, and how it benefits them and the project.


As this presentation will feature some technicalities, familiarity with creating Drupal themes is required.

Register NOW

Session Track

Front End

Experience Level

Beginner

Drupal Version