Skip to content

Fix list rendering issue in the architecture page #106

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 4, 2025
Merged

Fix list rendering issue in the architecture page #106

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/overview/architecture.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,11 +29,11 @@ Each plane in OpenChoreo operates as a distinct functional unit, with its own li
The brain of OpenChoreo. It watches developer- and platform-defined CRDs, validates and processes them, and coordinates activities across other planes. It translates intent such as "deploy this component" or "connect these services" into concrete infrastructure actions.

Responsibilities include:
• Validating CRD instances and resolving references (e.g., Connections between Components)
• Applying policy and environment-specific rules
• Coordinating CI jobs, deployments, and observability configurations
• Reconciling desired state with actual state across all planes
• Tracking the state of Components across environments and Data Planes
- Validating CRD instances and resolving references (e.g., Connections between Components)
- Applying policy and environment-specific rules
- Coordinating CI jobs, deployments, and observability configurations
- Reconciling desired state with actual state across all planes
- Tracking the state of Components across environments and Data Planes

The Control Plane is extensible, allowing integration with different backends for image building, observability tooling, environment provisioning, and more.

Expand Down
2 changes: 1 addition & 1 deletion docs/overview/what-is-openchoreo.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ import {versions} from '../_constants.mdx';
# What is OpenChoreo?
OpenChoreo is a comprehensive, 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 orchestrates many CNCF and other projects to provide a comprehensive framework for PE teams to build the platform they want.
OpenChoreo orchestrates many CNCF and other projects to give platform teams a strong head start, you can use it as-is, or tailor it to fit your own internal developer platform vision.

## Why OpenChoreo?

Expand Down
12 changes: 6 additions & 6 deletions versioned_docs/version-v0.3.x/overview/architecture.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ OpenChoreo is architected as a modular, Kubernetes-native control plane that int
The Control Plane acts as the orchestrator, transforming high-level platform and developer intent into actionable workloads deployed across Data Planes, while wiring them into the Observability Plane for visibility.

The diagram below illustrates how these components interact.
xz

![](../resources/openchoreo_components.svg)

Each plane in OpenChoreo operates as a distinct functional unit, with its own lifecycle, scaling behavior, and security boundaries. Together, these planes and supporting interfaces form the core components of the platform:
Expand All @@ -29,11 +29,11 @@ Each plane in OpenChoreo operates as a distinct functional unit, with its own li
The brain of OpenChoreo. It watches developer- and platform-defined CRDs, validates and processes them, and coordinates activities across other planes. It translates intent such as "deploy this component" or "connect these services" into concrete infrastructure actions.

Responsibilities include:
• Validating CRD instances and resolving references (e.g., Connections between Components)
• Applying policy and environment-specific rules
• Coordinating CI jobs, deployments, and observability configurations
• Reconciling desired state with actual state across all planes
• Tracking the state of Components across environments and Data Planes
- Validating CRD instances and resolving references (e.g., Connections between Components)
- Applying policy and environment-specific rules
- Coordinating CI jobs, deployments, and observability configurations
- Reconciling desired state with actual state across all planes
- Tracking the state of Components across environments and Data Planes

The Control Plane is extensible, allowing integration with different backends for image building, observability tooling, environment provisioning, and more.

Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-v0.3.x/overview/what-is-openchoreo.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ import {versions} from '../_constants.mdx';
# What is OpenChoreo?
OpenChoreo is a comprehensive, 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 orchestrates many CNCF and other projects to provide a comprehensive framework for PE teams to build the platform they want.
OpenChoreo orchestrates many CNCF and other projects to give platform teams a strong head start, you can use it as-is, or tailor it to fit your own internal developer platform vision.

## Why OpenChoreo?

Expand Down