render custom tags in doc site

Author: anik120

docs/css/extra.css

@@ -7,4 +7,19 @@
 .md-nav__item--active > .md-nav__link, /* Active top-level items */
 .md-nav__item--nested > .md-nav__link { /* Nested top-level items */
     font-weight: bold;
-}
+}
+
+.tags-list {
+    list-style: none;
+    padding: 0;
+  }
+  
+  .tag {
+    display: inline-block;
+    background-color: red;
+    border-radius: 3px;
+    padding: 2px 8px;
+    margin: 2px;
+    font-size: 0.9em;
+    color: white;
+  }

docs/howto/configure-global-pull-secrets.md

@@ -5,6 +5,8 @@ tags:
 
 # Configure global pull secrets for allowing components to pull private images
 
+**Note: The UX for how auth info for using private images is provided is an active work in progress.**  
+
 To configure `catalogd` and `operator-controller` to use authentication information for pulling private images (catalog/bundle images etc), the components can be informed about a kubernetes `Secret` object that contains the relevant auth information. The `Secret` must be of type `kubernetes.io/dockerconfigjson`. 
 
 Once the `Secret` is created, `catalogd` and `operator-controller` needs to be redeployed with an additional field, `--global-pull-secret=<secret-namespace>/<secret-name>` passed to the respective binaries.

docs/overrides/main.html

@@ -0,0 +1,14 @@
+{% extends "base.html" %}
+
+{% block content %}
+<div class="tags">
+  {% if page.meta.tags %}
+    <ul class="tags-list">
+      {% for tag in page.meta.tags %}
+        <li class="tag">{{ tag }}</li>
+      {% endfor %}
+    </ul>
+  {% endif %}
+</div>
+{{ super() }}
+{% endblock %}

mkdocs.yml

@@ -4,6 +4,7 @@ site_name: Operator Lifecycle Manager
 theme:
   logo: assets/logo.svg
   name: "material"
+  custom_dir: docs/overrides
   palette:
     primary: black
   features:

requirements.txt

@@ -33,3 +33,4 @@ six==1.16.0
 soupsieve==2.6
 urllib3==2.2.3
 watchdog==4.0.2
+