Blog items

Automating repetitive tasks doesn't only give a satisfying feeling; it also prevents mistakes that you can easily overlook. Let's take setting up your development environment when working on a Drupal project, which is a process you ideally should do every time you start working on something else.

I'm using Windows for quite some time now, but honestly, it hasn't been the most comfortable operating system when you're creating software. Sure, there are workarounds, but the integration of development tools doesn't feel as smooth as on, for instance, Ubuntu.

When using automated tools to improve code quality, it sometimes happens that warnings are shown while the code is correct or hard to fix. Depending on your setup, this warning can prevent committing your code or setting up a test/acceptance environment.

To improve the editing experience for content creators, you often want to alter the styling for the form that is used to create and edit nodes. These forms use the node-edit-form.html.twig template to generate the HTML when using an administration theme, and no extra theme suggestions are provided by Drupal natively.

I have to admit something, and it's a bit weird for a programmer to say, but I like comments. And I like them a lot, really a lot. If I'm frank, I love them even more than code. So, now that I've said that, I do feel relieved.

A default value can be set for fields that are attached to a content type (i.e., any field-able entity). The entered value is used to pre-fill the form (i.e., entity) when creating new content. Although having a static starting value is often perfectly fine, true power comes when these values can be set dynamically.