The first challenge of any Front-end Developer is knowing when to stop theming a page and to start building a design system. It is too easy to focus on the homepage, landing page or detail page of a site without ever thinking how the components on a page may be used. This often leads to extraneous markup, bloated CSS and technical debt that increases the complexity of your Drupal 8 site.
The Drupal Diversity & Inclusion Working Group (DD&I) was formed after DrupalCon New Orleans by Nikki Stevens (@drnikki). Nikki, along with Ruby Sinreich (@rubyji), Greg Dunlap (@heyrocker), Nathaniel Catchpole (@catch), and myself (@sugaroverflow), have spent the last year working to build a more inclusive, diverse and respectful Drupal Community.
In this session, we will embark on a Pokemon adventure to learn Object Oriented Programming. Each OOP concept will be explained with a Pokemon scenario, modelled into data, bridged to an OOP concept, and then shown in code.
Drush is really handy when it comes to its various standard commands. It's even better when you have your own custom commands! I'll cover step by step what you need to do to get your own nifty command alias to appear in that ever so long list of drush commands.
This session is for you if...
So, you know what nodes and modules are, how to configure your views, maybe you've even tried your hand at panels and blocks. But where do you go from there? The chasm between site building and web development can seem awfully wide, and it can be difficult to take the initial leap.
The idea of a decoupled Frontend and Backend has been around for a couple of years. Some teams tried them out, but nobody was really fully satisfied with it. Too many problems arose during development; bad or non existing accessibility, no support for crawlers and bots, changing APIs and expensive refactorings. Even the easy task of displaying a menu on the frontend was problematic.