Add initial changes to the what is OpenChoreo page

Author: sameerajayasoma

docs/overview/what-is-openchoreo.mdx

@@ -7,76 +7,44 @@ import Link from '@docusaurus/Link';
 import {versions} from '../_constants.mdx';
 
 # What is OpenChoreo?
+=======
+OpenChoreo is a complete, open-source Internal Developer Platform (IDP) designed for platform engineering (PE) teams who want to streamline developer workflows and deliver Internal Developer Portals without having to build everything from scratch.
 
-OpenChoreo is an open-source Internal Developer Platform (IDP) that makes Kubernetes accessible to development teams. It
-provides a complete platform engineering solution that transforms complex infrastructure into simple, self-service
-developer experiences.
+OpenChoreo orchestrates many CNCF and other projects to give a comprehensive framework for PE teams to build the platform they want.
 
-OpenChoreo brings the best ideas from [WSO2 Choreo](https://choreo.dev) (an enterprise IDP) to the open-source
-community.
+## Why OpenChoreo?
 
-## Who Should Use OpenChoreo?
+Kubernetes gives you powerful primitives like Namespaces, Deployments, CronJobs, Services and NetworkPolicies—but they are too low-level for most developers.
 
-OpenChoreo is designed for:
+This creates gap: **Platform engineers are left to build the real platform** defining higher-level APIs for developers and integrating tools for security, CI/CD, observability and operational guardrails. 
 
-- **Platform Engineering Teams** building internal developer platforms on Kubernetes
-- **DevOps Teams** looking to standardize deployments and reduce operational overhead
-- **Development Teams** wanting self-service deployment without infrastructure complexity
-- **Organizations** seeking to accelerate cloud-native adoption while maintaining security and compliance
+**OpenChoreo fills that gap.** It provides all essentional building blocks of an IDP, including:
+- **High-level APIs** for modeling cloud-native applications
+- A **Control Plane** that understands and enforces these APIs with GitOps support
+- A **built-in CI system**
+- An **opinionated Data Plane** with runtime enforcement of design-time semantics 
+- Built-in **Security**, **networking** and **observability** integrations
 
-## The Problem
+With OpenChoreo, we are bringing the best ideas of [WSO2 Choreo](https://choreo.dev) (an IDP as a Service) to the open-source community. WSO2 Choreo is designed not just to automate software delivery workflows, but to support engineering best practices: enforcing architecture standards, promoting service reuse, and integrating API management and observability.
 
-Modern cloud-native development has become unnecessarily complex:
+## OpenChoreo Components
 
-- **Kubernetes is powerful but overwhelming**: Developers need to understand pods, services, ingress, ConfigMaps, and
-  dozens of other concepts just to deploy a simple application
-- **Every team reinvents the wheel**: Without standards, each team creates their own deployment patterns, leading to
-  inconsistency and technical debt
-- **Security is an afterthought**: Teams often sacrifice security for speed, leaving applications vulnerable
-- **Platform building is expensive**: Companies spend months or years building internal platforms from scratch
+OpenChoreo is made up of several key components that work together to deliver a complete IDP. 
 
-## How OpenChoreo Solves It
+<!-- ![](../resources/openchoreo_components.svg) -->
 
-OpenChoreo provides a layered approach with clear separation between platform engineering and development:
+- **Platform API** - Declarative interfaces used by platform engineers to configure and manage OpenChoreo installation.  
+- **Developer API** - Simplified, self-service interfaces for developers to model, deploy and managed to the full SDLC of cloud-native applications, without needing to understand platform internals. 
+- **Control Plane** - The orchestration layer that watch developer and platform APIs, validates configurations and translate them into Kubernetes-native and cloud-native infrastructure.
+- **Data Plane** - The execution environment for applications that is built on Kubernetes and extended with Cilium, Envoy Gateway and other CNCF tools. Data Plane is where runtime semantics are enforced.
+- **CI Plane** - A built-in CI engine powered by Argo Workflows. It builds the container images, runs tests and publishes artifacts. It is an optional plane. 
+- **Observability Plane** - Out-of-the-box visibility with logs, metrics and traces, using tools like Prometheus, Fluent Bit and OpenSearch. 
 
-**For Platform Engineers:**
-
-- Set up **Data**, **Build**, and **Observability Planes** for infrastructure separation
-- Define **Organizations** for multi-tenant isolation
-- Configure **Environments** on DataPlanes
-- Create **Classes** (ServiceClass, WebApplicationClass) to enforce standards
-- Configure **DeploymentPipelines** for promotion workflows
-
-**For Developers:**
-
-- Create **Projects** to organize related services (aligned with DDD bounded contexts)
-- Define **Components** for applications
-- Specify **Workloads** with runtime configurations
-- Deploy **applications** (Services, WebApplications, ScheduledTasks) using platform Classes
-
-The platform automatically handles the complexity of Kubernetes, including:
-
-- [Cell-based isolation](https://github.com/wso2/reference-architecture/blob/master/reference-architecture-cell-based.md)
-  with zero-trust networking
-- Automatic mTLS for all service communication
-- Built-in observability and distributed tracing
-- CI/CD pipelines with GitOps workflows
-- RBAC and access control
-
-## What Makes OpenChoreo Different
-
-- **Kubernetes Native**: Built as operators extending Kubernetes, not a layer on top
-- **Complete Solution**: Includes build, deploy, networking, API management, and observability—not just a UI
-- **Open Source**: No vendor lock-in, transparent development, community-driven
-- **Separation of Concerns**: Platform engineers define standards through Classes, developers express intent through
-  Claims
-
-Built on proven CNCF projects including Cilium (eBPF networking), Buildpacks, Argo (workflows), and Envoy Gateway (API
-management).
+Learn more about how these components fit together in the [OpenChoreo Architecture](./architecture.md) section.
 
 ## Current Status
 
-OpenChoreo is currently in **active development** (v1alpha1). While the core platform is functional, APIs may change as
+OpenChoreo is currently in **active development**. While the core platform is functional, APIs may change as
 we incorporate community feedback. We recommend starting with non-production workloads as you evaluate the platform.
 
 See our [Roadmap](https://github.com/orgs/openchoreo/projects/4) for upcoming features and stable release timeline.
@@ -92,9 +60,17 @@ Ready to try OpenChoreo? Start here:
 
 ## Community
 
-OpenChoreo is an open-source project that welcomes contributions. Join our community:
+We’d love for you to be part of OpenChoreo’s journey! Whether you’re fixing a bug, improving documentation, or suggesting new features, every contribution counts.
 
+<<<<<<< HEAD:docs/overview/what-is-openchoreo.mdx
 - [GitHub Discussions](https://github.com/openchoreo/openchoreo/discussions) for questions and ideas
 - [Discord](https://discord.com/invite/asqDFC8suT) for real-time chat
 - <Link to={`https://github.com/openchoreo/openchoreo/blob/${versions.githubRef}/docs/contributors/contribute.md`}>Contributing Guide</Link> to get
   involved
+=======
+- [Contributor Guide](https://github.com/openchoreo/openchoreo/blob/main/docs/contributors/contribute.md) – Learn how to get started.
+- [Report an Issue](https://github.com/openchoreo/openchoreo/issues) – Help us improve OpenChoreo.
+- [Join our Discord](https://discord.com/invite/asqDFC8suT) – Be part of the community.
+
+We’re excited to have you onboard!
+>>>>>>> e2802bd (Add initial changes to the what is OpenChoreo page):docs/overview/what-is-openchoreo.md