Happy Friday! We hope you've had a great week and that you're gearing up for an even better holiday weekend.
This episode, we decided to switch it up a little and find out what some of the Mediacurrent team has in store for Labor Day. We hope everyone has a safe weekend and we'll pick back up in October with episode 17.
When building more complex queries using db_select() you will often want to see the exact SQL being generated. This is helpful for understanding the query or simply debugging the results.
I'll show you how to see the exact query being generated with db_select() as well as getting all the values passed as arguments. The examples in this article will be applicable for both Drupal 7 and Drupal 8.
Example #1: using db_select() and creating the query dynamically:
If you guys didn't already know, we're in the middle of the Results Oriented Web Roadshow! You can take a closer look at Tom's adventure across the country here. Our next stop is this upcoming Tuesday, September 6 in Chicago at Timothy O'Toole's Pub!What you can expect: Learning:
We will be giving a short presentation that focuses on the essential techniques to...Read more
This module provides a set of usefull process plugins to be used with the Migration Framework in Drupal 8. As the project evolves more plugins will be added.
The first release of this module is planned for the first week of september 2016. If you have any questions / suggestions please submit an issue.
The basis for knowing what to focus on for evolving Drupal core is learning about what people want to do with it.
Testing the initial experience of core as a whole has had our main attention so far. Now with focussed initiatives (content workflow, media handling, outside in, layouts,…), we’re adding experimental features with the assumed requirement that we validate and improve them trough feedback from usability testing.
So, we could (should!) create a more regular schedule of more smaller instead of few bigger usability test sessions. What’s our version of getting out of the building and increasing our exposure?
What would it look like if we did test every 6 weeks?
Produce testing scripts for each initiative. These can be reused, eventually updated where needed. Every 6 weeks we run those tests for each initiative. We learn what works, what needs to be improved. Initiative teams can prioritize fixing UX bugs. All things are connected anyway so we’ll learn about overall issues as well.
Feedback from the test participants can feed into ongoing persona work: what are people trying to achieve? Voilà, we’re learning about the Why.
Of course this requires planning, recruiting participants, having a setup for remote testing, getting access to a usability testing lab once in a while, observation, analysis, designing possible solutions, reporting back to the community, creating actionable issues to work on etc. But wow, we’d learn so much about where to focus our efforts.drupaluxusability testdrupalplanetSub title: Something something usability testing