Improve experimentation documentation and messaging

Context

At KubeCon EU 2026, the experimentation discussion (recap) concluded that OpenFeature should more explicitly communicate that it supports experimentation use cases.

Problem

OpenFeature already has API surface relevant to experimentation (tracking API, hooks, targeting key) but the website and docs don't make this obvious. Users exploring experimentation platforms may not realize OpenFeature can be part of their stack.

Suggested improvements

• Add an experimentation section or page to the docs explaining how OpenFeature supports experimentation workflows
• Document the tracking API with experimentation-focused examples
• Blog post or tutorial showing an end-to-end experimentation setup with OpenFeature
• Update the homepage or feature list to mention experimentation as a use case

Related

• open-feature/spec#370: Experimentation support: standardized context fields and experiment grouping
• open-feature/spec#371: Official evaluation metrics hook for experimentation

Start by reviewing the existing website documentation, homepage or feature list, and the tracking API material mentioned in the issue, along with the related experimentation specification discussions. Done means the selected documentation and messaging clearly explain OpenFeature's experimentation use cases, with experimentation-focused examples or an end-to-end tutorial where the scope is agreed.