-
Notifications
You must be signed in to change notification settings - Fork 14
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Split ALP into 2 DC files for products bedrock & micro (#101)
* Removed old DC file, created 2nd DC file for ALP * productname entities reworked
- Loading branch information
Showing
30 changed files
with
246 additions
and
5,501 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
# | ||
# | ||
|
||
MAIN="xml/ALP.asm.xml" | ||
ASSEMBLY="yes" | ||
# ASSEMBLY_DIR="xml" | ||
|
||
STYLEROOT="/usr/share/xml/docbook/stylesheet/suse2022-ns" | ||
DOCBOOK5_RNG_URI="http://docbook.org/xml/5.2/rng/docbookxi.rng" | ||
PROFOS="alp-bedrock" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -10,94 +10,96 @@ | |
xmlns="http://docbook.org/ns/docbook" | ||
xmlns:xi="http://www.w3.org/2001/XInclude" | ||
xmlns:xlink="http://www.w3.org/1999/xlink" > | ||
<info> | ||
<title>The &alp; Guide</title> | ||
<dm:docmanager xmlns:dm="urn:x-suse:ns:docmanager"> | ||
<dm:bugtracker> | ||
<dm:url>https://bugzilla.suse.com/enter_bug.cgi</dm:url> | ||
<dm:component>Documentation</dm:component> | ||
<dm:product>ALP</dm:product> | ||
<dm:assignee>[email protected]</dm:assignee> | ||
</dm:bugtracker> | ||
<!-- 2022-11-07 toba: removing for now | ||
<dm:editurl>https://github.com/SUSE/doc-modular/edit/main/xml/</dm:editurl> | ||
--> | ||
<dm:translation>no</dm:translation> | ||
</dm:docmanager> | ||
<!-- can we try to use the same date format here as in other docs? how can we use the | ||
<date><?dbtimestamp format="B d, Y"?></date> | ||
format here? --> | ||
<pubdate> | ||
<!-- enter the original publishing date --> | ||
</pubdate> | ||
<meta name="updated" content="enter ISO date of last update as YYYY-MM-DD" /> | ||
<meta name="time-to-read" content="enter time to read in minutes" /> | ||
<meta name="bugtracker"><phrase role="url">https://bugzilla.suse.com/enter_bug.cgi</phrase><phrase role="component">Non-product-specific documentation</phrase><phrase role="product">Smart Docs</phrase><phrase role="assignee">[email protected]</phrase> | ||
</meta> | ||
<meta name="translation"><phrase role="trans">no</phrase><phrase role="language" > | ||
<!-- comma-separated list of languages, for example en-us,de-de,cs-cz --></phrase> | ||
</meta> | ||
<meta name="refers-to" content="enter id of parent chapter or article" /> | ||
<meta name="architecture" content="" /> | ||
<meta name="&alp;"><productname version="1">&alp;</productname> | ||
</meta> | ||
<meta name="title">&alp;</meta> | ||
<meta name="description" >The &alp; (&alpshort;) is a lightweight operating system. Instead of applications distributed in traditional software packages, it runs containerized and virtualized workloads.</meta> | ||
<meta name="social-descr"></meta> | ||
<meta name="targetgroup" content="" /> | ||
<meta name="function" content="" /> | ||
<meta name="task" content="" /> | ||
<meta name="category" content="" /> | ||
<!-- <xi:include href="common_copyright_gfdl.xml"/>--> | ||
<abstract> | ||
<para> | ||
This guide introduces the &alp; (&alpshort;)—its deployment, system | ||
management and software installation as well as running of containerized | ||
workloads. To enhance this &alpshort; documentation, find its sources at | ||
<link xlink:href="https://github.com/SUSE/doc-modular/edit/main/xml/"/>. | ||
</para> | ||
<variablelist> | ||
<varlistentry> | ||
<term>WHAT?</term> | ||
<listitem> | ||
<info> | ||
<title>The &productname; Guide</title> | ||
<dm:docmanager xmlns:dm="urn:x-suse:ns:docmanager"> | ||
<dm:bugtracker> | ||
<dm:url>https://bugzilla.suse.com/enter_bug.cgi</dm:url> | ||
<dm:component>Documentation</dm:component> | ||
<dm:product></dm:product> | ||
<dm:assignee>[email protected]</dm:assignee> | ||
</dm:bugtracker> | ||
<!-- 2022-11-07 toba: removing for now | ||
<dm:editurl>https://github.com/SUSE/doc-modular/edit/main/xml/</dm:editurl> | ||
--> | ||
<dm:translation>no</dm:translation> | ||
</dm:docmanager> | ||
<!-- can we try to use the same date format here as in other docs? how can we use the | ||
<date><?dbtimestamp format="B d, Y"?></date> | ||
format here? --> | ||
<pubdate> | ||
<!-- enter the original publishing date --> | ||
</pubdate> | ||
<meta name="updated" content="enter ISO date of last update as YYYY-MM-DD" /> | ||
<meta name="time-to-read" content="enter time to read in minutes" /> | ||
<meta name="bugtracker"><phrase role="url">https://bugzilla.suse.com/enter_bug.cgi</phrase><phrase role="component">Non-product-specific documentation</phrase><phrase role="product">Smart Docs</phrase><phrase role="assignee">[email protected]</phrase> | ||
</meta> | ||
<meta name="translation"><phrase role="trans">no</phrase><phrase role="language" > | ||
<!-- comma-separated list of languages, for example en-us,de-de,cs-cz --></phrase> | ||
</meta> | ||
<meta name="refers-to" content="enter id of parent chapter or article" /> | ||
<meta name="architecture" content="" /> | ||
<meta name="productname"><productname version="1">&productname;</productname> | ||
</meta> | ||
<meta name="title">&productname;</meta> | ||
<meta name="description" >The &productname; (&productnameshort;) is a lightweight operating system. Instead of applications distributed in traditional software packages, it runs containerized and virtualized workloads.</meta> | ||
<meta name="social-descr"></meta> | ||
<meta name="targetgroup" content="" /> | ||
<meta name="function" content="" /> | ||
<meta name="task" content="" /> | ||
<meta name="category" content="" /> | ||
<!-- <xi:include href="common_copyright_gfdl.xml"/>--> | ||
<abstract> | ||
<para> | ||
&alpshort; is a lightweight operating system. Instead of | ||
applications distributed in traditional software packages, it runs | ||
containerized and virtualized workloads. | ||
This guide introduces the &productname; (&productnameshort;)—its deployment, | ||
system management and software installation as well as running of | ||
containerized workloads. To enhance this &productnameshort; documentation, find | ||
its sources at | ||
<link xlink:href="https://github.com/SUSE/doc-modular/edit/main/xml/"/>. | ||
</para> | ||
</listitem> | ||
</varlistentry> | ||
<varlistentry> | ||
<term>WHY?</term> | ||
<listitem> | ||
<para> | ||
This guide introduces an overview of what &alpshort; is and how it is | ||
different from traditional operating systems. It also describes how to | ||
administer &alpshort; and install and manage individual workloads. | ||
</para> | ||
</listitem> | ||
</varlistentry> | ||
<varlistentry> | ||
<term>EFFORT?</term> | ||
<listitem> | ||
<para> | ||
To understand the concepts and perform tasks described in this guide, | ||
you need to have good knowledge and practice with the Linux | ||
operating system. | ||
</para> | ||
</listitem> | ||
</varlistentry> | ||
<varlistentry> | ||
<term>GOAL!</term> | ||
<listitem> | ||
<para> | ||
After having read this guide, you will be able to deploy &alpshort;, | ||
modify its file system in a transactional way, and install and run | ||
specific workloads on top of it. | ||
</para> | ||
</listitem> | ||
</varlistentry> | ||
</variablelist> | ||
</abstract> | ||
</info> | ||
<variablelist> | ||
<varlistentry> | ||
<term>WHAT?</term> | ||
<listitem> | ||
<para> | ||
&productnameshort; is a lightweight operating system. Instead of | ||
applications distributed in traditional software packages, it | ||
runs containerized and virtualized workloads. | ||
</para> | ||
</listitem> | ||
</varlistentry> | ||
<varlistentry> | ||
<term>WHY?</term> | ||
<listitem> | ||
<para> | ||
This guide introduces an overview of what &productnameshort; is and how | ||
it is different from traditional operating systems. It also | ||
describes how to administer &productnameshort; and install and manage | ||
individual workloads. | ||
</para> | ||
</listitem> | ||
</varlistentry> | ||
<varlistentry> | ||
<term>EFFORT?</term> | ||
<listitem> | ||
<para> | ||
To understand the concepts and perform tasks described in this | ||
guide, you need to have good knowledge and practice with the | ||
Linux operating system. | ||
</para> | ||
</listitem> | ||
</varlistentry> | ||
<varlistentry> | ||
<term>GOAL!</term> | ||
<listitem> | ||
<para> | ||
After having read this guide, you will be able to deploy | ||
&productnameshort;, modify its file system in a transactional way, and | ||
install and run specific workloads on top of it. | ||
</para> | ||
</listitem> | ||
</varlistentry> | ||
</variablelist> | ||
</abstract> | ||
</info> | ||
</book> |
Oops, something went wrong.