refactor(evaluate): refreshed the Features content in the Evaluate section

docs/best-practices/multi-tenant-patterns.mdx

@@ -130,7 +130,7 @@ need its own service accounts, API keys, dashboards, or rate limits. If that is
 [Namespace best practices](/best-practices/managing-namespace) before committing to Namespace-per-tenant isolation.
 
 <RelatedReadContainer>
-  <RelatedReadItem path="/evaluate/development-production-features/multi-tenancy#namespace-isolation" text="Namespace Isolation in Temporal Cloud" archetype="cloud-guide" />
+  <RelatedReadItem path="/evaluate/features/multi-tenancy#namespace-isolation" text="Namespace Isolation in Temporal Cloud" archetype="cloud-guide" />
 </RelatedReadContainer>
 
 ### Pattern comparison
@@ -343,7 +343,7 @@ TenantId = 'customer-123' AND ExecutionStatus = 'Running'
 ## Related resources
 
 <RelatedReadContainer>
-  <RelatedReadItem path="/evaluate/development-production-features/multi-tenancy" text="Multi-tenancy Overview" archetype="feature-guide" />
+  <RelatedReadItem path="/evaluate/features/multi-tenancy" text="Multi-tenancy Overview" archetype="feature-guide" />
   <RelatedReadItem path="/cloud/limits" text="Temporal Cloud Limits" archetype="cloud-guide" />
   <RelatedReadItem path="/visibility" text="Visibility and Search Attributes" archetype="feature-guide" />
 </RelatedReadContainer>

docs/best-practices/pre-production-testing.mdx

@@ -234,7 +234,7 @@ Intentionally break or degrade downstream dependencies used by Activities:
 
 - [Workflow Versioning Strategies - Developer Corner](https://community.temporal.io/t/workflow-versioning-strategies/6911)
 - [Worker Versioning](/production-deployment/worker-deployments/worker-versioning)
-- [Replay Testing](/evaluate/development-production-features/testing-suite)
+- [Replay Testing](/evaluate/features/testing-suite)
 
 **What to test**
 
@@ -257,7 +257,7 @@ Intentionally break or degrade downstream dependencies used by Activities:
 
 - [Workflow Versioning Strategies - Developer Corner](https://community.temporal.io/t/workflow-versioning-strategies/6911)
 - [Worker Versioning](/production-deployment/worker-deployments/worker-versioning)
-- [Replay Testing](/evaluate/development-production-features/testing-suite)
+- [Replay Testing](/evaluate/features/testing-suite)
 
 **What to test**
 

docs/cli/setup-cli.mdx

@@ -97,7 +97,7 @@ extension using the following command:
 
 :::tip Support, stability, and dependency info
 
-The Temporal Cloud extension is in [Pre-release](/evaluate/development-production-features/release-stages#pre-release).
+The Temporal Cloud extension is in [Pre-release](/evaluate/features/release-stages#pre-release).
 APIs and configuration may change before the stable release.
 
 :::

docs/cloud/get-started/namespaces.mdx

@@ -254,7 +254,7 @@ key and mTLS authentication on the same Namespace, please contact
 :::info
 
 Using **both** API key and mTLS authentication on the **same** Namespace is in
-[pre-release](/evaluate/development-production-features/release-stages) and doesn't support
+[pre-release](/evaluate/features/release-stages) and doesn't support
 [High Availability features](/cloud/high-availability) or authenticating with an API Key to a Namespace Endpoint.
 
 :::

docs/cloud/high-availability/index.mdx

@@ -139,7 +139,7 @@ These are often major concerns for financial services, e-commerce, gaming, globa
 
 In selected regions, you can add a replica to a Namespace in the same region.
 Temporal operates a "cell architecture" and will replicate the Namespace across multiple cells in that region.
-This feature is currently in [Public Preview](/evaluate/development-production-features/release-stages) in selected regions.
+This feature is currently in [Public Preview](/evaluate/features/release-stages) in selected regions.
 
 Failovers between cells are always managed automatically by Temporal. Unlike Multi-region and Multi-cloud Replication, you cannot disable automatic failovers and you cannot trigger a manual failover for a Same-region Replication Namespace. See [Failovers](/cloud/high-availability/failovers) for details.
 

docs/demos/standalone-activities.mdx

@@ -20,7 +20,7 @@ import { StandaloneActivityDemo, ReleaseNoteHeader, SdkGuideLinks } from '@site/
   languages={["Go", "Python", "Java", ".NET", "TypeScript", "Ruby"]}
   guidePath="activities/standalone-activities"
 >
-  Available in [Temporal Cloud](/standalone-activity#temporal-cloud-support) and in the [Temporal CLI](/standalone-activity#temporal-cli-support) v1.7.0 or higher with Temporal Server v1.31.0 or higher. Java SDK support is in [Pre-release](/evaluate/development-production-features/release-stages#pre-release).
+  Available in [Temporal Cloud](/standalone-activity#temporal-cloud-support) and in the [Temporal CLI](/standalone-activity#temporal-cli-support) v1.7.0 or higher with Temporal Server v1.31.0 or higher. Java SDK support is in [Pre-release](/evaluate/features/release-stages#pre-release).
 </ReleaseNoteHeader>
 
 Standalone Activities let you run a single Activity straight from your application without

docs/develop/plugins-guide.mdx

@@ -195,7 +195,7 @@ requirements:
   meaning it produces the same commands and results when replayed. For example, don't call system time APIs, generate
   random values, or perform direct network and file I/O from Workflow-context code; move that work to Activities or
   Nexus Operations.
-- See [observability](/evaluate/development-production-features/observability) to avoid duplicating observation side
+- See [observability](/evaluate/features/observability) to avoid duplicating observation side
   effects when Workflows replay.
 - Put other side effects inside of Activities or [Local Activities](/local-activity). This helps your Workflow handle
   being restarted, resumed, or executed in a different process from where it originally began without losing correctness
@@ -212,7 +212,7 @@ queues and Workers.
 Users use Workflows for:
 
 - Orchestration and decision-making
-- Interactivity via [message-passing](/evaluate/development-production-features/workflow-message-passing)
+- Interactivity via [message-passing](/evaluate/features/workflow-message-passing)
 - Tracing and observability
 
 #### Making changes to your library

docs/develop/ruby/workflows/message-passing.mdx

@@ -316,7 +316,7 @@ To send an Update to a Workflow Execution, you can:
 
 :::tip Stability
 
-In [Public Preview](/evaluate/development-production-features/release-stages#public-preview) in Temporal Cloud.
+In [Public Preview](/evaluate/features/release-stages#public-preview) in Temporal Cloud.
 
 Minimum Temporal Server version [Temporal Server version 1.26](https://github.com/temporalio/temporal/releases/tag/v1.26.2)
 

docs/develop/rust/workers/worker-process.mdx

@@ -10,7 +10,7 @@ tags:
   - Worker
 ---
 
-The Rust SDK is in [Public Preview](/evaluate/development-production-features/release-stages#public-preview), and its API can change between releases.
+The Rust SDK is in [Public Preview](/evaluate/features/release-stages#public-preview), and its API can change between releases.
 The code on this page is written against `temporalio-sdk` 0.7.0.
 
 ## Create and run a Worker {/* #run-a-dev-worker */}

docs/encyclopedia/activities/activity-operations.mdx

@@ -35,7 +35,7 @@ support. Activity Operations don't apply to [Local Activities](/local-activity)
 
 :::note Public Preview
 
-Activity Operations are in [Public Preview](/evaluate/development-production-features/release-stages#public-preview).
+Activity Operations are in [Public Preview](/evaluate/features/release-stages#public-preview).
 Pause, Unpause, and Reset are available in Server v1.28.0+. Self-hosted UI requires v2.47.0+.
 
 Activity Operations aren't available as SDK client methods. They're operational controls designed for the CLI, UI, and

docs/encyclopedia/activities/standalone-activity.mdx

@@ -33,7 +33,7 @@ See [limitations](#public-preview-limitations) below.
 If you need to orchestrate multiple Activities, use a [Workflow](/workflows). But if you just need to
 execute a single Activity, use a Standalone Activity.
 
-Standalone Activities are Temporal’s [job queue](/evaluate/development-production-features/job-queue) -
+Standalone Activities are Temporal’s [job queue](/evaluate/features/job-queue) -
 the simplest way to run durable, retryable tasks on Temporal.
 
 <div style={{textAlign: 'center', margin: '2rem 0'}}>
@@ -69,7 +69,7 @@ Pick your SDK and follow the quickstart:
 ## Use cases
 
 Standalone Activities can be used for [durable job processing use
-cases](/evaluate/development-production-features/job-queue) such as sending an email, processing a
+cases](/evaluate/features/job-queue) such as sending an email, processing a
 webhook, syncing data, or executing a single function reliably with built-in retries and timeouts.
 
 ## Key features

docs/encyclopedia/workflow/workflow-pause.mdx

@@ -163,7 +163,7 @@ request ID.
 - Signals are accepted while Paused and processed after the Workflow is Unpaused.
 - Updates and Queries are rejected while Paused.
 - Cancel requests are recorded while Paused, but cancellation takes effect after the Workflow is Unpaused.
-- [Terminate](/evaluate/development-production-features/interrupt-workflow) requests still terminate the Workflow
+- [Terminate](/evaluate/features/interrupt-workflow) requests still terminate the Workflow
   immediately.
 - Resetting a Paused Workflow terminates the current Run and starts a new Run from the selected reset point.
 

docs/evaluate/features/index.mdx

@@ -0,0 +1,47 @@
+---
+id: index
+title: Temporal development and production features
+description: Leverage a Temporal SDK to develop robust applications featuring Workflows, Activities, Workers, testing suites, Temporal Clients, Scheduled Workflows, and advanced observability tools.
+sidebar_label: Features
+keywords:
+  - temporal sdk
+  - core application primitives
+  - workflows in temporal
+  - activities and workers
+  - temporal testing suite
+  - temporal clients
+  - scheduled workflows
+  - workflow cancellation
+  - runtime safeguards
+  - failure detection in temporal
+  - automatic retries
+  - temporal messages
+  - business process versioning
+  - observability in workflows
+  - debugging temporal applications
+  - data encryption in applications
+  - throughput composability
+  - signals
+  - queries
+---
+
+Through a Temporal SDK, Temporal provides a wide range of features that enable developers to build applications that serve a wide range of use cases.
+
+- **[Core application primitives](/evaluate/features/core-application)**: Develop and run your application with Workflows, Activities, and Workers.
+- **[Testing suite](/evaluate/features/testing-suite)**: Each Temporal SDK comes with a testing suite that enables developers to test their applications as they would any other.
+- **[Scheduled Workflows](/evaluate/features/schedules)**: Start a business process at a specific time or on a given time interval.
+- **[Interrupt a Workflow](/evaluate/features/interrupt-workflow)**: Cancel or terminate a business process (Workflow) that is already in progress and compensate for any steps already taken.
+- **Runtime safeguards**: Prevent avoidable errors and issues from executing during runtime.
+- **[Failure detection and mitigation](/evaluate/features/failure-detection)**: Detect failures with timeouts and configure automatic retries to mitigate them.
+- **[Temporal Nexus](/evaluate/nexus)**: Connect Temporal Applications across (and within) isolated Namespaces for improved modularity, security, debugging, and fault isolation. Nexus supports cross-team, cross-domain, and multi-region use cases.
+- **[Workflow message passing](/evaluate/features/workflow-message-passing)**: Build responsive applications that react to events at runtime and enable data retrieval from ongoing Workflows.
+- **Versioning**: Support multiple versions of your business logic for long-running business processes.
+- **[Observability](/evaluate/features/observability)**: List business processes, view their state, and set up dashboards with metrics.
+- **[Debugging](/evaluate/features/debugging)**: Surface errors and step through code to find issues.
+- **[Data encryption](/evaluate/features/data-encryption)**: Transform data and protect the privacy of the users of your application.
+- **[Throughput composability](/evaluate/features/throughput-composability)**: Breakup business processes by data streams, team ownership, or other organization factors.
+- **[Cloud Automation](/evaluate/features/cloud-automation)**: Simplify cloud management and boost security with Temporal's Cloud Automation.
+- **[Low Latency](/evaluate/features/low-latency)**: Making your applications faster, more performant, and more efficient.
+- **[Multi-tenancy](/evaluate/features/multi-tenancy)**: Enhances efficiency and cost-effectiveness.
+
+For detailed information on Temporal feature release stages and criteria, see this [Product Release Stages Guide](/evaluate/features/release-stages).

docs/evaluate/index.mdx

@@ -20,7 +20,7 @@ Applications benefit from fault-tolerance and execution guarantees.
 Thousands of companies of all sizes are leveraging Temporal's capabilities for both mission critical and standard workloads.
 
 - [Why Temporal](/evaluate/why-temporal)
-- [Development and production features](/evaluate/development-production-features)
+- [Development and production features](/evaluate/features)
 - [Use cases](/evaluate/use-cases-design-patterns)
 - [Temporal Cloud](/cloud)
 - [Security](/security)

docs/glossary.md

@@ -254,7 +254,7 @@ responsible for rate limiting, authorizing, validating, and routing all inbound
 
 <!-- _Tags: [term](/tags/term)_ -->
 
-#### [General Availability](/evaluate/development-production-features/release-stages#general-availability)
+#### [General Availability](/evaluate/features/release-stages#general-availability)
 
 Learn more about the General Availability release stage
 
@@ -475,13 +475,13 @@ A Payload Converter serializes data, converting objects or values to bytes and b
 
 <!-- _Tags: [term](/tags/term), [explanation](/tags/explanation)_ -->
 
-#### [Pre-release](/evaluate/development-production-features/release-stages#pre-release)
+#### [Pre-release](/evaluate/features/release-stages#pre-release)
 
 Learn more about the Pre-release stage
 
 <!-- _Tags: [product-release-stages](/tags/product-release-stages), [term](/tags/term)_ -->
 
-#### [Public Preview](/evaluate/development-production-features/release-stages#public-preview)
+#### [Public Preview](/evaluate/features/release-stages#public-preview)
 
 Learn more about the Public Preview release stage
 

docs/production-deployment/self-hosted-guide/checklist.mdx

@@ -23,7 +23,7 @@ This page covers common challenges you'll face when self-hosting Temporal for pr
 
 :::note
 
-This guide covers self-hosted deployments. If you're weighing self-hosting against a managed offering, see [Temporal Cloud vs. self-hosted Temporal](/evaluate/development-production-features/cloud-vs-self-hosted-features).
+This guide covers self-hosted deployments. If you're weighing self-hosting against a managed offering, see [Temporal Cloud vs. self-hosted Temporal](/evaluate/features/cloud-vs-self-hosted-features).
 
 :::