Drupal Camp Asheville 2024 - July 12th-14th
As developers, we’re all aiming for simple, easily documented code. Which is great as professionals. But we forget that we can still have fun with it. Code can be complicated and elegant, creative and amusing. SCSS mixins and formulas, javascript functions and DOM manipulations can be art.
Are you looking to improve the handoff between your design and development teams? In this session, we’ll share our approach at Lullabot for how the design team works with the front-end team throughout the entire design process to help improve the design handoff. We’ll discuss:
Nearly every new project focuses heavily on the flashy design and fancy tools it'll make for its visitors. So much focus is driven into the site user's experience to make it intuitive and pleasant, but in many cases this ignores the users that will visit the site more than anybody else: the content editors.
Design systems are all the rage these days, but what exactly is a design system? How do you know when you need one? In this session we'll cover the following:
In a user-first world, content is the basis for ensuring great user experience. A content audit lays the groundwork for aligning organizational objectives with site visitor needs. It is the preparatory work for the site architecture, content model, and page layouts. It addresses content governance and the content creation process.
With 40 years of scientific research, development programs in 70+ countries, and technical services for hire to other NGOs, FHI 360 needed (and found) a better way to organize and feature its abundant website content.
You’ve gotten familiar with Drupal 7 theming and are starting to feel comfortable with it, just in time for development to start shifting to Drupal 8. Or perhaps you’re new to Drupal theming and aren’t sure where to start. Either way, this session is for you!
For some, accessibility conjures nightmares of garish focus rings and high-contrast fonts. For others, it's snooze-inducing checklists ad nauseam.
User personas are good tools, but they have limits. They take a narrow look at what a specific "person" is going to do on a website. Personas don't give us a bigger picture of what drives our users and why they do the actions in the first place.
With all of the advances in DevOps, it is easy to focus on delivering more, faster, as our important measures of success. However, DevOps is as much about listening as it is about delivering. How do we know we are delivering the right things? How are we informing our customers of this work and getting their feedback effectively?
