It was a long-standing desire for me to take the Acquia front-end exam. And today I visited a testing centre and I successfully passed the exam!
Continue readingTag Archives: theming
JavaScript is Coming to Eat You
I’ve just watched the video of Tim Broeker’s excellent talk from BADCamp 2019. And I think everyone who creates classic Drupal sites should see it!
The really short summary of it is that the web changed a lot in the last years (what a surprise…! 😉), and Drupal is not as cool as it was before. Solutions built using some kind of backend service and a JavaScript framework (known as the JAMstack) are the No1.
Fortunately, this is not unknown in the Drupal community. But according to Tim, the new role of Drupal is to be (only) the backend solution for a decoupled frontend. Because Drupal is perfect for that and (can be) better than the other (hosted) services/solutions.
“The backend has been solved, and is now fully commoditized. Our job today is to create amazing experiences that help our users navigate an increasingly noisy barrage of devices, networks, content, and tools.”
Tim recommends (to learn) to use React and/or Gatsby as the front-end solution(s). I know that they are the most famous tools for that, but let me advertise and recommend (the open-source!) Vue.js, Gridsome or Svelte as well (or instead of them)!
And I hope it is too early to bury Drupal theming so I recommend Compony.io too! (More on that later.)
Drupal 8 Twig: add custom CSS classes to menus (based on menu name)
Twig templates of Drupal 8 make our life much easier when we want to customize the HTML output. But when the goal is to change a Drupal 8 menu we have to use the menu.html.twig template which is not the most friendly one and it’s customization can be tricky because of several reasons. So I wanna show you how I did it.
Continue readingDrupal 8 theming basics
You can read below – kind of – a transcript of the presentation I gave at Drupal Developer Days, Szeged 2014.
Once upon a time
…there was a man who had to build a site for a client. This site was really a simple one: a contact form, a static page, articles, comments – and that’s all. And if you listen carefully you may realize that it sounds just like Drupal core! And because this story took place in December, last year, it could be not only Drupal 7, but Drupal 8! (We already had a nice alpha version at that time…)
To share some more details with you, the client was my wife and the developer was me. And I decided to use Drupal 8 because it was possible and I really wanted to learn about it. And I think the best way to learn new things is to face real challenges.
While the core functions of Drupal 8 were enough for us, we didn’t want to use core Bartik theme. We didn’t want to look like thousands of others sites on the net. We wanted something what is a little bit different. So I had to create something custom… And I did it.