The current trend in Drupal front-end development, particularly with regard to Drupal 8, is to build components first and then assemble the components into full Drupal pages.
The benefit on the front-end development side is code that can be applied in a modular fashion. If done correctly, it can improve efficiency and maintainability. However, for the designer it signifies a need for a change of approach. Sure, it makes good sense for designers to think about web sites as a system of components, but clients want to see full pages. Then after the client approves a design direction, what happens? The front end developer gets the same design files as the client. This is somewhat useful, but does not give the full picture, namely:
1. What are the components without having to hunt through dozens of png files or pages in a pdf file?
2. What are the specifications for the component?
This session will outline a methodology for bridging the gap from design to presentation to handoff to a front end developer.
It is intended for designers and front end developers.