Warsaw. May 2018. A bunch of friendly and brilliant people taking to the stage to share insights on front-end web development matters and inspire an eager audience. Balloons. Following my colleague Blazej’s great advice to sign up for the city’s public bike system, I happily rode my way to Front-Trends, a very well organized conference for developers on all experience levels.
Retrospectives are an essential part of our team’s workflow. After each iteration, we get together to collect insights and feedback. By doing so, our teams ensure they have time to celebrate achievements, learn from mistakes and steer their efforts along a process of continuous improvement.
Drupal is all about security
The Drupal community is unique in many ways, and the Drupal Security Team is an example of this. They provide documentation about writing secure code and keeping your site secure. They work with the drupal.org infrastructure team and the maintainers of contributed modules, to look into and resolve security issues that have been reported.
I’ve recently revisited the concept of vertical rhythm in page design and I like to think it’s paying off in practice. By adhering to a simple baseline grid I’ve noticed improvements in my typography, layouts, and design consistency.
“Absolutely incredible!” - just one quote from our first Amazeenar in which we explore the power of GraphQL Twig. Decoupling Drupal is the future, however, it may be a big leap to learn a whole new development stack. With GraphQL Twig, we can take baby steps with a soft-decoupled approach by writing GraphQL inside our Twig templates.
In this series we’ll take a closer look at progressive decoupling in Drupal 8. We’ll go through the project setup, check the tools and libraries and discuss potential applications. Let’s start with the definition.