Refocusing on the Developer Experience: Updating Terminology

Introduction

This update refines the language used in the developer portal to better resonate with individual developers. It involves reverting a B2B-focused hero section to its original developer-centric narrative and consistently using "developers" instead of "builders" across multiple language files.

Changes Implemented

The primary focus was on aligning the messaging with the target audience: individual developers. This was achieved through the following steps:

• Hero Section Restoration: The main title and subtitle of the landing page were reverted to their original form, emphasizing the value proposition for individual developers.
• Terminology Update: The term "builders" was replaced with "developers" across all relevant text in the English (EN), Spanish (ES), German (DE), and French (FR) language files. This included navigation labels and section headings to ensure consistency.

Impact

These changes aim to:

• Improve Clarity: Using consistent and accurate terminology enhances the user experience for developers visiting the portal.
• Strengthen Resonance: A developer-focused narrative will likely resonate more strongly with the intended audience, potentially increasing engagement and adoption.
• Enhance International Consistency: Applying the changes across multiple language files ensures a unified message for developers worldwide.

Example

Consider a section heading initially labeled as:

For Our Builders

This was updated to:

For Our Developers

This seemingly small change clarifies the intended audience and avoids any potential ambiguity.

Next Steps

Future improvements might include:

• Gathering user feedback on the updated language to ensure it effectively communicates the platform's value.
• Conducting A/B testing with different messaging to optimize engagement.
• Extending the terminology update to other areas of the developer portal to ensure a consistent experience.