RNG: Refactor Product/Portal Schema

### Situation

As discussed in [Meeting Portal Datamodel](https://confluence.suse.com/x/0QB5e), some structures in the RNC need to be change. The RNC schema needs to be adjusted to make it flexible for our upcoming use cases.


### Use Case

The RNC schema served us well, but we have now use cases we need to cover:

* CN and MLM teams need to be able to write a `<product>` or `<docset>` as root elements in their files.
* We need to reference to internal HTML documents that are not being built by DAPS.
* Having XIncludes on specific sections may help to modularize the config file.
* Translations need to be collected by language, not other groups.


### Possible Implementation

The RNC schema need to refactored in certain ways:

#### General
* [x] Add DocBook tags to document the important parts in the RNG schema. This can be extracted to create a public documentation.
* [x] Include XInclude.


#### `<portal>` Content model changes

* [x] Use `<portal>` as root element.
* [x] Allow more start elements (not only `<product>`).
* [ ] Add new `portal/categories` element
* [x] Add new `portal/productfamilies` element
* [x] Add new `portal/series` element


#### `<product>` Content model changes

* [x] Allow a wrapper element `<descriptions>` that holds multiple <desc> elements.
* [x] Add a new `series` attribute.
* [x] Add a new `family` attribute.
* [x] Add a new `rank` attribute. This determines the order of the product tile on the homepage.
* [ ] Allow XInclude elements on the `docset` level
* [ ] Add `<categories>` to allow local categories
* [ ] Remove `site-sections` 
* [ ] Add new `series` attribute


#### `<docset>` Content model changes

* [x] Rename `<overridedesc>` to `<description>`

#### `<categories>` and `<category>` Content model changes

* [x] Add a new `<categories>` element
* [ ] Group `<category>` for language, not category ID. For example:

  ```xml
  <category lang="en-us" default="true">
    <entry categoryid="about" title="About" />
    <entry categoryid="deployment" title="Deployment" />
    <entry categoryid="inital-config" title="Initial configuration" />
    
  </category>
  ```


#### `<deliverable>` Content model changes
* [ ] Add `<html>` (name subject to change) as a sibling of `<dc>`. These are internal documentation that are marked as "external" because we haven't the capabilities to do so.
  The content model would look like:

  ```rnc
  ds.html := element html {
     attribute id { IDREF },
     ds.title,
     ds.subtitle?,
     ds.desc+,
     ds.link
  }
  ```

  Possible names: `<resource>`, `<document>`, `<doc>`, `<entry>`, or `<item>`. Or create a more general element that can contain both types?

### `<internal>` and `<external>` Content model changes
* [ ] Allow `descriptions` in internal links to customize descriptions:

  ```xml
  <internal>
    
    <ref product="sle-micro" docset="5.5" dc="DC-SLE-Micro-Admin" category="best-practices" titleformat="title subtitle">
      <descriptions> ... </descriptions>
    </ref>
  </internal>
  ```

* [ ] Allow `descriptions` in external links:

  ```xml
  <external>
    <link category="about" gated="true | false">
      <url href="..." format="html | pdf | ..." />
      <descriptions>
        <desc lang="en-us">
           <title>The title</title>
           
        </desc>
        
      </descriptions>
    </link>
  </external>
  ```

### Removed Content models

Some elements which aren't used or not really useful anymore:

* [ ] Remove `ds.deliverablerestricted`
* [x] Remove `ds.param`
* [x] Remove `ds.buildcontainer` (including `ds.type.hexdigest` and `ds.type.containerref`)


Some attributes which aren't used or not really useful anymore:
* [x] Remove `meta`
* [ ] Remove `includes-productname`
* [x] Remove `translation-type`


#### Other Content model changes

* [ ] Should we simplify the `language` element in regards to the `translation-type` attribute?
* [ ] Do we need a `<metadata>` element somewhere?

* [x] Change the `<ref/>` element to allow to point to any deliverable file:

  ```xml
  <ref product="cloudnative" docset="storage" deliverable="cn-storage-concepts"/>
  ```

  => Can we consolidate that and don't distinguish between DC and HTML anymore? Maybe a more general `entryref` attribute?

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

RNG: Refactor Product/Portal Schema #187

Situation

Use Case

Possible Implementation

General

`<portal>` Content model changes

`<product>` Content model changes

`<docset>` Content model changes

`<categories>` and `<category>` Content model changes

`<deliverable>` Content model changes

`<internal>` and `<external>` Content model changes

Removed Content models

Other Content model changes

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

RNG: Refactor Product/Portal Schema #187

Description

Situation

Use Case

Possible Implementation

General

<portal> Content model changes

<product> Content model changes

<docset> Content model changes

<categories> and <category> Content model changes

<deliverable> Content model changes

<internal> and <external> Content model changes

Removed Content models

Other Content model changes

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

`<portal>` Content model changes

`<product>` Content model changes

`<docset>` Content model changes

`<categories>` and `<category>` Content model changes

`<deliverable>` Content model changes

`<internal>` and `<external>` Content model changes