Articles

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.

Driving API adoption is crucial for a developer portal. How can you integrate all your users’ needs into your devportal? What are the jobs that a developer portal needs to fulfill? In this post, we explore how you can strengthen user engagement right from the very start of your API program regardless of whether you have a public-facing, partner or internal devportal.

After stock photo companies, video player software providers and audio distribution platforms this article will analyze developer portals in the journalism industry. We focused on two types of news organizations: the traditional ones that already existed before the digital era (such as TV channels, newspapers or radios) and those that were born web-based (and serve as online data providers). Our research revealed some of the differences in their approach to developer portals.