It keeps individual components encapsulated in their own directories containing all the css, js, and template assets necessary for them to work, and using an info.yml file to declare these components and their framework dependencies to Drupal.
Gather 'round and I'll tell you the story of my journey from starting out as a complete Drupal newbie to becoming a core committer for Drupal 8. I'll share some lessons I've learned and we'll talk about how you can implement some of them into your life and your career.
Front-end performance optimization is not necessarily complex, but it is specifc and always evolving. Browser specs change, mobile adoption rates are sky rocketing, and new technology is driving more intrictate (read: heavy) applications. Juggling the demands of the project versus the reality of the network is a battle that is best fought with good technique.
When you’re designing a Drupal site, you often don’t know how much your design is going to survive use by your content administrators — so it’s tempting to either tie your design/theme to a rigid content type layout (ultimately frustrating your admins who want to use your styling midway through a long page, not at the top or bottom in a prescribed field), or rely on your admins to add CSS classes through the WYSIWYG to elements that need to get special styling midway down the page (…also frustrating your admins, who probably hate using the Source view).
CSS bloat is a challenge for every enterprise website. As design elements grow and change, code gets added but rarely deleted and our CSS files get larger and harder to maintain. What was that class name that makes the font color black and 22px? Where is the pattern that gives me the right layout and color scheme for this design? Modular design encourages us to look beyond classes and begin styling on the component level using data attributes. Separate content from design and your code base becomes reusable and more compact.
Images seem simple: save, compress, and upload. Yet, I’m willing to bet you’ve asked yourself one of these following questions: What file type do I use? What file size (or k-weight) should I target? Is there a “correct” way to save an image for the web? What about retina screens, do I need to do something different? This session will explore all of these questions and more.
Lack of available talent to hire is a common refrain of business owners in our field. Give up on looking and complaining! To create a sustainable business you need to be able to grow your own.
Growing your own means hiring smart, motivated people with all the right soft skills and investing in them for the long haul. In return for helping give them a career, expect that they'll reward you with loyalty, will care about helping to teach your newer staff, and will work together with a cohesive vision (having all been trained the same way).
When we started our support program, it almost seemed like post-launch support was a dirty word in the community. It was very easy to build a fancy Drupal site and walk away. We noticed that the average end user can't really work a Drupal site that well. This led to a very simple question: how do we offer support to clients so they benefit and we make a profit?
We will go over many methods that have worked for us. We will also talk about the methods we tried and failed at in the past four years of our Kalacare program. Topics will include, but will not be limited to:
Trainers: Chapter Three, Zakiya Khabir, Phil Boden, Drew Bolles, and Israel Morales
This training will focus on creating Drupal 8 theme code, so bring your HTML, CSS and PHP skills. Come with a local copy of Drupal 8 running, if you get stuck here, show up early and we’ll help you out before we get started.