A few years ago I was just getting started learning Drupal 8 and decided to try to play around with the Twig theming templates. I barely understood Drupal at the time so that was a bit of a mistake. Not really understanding what I was looking at meant that I was overwhelmed quickly by the number of files and not understanding what I was looking at inside of them. I soon realized that if I was going to work on a theme, I needed to try to understand Twig, but without the complexity of Drupal surrounding it.
26 March, 2018Web Projects on by : Rob Tags: Drupal 8, Projects, Webform
I was recently working on a client site in Drupal 8 that involved a multi-step form. The client is an insurance agency and wanted to have a quote form that users can fill out to start the process of getting a quote for insurance. Since the agency covers multiple kinds of insurance, this meant that the form needed to handle multiple types of insurance. I thought about doing multiple forms for simplicity, but realized that a single user might want to get a quote for more than one kind of insurance and asking them to fill out the same information multiple times would be frustrating and would be a negative user experience.
I’ve always wanted to really get some more usable information out of my analytics reports. So far, all I’ve really ever done is just paste in the basic Google Analytics (GA) code and call it a day. I poke around the reports and kinda think I know what’s going on, but getting the really helpful
I’ve been through this a couple times now because I wanted to move my NPM global install location to a new spot where I wasn’t constantly dealing with permissions issues and both times it was a bigger hassle than it probably should have been.
Now that I’ve passed version 1, I’m at the place where I can start adding UX enhancements that will make the app more usable and intuitive. The first and most important one is hiding the card entry form. It defeats the point of a flashcard app if you can see what the front and back