add ffe server sdk landing page and stubs for each language (#33220)

* add ffe server sdk landing page and stubs for each language

* add to sidebar

* poll

* simpler setup

* rebuild nav structure

also:
- rename `setup` to `client`
- update links, other URL references

* add tile layout for server landing page

+ also renames the tile partial in the client page for consistency

* add go docs for openfeature implementation (#33234)

* add go docs for openfeature implementation

* add docs for blocking init, custom timeout, non blocking

* no agent version

* Documentation for dd-trace with feature flagging support (#33165)

* Documentation for dd-trace with feature flagging support

* Update content/en/feature_flags/setup/nodejs.md

Co-authored-by: Leo Romanovsky <leo.romanovsky@datadoghq.com>

---------

Co-authored-by: Leo Romanovsky <leo.romanovsky@datadoghq.com>

* Add Ruby feature flags documentation (#33233)

* Add Ruby feature flags server documentation

- Port content from setup/ruby.md to server/ruby.md
- Maintain all Vale linting fixes from previous commits
- Include prerequisites, installation, usage examples, and troubleshooting
- Support for boolean, string, number, object flags and evaluation context

* Update content/en/feature_flags/server/ruby.md

Co-authored-by: Leo Romanovsky <leo.romanovsky@datadoghq.com>

---------

Co-authored-by: Leo Romanovsky <leo.romanovsky@datadoghq.com>

* Add python documentation for OpenFeature implementation (#33247)

* consolidate duplicate files

Files were in two different paths (older `setup` path and newer `server` path)

* Add Java Feature Flags Setup Documentation (#33194)

* Add Java Feature Flags setup documentation

- Add comprehensive Java SDK onboarding guide
- Include installation instructions for Maven and Gradle
- Document OpenFeature provider initialization and usage
- Add code examples for all flag types (boolean, string, int, double, object)
- Document error handling and common error codes
- Include best practices and troubleshooting guide
- Add Java to feature flags setup page navigation
- Document integration with Datadog APM and exposure tracking

Related: FFE Server SDK code freeze preparation

* fix(docs): Add missing bootstrap JAR and improve Java Feature Flags documentation

Critical fixes:
- Add missing dd-java-agent-feature-flagging-bootstrap dependency to all examples
- Add Building from Source section with detailed instructions
- Explain bootstrap module purpose (classloader communication)
- Add troubleshooting for ClassNotFoundException

Improvements to match Java APM documentation patterns:
- Add application server configuration tabs (Spring Boot, Tomcat, JBoss, Jetty, Docker)
- Update all code examples to use SLF4J logger instead of System.out/err
- Add Compatibility requirements section
- Add Getting started section
- Update initialization example to show complete application structure

Code quality:
- Use logger.info/warn/error throughout with parameterized messages
- Show proper exception handling with logger
- Match actual implementation in ffe-dogfooding repo
- Include named client usage ("my-app")

The documentation now accurately reflects the required dependencies,
follows established Datadog docs patterns, and provides complete
setup instructions for the development build.

* docs(java): Improve documentation based on review feedback

Changes:
- Add cross-linking to Configuration section from early warning
- Add OpenFeature SDK to compatibility requirements (it is required)
- Remove all local build instructions (only reference published X.X.X versions)
- Add skip guidance for users with existing agent/remote-config setup
- Clarify ProviderNotReadyError is OpenFeature exception (optional handling)
- Update exception handling to be optional based on availability requirements
- Note that not catching exception may prevent application startup

Improvements:
- Users with existing APM can skip to provider initialization
- Users with existing remote-config can skip agent configuration
- Clear guidance on when exception handling is optional vs required
- Removed all references to building from source

* docs(java): Add event state watching and clarify provider instance sharing

Changes:
- Add PROVIDER_ERROR and PROVIDER_STALE event listeners to async init example
- Note that PROVIDER_CONFIGURATION_CHANGED is optional (depends on provider support)
- Update multiple clients section: "organize context and flags" (not just flags)
- Clarify that Provider instance is shared globally (client names are organizational only)

The Provider constructor doesn't take a name parameter - it's a single shared instance.
Named clients are just for organizing your application code, not separate providers.

* docs(java): Align flag keys and attributes with mobile SDK conventions

Changes:
- Update all flag keys to use dot notation (matching Android/iOS):
  * new-checkout-flow -> checkout.new
  * ui-theme -> ui.theme
  * payment-api-endpoint -> payment.api.endpoint
  * max-retries -> retries.max
  * discount-rate -> pricing.discount.rate
  * feature-config -> ui.config
  * All other flags updated to dot notation

- Standardize attribute to use "tier" consistently (not "plan")

- Remove "country" attribute from basic example to match mobile simplicity

This creates consistency across all SDK documentation and makes it easier
for users to migrate between platforms or reference examples.

* fix tile image, add page to side nav

* headings: sentence-case capitalization

* style linter, general style edits

* Add Java Feature Flags setup documentation

- Add comprehensive Java SDK onboarding guide
- Include installation instructions for Maven and Gradle
- Document OpenFeature provider initialization and usage
- Add code examples for all flag types (boolean, string, int, double, object)
- Document error handling and common error codes
- Include best practices and troubleshooting guide
- Add Java to feature flags setup page navigation
- Document integration with Datadog APM and exposure tracking

Related: FFE Server SDK code freeze preparation

* fix(docs): Add missing bootstrap JAR and improve Java Feature Flags documentation

Critical fixes:
- Add missing dd-java-agent-feature-flagging-bootstrap dependency to all examples
- Add Building from Source section with detailed instructions
- Explain bootstrap module purpose (classloader communication)
- Add troubleshooting for ClassNotFoundException

Improvements to match Java APM documentation patterns:
- Add application server configuration tabs (Spring Boot, Tomcat, JBoss, Jetty, Docker)
- Update all code examples to use SLF4J logger instead of System.out/err
- Add Compatibility requirements section
- Add Getting started section
- Update initialization example to show complete application structure

Code quality:
- Use logger.info/warn/error throughout with parameterized messages
- Show proper exception handling with logger
- Match actual implementation in ffe-dogfooding repo
- Include named client usage ("my-app")

The documentation now accurately reflects the required dependencies,
follows established Datadog docs patterns, and provides complete
setup instructions for the development build.

* docs(java): Improve documentation based on review feedback

Changes:
- Add cross-linking to Configuration section from early warning
- Add OpenFeature SDK to compatibility requirements (it is required)
- Remove all local build instructions (only reference published X.X.X versions)
- Add skip guidance for users with existing agent/remote-config setup
- Clarify ProviderNotReadyError is OpenFeature exception (optional handling)
- Update exception handling to be optional based on availability requirements
- Note that not catching exception may prevent application startup

Improvements:
- Users with existing APM can skip to provider initialization
- Users with existing remote-config can skip agent configuration
- Clear guidance on when exception handling is optional vs required
- Removed all references to building from source

* docs(java): Add event state watching and clarify provider instance sharing

Changes:
- Add PROVIDER_ERROR and PROVIDER_STALE event listeners to async init example
- Note that PROVIDER_CONFIGURATION_CHANGED is optional (depends on provider support)
- Update multiple clients section: "organize context and flags" (not just flags)
- Clarify that Provider instance is shared globally (client names are organizational only)

The Provider constructor doesn't take a name parameter - it's a single shared instance.
Named clients are just for organizing your application code, not separate providers.

* docs(java): Align flag keys and attributes with mobile SDK conventions

Changes:
- Update all flag keys to use dot notation (matching Android/iOS):
  * new-checkout-flow -> checkout.new
  * ui-theme -> ui.theme
  * payment-api-endpoint -> payment.api.endpoint
  * max-retries -> retries.max
  * discount-rate -> pricing.discount.rate
  * feature-config -> ui.config
  * All other flags updated to dot notation

- Standardize attribute to use "tier" consistently (not "plan")

- Remove "country" attribute from basic example to match mobile simplicity

This creates consistency across all SDK documentation and makes it easier
for users to migrate between platforms or reference examples.

* docs(java): Move Java Feature Flags docs to server/ directory

- Move java.md from feature_flags/setup/ to feature_flags/setup/server/
- Update frontmatter to reference server-side landing page
- Apply style edits from linter (sentence-case headings, consistent capitalization)

* extra dev info

* various style edits

* section collapsing

* better sections

* reduce expanders

---------

Co-authored-by: Joe Peeples <joe.peeples@datadoghq.com>

* remove Java from client-side tile partial

* Python review edits

also applied to other languages with the same text

* Ruby review edits

and other languages with same text

* Go review edits

and other languages with same text

* Node.js review edits

+ other languages

* clean up links

---------

Co-authored-by: Joe Peeples <joe.peeples@datadoghq.com>
Co-authored-by: Greg Huels <greg.huels@gmail.com>
Co-authored-by: Sameeran Kunche <sameeran.kunche@datadoghq.com>
Co-authored-by: Oleksii Shmalko <oleksii.shmalko@datadoghq.com>
Co-authored-by: Tyler Potter <tyler.potter@datadoghq.com>

Author: 6 people

config/_default/menus/main.en.yaml

@@ -5617,21 +5617,51 @@ menu:
       parent: software_delivery_heading
       identifier: feature_flags
       weight: 80000
-    - name: Setup
-      url: feature_flags/setup
+    - name: Client SDKs
+      url: feature_flags/client
       parent: feature_flags
-      identifier: feature_flags_setup
+      identifier: feature_flags_client
       weight: 1
     - name: Android and Android TV
-      url: feature_flags/setup/android
-      parent: feature_flags_setup
-      identifier: feature_flags_setup_android
+      url: feature_flags/client/android
+      parent: feature_flags_client
+      identifier: feature_flags_client_android
       weight: 101
     - name: iOS and tvOS
-      url: feature_flags/setup/ios
-      parent: feature_flags_setup
-      identifier: feature_flags_setup_ios
+      url: feature_flags/client/ios
+      parent: feature_flags_client
+      identifier: feature_flags_client_ios
       weight: 102
+    - name: Server SDKs
+      url: feature_flags/server
+      parent: feature_flags
+      identifier: feature_flags_server
+      weight: 2
+    - name: Go
+      url: feature_flags/server/go
+      parent: feature_flags_server
+      identifier: feature_flags_server_go
+      weight: 201
+    - name: Java
+      url: feature_flags/server/java
+      parent: feature_flags_server
+      identifier: feature_flags_server_java
+      weight: 202
+    - name: Node.js
+      url: feature_flags/server/nodejs
+      parent: feature_flags_server
+      identifier: feature_flags_server_nodejs
+      weight: 203
+    - name: Python
+      url: feature_flags/server/python
+      parent: feature_flags_server
+      identifier: feature_flags_server_python
+      weight: 204
+    - name: Ruby
+      url: feature_flags/server/ruby
+      parent: feature_flags_server
+      identifier: feature_flags_server_ruby
+      weight: 205
     - name: MCP Server
       url: feature_flags/feature_flag_mcp_server
       parent: feature_flags

content/en/feature_flags/_index.md

@@ -5,9 +5,12 @@ further_reading:
 - link: "/getting_started/feature_flags/"
   tag: "Documentation"
   text: "Getting started with Feature Flags"
-- link: "/feature_flags/setup/"
+- link: "/feature_flags/client/"
   tag: "Documentation"
-  text: "Set up Feature Flags for your applications"
+  text: "Set up Feature Flags for client-side applications"
+- link: "/feature_flags/server/"
+  tag: "Documentation"
+  text: "Set up Feature Flags for server-side applications"
 - link: "/feature_flags/guide/migrate_from_statsig"
   tag: "Guide"
   text: "Migrate Your Feature Flags from Statsig"

content/en/feature_flags/setup/_index.md content/en/feature_flags/client/_index.mdcontent/en/feature_flags/setup/_index.md renamed to content/en/feature_flags/client/_index.md

@@ -1,13 +1,18 @@
 ---
-title: Set Up Feature Flags
-description: Set up Datadog Feature Flags for your mobile applications.
+title: Client-Side Feature Flags
+description: Set up Datadog Feature Flags for client-side applications.
+aliases:
+  - /feature_flags/setup/
 further_reading:
 - link: "/feature_flags/"
   tag: "Documentation"
   text: "Learn about Feature Flags"
 - link: "/getting_started/feature_flags/"
   tag: "Documentation"
   text: "Getting Started with Feature Flags"
+- link: "feature_flags/server/"
+  tag: "Documentation"
+  text: "Server-Side Feature Flags"
 ---
 
 {{< callout url="http://datadoghq.com/product-preview/feature-flags/" >}}
@@ -18,7 +23,7 @@ Feature Flags are in Preview. Complete the form to request access.
 
 Set up Datadog Feature Flags for your applications. Follow the platform-specific guides below to integrate feature flags into your application and start collecting feature flag data:
 
-{{< partial name="feature_flags/feature_flags_setup.html" >}}
+{{< partial name="feature_flags/feature_flags_client.html" >}}
 
 ## Further reading
 

content/en/feature_flags/setup/android.md …ntent/en/feature_flags/client/android.mdcontent/en/feature_flags/setup/android.md renamed to content/en/feature_flags/client/android.md content/en/feature_flags/setup/android.md renamed to content/en/feature_flags/client/android.md

@@ -1,10 +1,12 @@
 ---
 title: Android and Android TV Feature Flags
 description: Set up Datadog Feature Flags for Android and Android TV applications.
+aliases:
+  - /feature_flags/setup/android/
 further_reading:
-- link: "/feature_flags/setup/"
+- link: "/feature_flags/client/"
   tag: "Documentation"
-  text: "Feature Flags Setup"
+  text: "Client-Side Feature Flags"
 - link: "/real_user_monitoring/android/"
   tag: "Documentation"
   text: "Android and Android TV Monitoring"

content/en/feature_flags/setup/ios.md content/en/feature_flags/client/ios.mdcontent/en/feature_flags/setup/ios.md renamed to content/en/feature_flags/client/ios.md

@@ -1,10 +1,12 @@
 ---
 title: iOS and tvOS Feature Flags
 description: Set up Datadog Feature Flags for iOS and tvOS applications.
+aliases:
+  - /feature_flags/setup/ios/
 further_reading:
-- link: "/feature_flags/setup/"
+- link: "/feature_flags/client/"
   tag: "Documentation"
-  text: "Feature Flags Setup"
+  text: "Client-Side Feature Flags"
 - link: "/real_user_monitoring/ios/"
   tag: "Documentation"
   text: "iOS and tvOS Monitoring"

content/en/feature_flags/server/_index.md

@@ -0,0 +1,72 @@
+---
+title: Server-Side Feature Flags
+description: Set up Datadog Feature Flags for server-side applications.
+further_reading:
+- link: "/feature_flags/client/"
+  tag: "Documentation"
+  text: "Client-Side Feature Flags"
+- link: "/remote_configuration/"
+  tag: "Documentation"
+  text: "Remote Configuration"
+---
+
+{{< callout url="http://datadoghq.com/product-preview/feature-flags/" >}}
+Feature Flags are in Preview. Complete the form to request access.
+{{< /callout >}}
+
+## Overview
+
+Datadog Feature Flags for server-side applications allow you to remotely control feature availability, run experiments, and roll out new functionality with confidence. Server-side SDKs integrate with the Datadog APM tracer and use Remote Configuration to receive flag updates in real time.
+
+This guide covers the common setup required for all server-side SDKs, including Agent configuration and application environment variables. Select your language or framework to view SDK-specific setup instructions:
+
+{{< partial name="feature_flags/feature_flags_server.html" >}}
+
+## Prerequisites
+
+Before setting up server-side feature flags, ensure you have:
+
+- **Datadog Agent 7.55 or later** installed and running
+- **Datadog API key** configured
+- **APM tracing** enabled in your application
+
+## Agent configuration
+
+Server-side feature flags use [Remote Configuration][1] to deliver flag configurations to your application. Enable Remote Configuration in your Datadog Agent by setting `DD_REMOTE_CONFIGURATION_ENABLED=true` or adding `remote_configuration.enabled: true` to your `datadog.yaml`.
+
+See the [Remote Configuration documentation][1] for detailed setup instructions across different deployment environments.
+
+### Polling interval
+
+The Agent polls Datadog for configuration updates at a configurable interval. This interval determines the average time between making a flag change in the UI and the change becoming available to your application.
+
+{{< code-block lang="bash" >}}
+# Optional: Configure polling interval (default: 60s)
+DD_REMOTE_CONFIGURATION_REFRESH_INTERVAL=10s
+{{< /code-block >}}
+
+[1]: /remote_configuration
+
+## Application configuration
+
+Configure your application with the standard Datadog environment variables. These are common across all server-side SDKs:
+
+{{< code-block lang="bash" >}}
+# Required: Service identification
+DD_SERVICE=<YOUR_SERVICE_NAME>
+DD_ENV=<YOUR_ENVIRONMENT>
+DD_VERSION=<YOUR_APP_VERSION>
+
+# Agent connection (if not using default localhost:8126)
+DD_AGENT_HOST=localhost
+DD_TRACE_AGENT_PORT=8126
+
+# Enable Remote Configuration in the tracer
+DD_REMOTE_CONFIG_ENABLED=true
+{{< /code-block >}}
+
+<div class="alert alert-info">Some SDKs require additional experimental flags to enable feature flagging. See the SDK-specific documentation for details.</div>
+
+## Further reading
+
+{{< partial name="whats-next/whats-next.html" >}}