Fix/re-introduce custom Jekyll tags for better glossary integration (#6163)

docs/concepts/services-networking/ingress.md

@@ -5,7 +5,7 @@ title: Ingress
 ---
 
 {% capture overview %}
-{% include templates/glossary/snippet.md term="ingress" length="all" %}
+{% glossary_definition term_id="ingress" length="all" %}
 {% endcapture %}
 
 {% capture body %}

docs/concepts/workloads/controllers/statefulset.md

@@ -10,10 +10,10 @@ title: StatefulSets
 ---
 
 {% capture overview %}
-**StatefulSet is the workload API object used to manage stateful applications. 
+**StatefulSet is the workload API object used to manage stateful applications.
 StatefulSets are beta in 1.8.**
 
-{% include templates/glossary/snippet.md term="statefulset" length="all" %}
+{% glossary_definition term_id="statefulset" length="all" %}
 {% endcapture %}
 
 {% capture body %}

docs/reference/glossary.md

@@ -56,9 +56,10 @@ default_active_tag: fundamental
 Also known as: <i>{{ term.aka | join: ", " }}</i>
 <br>
 {% endif %}
-<span class="preview-text">{{ term.short-description | markdownify }} <a href="javascript:void(0)" class="click-controller no-underline" data-target="{{ term.id }}">[+]</a></span>
+
+<span class="preview-text">{{ term.short-description | liquify | markdownify }} <a href="javascript:void(0)" class="click-controller no-underline" data-target="{{ term.id }}">[+]</a></span>
 <div id="{{ term.id }}" class="hide">
-{{ term.long-description | markdownify }}
+{{ term.long-description | liquify | markdownify }}
 </div>
 </div>
 </li>

docs/search.md

@@ -2,8 +2,11 @@
 layout: docwithnav
 title: Search Results
 ---
-<script>
+<script type="text/javascript">
+  document.write('<gcse:searchresults-only linktarget="_parent"></gcse:searchresults-only>');
+</script>
 
+<script>
   (function() {
     var cx = '013288817511911618469:elfqqbqldzg';
     var gcse = document.createElement('script');
@@ -17,4 +20,3 @@ title: Search Results
     document.querySelector('html').classList.add('search');
   })();
 </script>
-<gcse:searchresults-only linktarget="_parent"></gcse:searchresults-only>

docs/tasks/configure-pod-container/assign-memory-resource.md

@@ -124,12 +124,14 @@ Pod's 200 MiB limit.
 }
 ```
 
+
 Delete your Pod:
 
 ```shell
 kubectl delete pod memory-demo --namespace=mem-example
 ```
 
+
 ## Exceed a Container's memory limit
 
 A Container can exceed its memory request if the Node has memory available. But a Container
@@ -370,4 +372,3 @@ kubectl delete namespace mem-example
 
 
 {% include templates/task.md %}
-

docs/tasks/inject-data-application/define-command-argument-container.md

@@ -5,7 +5,7 @@ title: Define a Command and Arguments for a Container
 {% capture overview %}
 
 This page shows how to define commands and arguments when you run a container
-in a Kubernetes Pod.
+in a {% glossary_tooltip term_id="pod" %}.
 
 {% endcapture %}