Reasons for choosing standards-based technologies

Submitted by aleksip on Mon, 10/09/2017 - 18:12
The recent announcement that Drupal is looking to adopt React has inspired me to live up to my Twitter bio, and be an active advocate for open standards-based technologies. While my knee-jerk reaction to the announcement was to focus on React, this blog post approaches the topic of adopting technologies in a more general manner, while still aiming to contribute to the current front-end framework discussion.

Values, community and technological choices

Submitted by aleksip on Wed, 10/04/2017 - 21:10
Drupal needs to adopt a JavaScript framework for its administrative interfaces. The selection of this framework is an important decision, which should not be based on just technical merits or popularity. Drupal has been an open source project and a community for over 17 years, and when we make decisions like this, our values should weigh more than what is the hottest JavaScript framework at the moment.

Does Drupal have a minor upgrade problem?

Submitted by aleksip on Tue, 04/25/2017 - 20:47
Drupal 8 has a new upgrade model, and the promise is to make upgrades easy forever. The idea behind the upgrade model is great, and has already been proven in other projects like Symfony. However, there might still be some issues that need to be solved, as demonstrated by the recent 8.3 release and the security release that followed it.

Presenting component projects

Submitted by aleksip on Fri, 05/13/2016 - 21:39
Starting right from the Driesnote, it seemed like the topic of theme components was coming up everywhere at DrupalCon New Orleans 2016. Out of all the activity in this area I have been especially interested in two things: presenters and component folders. I think that they are two key pieces required for the next step, which is component projects.

Making Pattern Lab work with Drupal 8 Twig theme templates

Submitted by aleksip on Fri, 01/29/2016 - 15:55
In the solutions described in this post I have tried to use the existing extension mechanisms built into Pattern Lab as much as possible, and not to introduce any dependencies to Drupal core. The end result is that Pattern Lab can be used on its own with just the Twig templates, CSS and other assets from a Drupal theme.

Atomic design, Pattern Lab and Drupal 8 theme development

Submitted by aleksip on Fri, 01/29/2016 - 15:50
When presented with something that almost instantly seems obvious, you don't need much more convincing. For me atomic design was like that. After making the choice to use atomic design and Pattern Lab in a real world Drupal 8 project and seeing the methodology validated, I have wanted to design and build all websites in this way.