Conversation
| @@ -0,0 +1,610 @@ | |||
| # **Cookbook: Deploying UC For The First Time** | |||
There was a problem hiding this comment.
How do we describe what UC is?
There was a problem hiding this comment.
It's described on line 5ff. is that not sufficient?
docs/cookbook-first-time-use.md
Outdated
|
|
||
| Due to its nature, the operating system does not come with a standard package manager (e.g. zypper). Installation and updates are done using container native workflows and artifacts, not standard system management processes. This keeps “pristinity” as one of its core concepts, prevents tampering, and allows for seamless, atomic, containerized-based updates that favor repeatability. | ||
|
|
||
| ### Kubernetes {#kubernetes} |
There was a problem hiding this comment.
The section formatting is broken. There are few other similar occurrences.
It also breaks the Glossary links.
There was a problem hiding this comment.
This is the formatting to add a persistent custom anchor. By default, Markdown parsers generate IDs based on the text (e.g., #example-overview). This syntax allows you to manually define the ID so it remains stable even if you change the heading text later (e.g., to ## Project Summary {#example-overview}). You can link directly to this section from elsewhere in the document or from another page using Link Text.
the glossary is somehow out of place. there is no support for footnotes in markdown so I'll delete them.
This can be used for early access external users.
This can be used for early access external users.