Articles

In our Developer Portal Design Guide series, you will read about common design patterns, get an insight into our project work related experiences, and learn how we tackle the design of a developer portal user interface. Part 1: Developer portals on different devices & responsiveness

UI design is a key component of a great developer portal. But what makes a great devportal design? How can you avoid obvious pitfalls? What are UI elements you could use to improve the developer experience (DX) of your devportal?

In the second part of our series, you will discover analytics and why it’s needed for Docs As Code. This post is focusing on the functional basis of Quality Assurance.

How can API portals enhance user experience in general, and pay special attention to developer experience? How can design elements support usability and content? What makes a devportal, in overall, stand out against competitors? We highlight the criteria that we think define the categories Best New DX Innovation, Best Design, and Best Overall Developer Portal and we include examples taken from last year’s nominated devportals.

In the first part of our new Docs As Code series, you will read about the philosophy behind the approach coupled with Quality Assurance, and how you can get started.

We would like to introduce a new tool called _Rector_ that could speed up an upgrade process and can reduce upgrade costs. We run a proof of concept for the possible use cases in which Rector can be beneficial for Drupal developers - including but not limited to the automated update to Drupal 9.