Articles

In this article, John Doyle (CEO, Drupal Architect at Digital Polygon) explains why creating APIs is no longer enough, and organizations must effectively market their APIs to developers and product owners if they want to gain traction. In this post, John Doyle will explain what it takes to achieve business success with your API projects. 

Providing a delightful developer experience is about more than just satisfying technical requirements: there are psychological factors at play that influence expectations towards API products. In this article, we explore the importance of expectation management for developer success.

One of Pronovix’ partners is from the energy industry. The aim was to create a status report of the developer portal’s state at that time. Based on that, and after mapping out the needs and how Pronovix best can serve the Company's goals with the Zero Gravity Developer Portal solutions, a closer collaboration has been started.   

Developer Success as an objective can be seen as the combination of successfully serving the needs of the different participants in the API economy: application user experience, developer experience, and value exchange. From among these three, here we focus on the onboarding needs- and behavior of the developer who builds the application.

A shortened transcript from the panel discussion at the API The Docs conference in Amsterdam. At the event, John Daffern (BT Group), Jack Bambury (Shell), Koen Adolfs (ABN AMRO), and Suzanne Daniels (Port) answered Carla Teixeira's (Miro) and the audience's questions.

A developer documentation hub CMS can underpin a unified content strategy that ensures consistent branding and styling, provides access control, can capture intent signals for marketing, and more, while individual teams can keep using their working docs-as-code tooling. In this article we discuss how docs-as-code content is mapped and migrated into the CMS, and what benefits a DevRel team can expect.