feat: reworked add cv#703
Conversation
- Add theme-aware Mermaid rendering with dynamic updates on theme changes - Reworked add cv to be more approachable Signed-off-by: Jakob Möller <contact@jakob-moeller.com>
✅ Deploy Preview for open-component-model ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
looks great! Also the extension of the baseof.html makes absolutely no sense sense. I took over all new style and structure tips into the new templates we created with #713 and #714. There are some issue with relative links that should get a replacement by relref and a minor conflict. Besides that, 👍🏻👍🏻👍🏻 |
| ``` | ||
|
|
||
| The command [`ocm add component-version`]({{< relref "ocm_add_component-version.md" >}}) directly creates a component version from a `component-constructor.yaml` file and stores it in a local CTF archive. | ||
| Component versions are created using a `component-constructor.yaml` file that describes components and their artifacts. The OCM CLI builds these into a [Common Transport Format (CTF)](https://github.com/open-component-model/ocm-spec/blob/main/doc/04-extensions/03-storage-backends/ctf.md) archive, which can then be transferred to any OCI registry |
There was a problem hiding this comment.
| Component versions are created using a `component-constructor.yaml` file that describes components and their artifacts. The OCM CLI builds these into a [Common Transport Format (CTF)](https://github.com/open-component-model/ocm-spec/blob/main/doc/04-extensions/03-storage-backends/ctf.md) archive, which can then be transferred to any OCI registry | |
| Component versions are created using a `component-constructor.yaml` file that describes components and their artifacts. The OCM CLI builds these into a local [Common Transport Format (CTF)](https://github.com/open-component-model/ocm-spec/blob/main/doc/04-extensions/03-storage-backends/ctf.md) archive, which can then be transferred to any OCI registry |
| OCM supports various ways to include resource artifacts in your components via `resources`. | ||
|
|
||
| A resource is described either by its access information to a remote repository or by locally provided resources. | ||
| **Use `input` to embed content directly, or `access` to reference external artifacts.** |
There was a problem hiding this comment.
| **Use `input` to embed content directly, or `access` to reference external artifacts.** | |
| Use **`input`** to embed content directly, or **`access`** to reference external artifacts. |
| OCM uses a double-slash (`//`) notation to separate the repository from the component path: | ||
|
|
||
| To list all versions of a component, only specify the component name and skip the version. Let us view all versions of the component with the name `ocm.software/demos/podinfo`, which is stored in the the OCM repository `ghcr.io/open-component-model`: | ||
| - **Local CTF**: `./transport-archive//github.com/acme.org/helloworld:1.0.0` |
There was a problem hiding this comment.
| - **Local CTF**: `./transport-archive//github.com/acme.org/helloworld:1.0.0` | |
| - Local Archive (CTF): `./transport-archive//github.com/acme.org/helloworld:1.0.0` |
|
|
||
| To list all versions of a component, only specify the component name and skip the version. Let us view all versions of the component with the name `ocm.software/demos/podinfo`, which is stored in the the OCM repository `ghcr.io/open-component-model`: | ||
| - **Local CTF**: `./transport-archive//github.com/acme.org/helloworld:1.0.0` | ||
| - **Remote OCI Registry**: `ghcr.io/open-component-model/ocm//ocm.software/ocmcli:0.17.0` |
There was a problem hiding this comment.
| - **Remote OCI Registry**: `ghcr.io/open-component-model/ocm//ocm.software/ocmcli:0.17.0` | |
| - Remote Registry (OCI): `ghcr.io/open-component-model/ocm//ocm.software/ocmcli:0.17.0` |
| {{< card-grid >}} | ||
| {{< link-card | ||
| title="Sign Component Versions" | ||
| description="Add cryptographic signatures for authenticity." | ||
| href="../sign-component-version" | ||
| >}} | ||
| {{< link-card | ||
| title="Download Resources" | ||
| description="Extract resources from component versions." | ||
| href="../download-resources-from-component-versions" | ||
| >}} | ||
| {{< /card-grid >}} |
There was a problem hiding this comment.
We should check how a "next steps" section should be formatted, as this card grid is exactly the same the doks scheme uses for the prev/next page view. Maybe a standard list fits better?
…e "download resources" doc to how-to section On-behalf-of: Gerald Morrison (SAP) <gerald.morrison@sap.com> Signed-off-by: Gerald Morrison (SAP) <gerald.morrison@sap.com>
|
superseeded by #733 |
…ture (#733) <!-- markdownlint-disable MD041 --> #### What this PR does / why we need it - Rework getting started guides following the example from #703 . - Move "download resources" doc from getting-started to how-to section. - Delete sign and verify component from the getting started (will be reworked into how-tos as part of open-component-model/ocm-project#886 - Enhance baseof.html layout to allow mermaid diagrams in our docs. This PR superseeds #703 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Major rework of getting-started guides into stepwise tutorials with expanded examples, troubleshooting, estimated times; several older signing/verification pages removed and a consolidated "Download Resources" how‑to added. * **New Features** * Mermaid diagram rendering improved with theme auto-detection (light/dark) and dynamic re-rendering on theme changes. * **Chores** * Site layout and navigation adjusted; repository ignore patterns updated to include a new ignore file. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Signed-off-by: Gerald Morrison (SAP) <gerald.morrison@sap.com> Signed-off-by: Gerald Morrison <67469729+morri-son@users.noreply.github.com> Co-authored-by: Gerald Morrison (SAP) <gerald.morrison@sap.com> Co-authored-by: Piotr Janik <piotrjanik@nautilia.pl>
…ture (#733) <!-- markdownlint-disable MD041 --> #### What this PR does / why we need it - Rework getting started guides following the example from #703 . - Move "download resources" doc from getting-started to how-to section. - Delete sign and verify component from the getting started (will be reworked into how-tos as part of open-component-model/ocm-project#886 - Enhance baseof.html layout to allow mermaid diagrams in our docs. This PR superseeds #703 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Major rework of getting-started guides into stepwise tutorials with expanded examples, troubleshooting, estimated times; several older signing/verification pages removed and a consolidated "Download Resources" how‑to added. * **New Features** * Mermaid diagram rendering improved with theme auto-detection (light/dark) and dynamic re-rendering on theme changes. * **Chores** * Site layout and navigation adjusted; repository ignore patterns updated to include a new ignore file. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Signed-off-by: Gerald Morrison (SAP) <gerald.morrison@sap.com> Signed-off-by: Gerald Morrison <67469729+morri-son@users.noreply.github.com> Co-authored-by: Gerald Morrison (SAP) <gerald.morrison@sap.com> Co-authored-by: Piotr Janik <piotrjanik@nautilia.pl> 08179b0
What this PR does / why we need it
While im currently reworking the website documentation I really struggled to follow the most basic guide we have. Thats why I set out to rework it into a "guide" approach that is much more easy to digest (at least imo) and has more collapsible sections that hide unneeded information if people dont want to dive deeper. It also adds Add theme-aware Mermaid rendering with dynamic updates on theme changes.
Which issue(s) this PR is related to
Part of smaller docs reworks that I didnt want to push as part of diataxis rework in open-component-model/ocm-project#841