OPSEXP-2528: fix jekyll workflow (#311)

Co-authored-by: Giovanni Toraldo <[email protected]>

.github/workflows/docs.yml

@@ -15,13 +15,14 @@ on:
       - _config.yml
       - Gemfile*
       - charts/**/README.md
+      - charts/**/docs/**.md
   workflow_run:
     workflows: [Release Charts]
     types: [completed]
 
 jobs:
   publish:
-    uses: Alfresco/jekyll-build-tools/.github/workflows/jekyll-publish.yml@f6f1df9a2144fb76132602180732c456ddc13f3e
+    uses: Alfresco/jekyll-build-tools/.github/workflows/jekyll-publish.yml@5ee00079dbc774857cafa61054385d98a6f52374
     if: github.event_name == 'pull_request' || github.event.workflow_run.conclusion == 'success'
     with:
       working-directory: .

charts/alfresco-transform-service/docs/autoscaling.md

@@ -1,6 +1,6 @@
 ---
-title: ATS Autoscaling
-parent: alfresco-transform-service
+title: Autoscaling
+parent: Alfresco Transform Service
 grand_parent: Guides
 ---
 
@@ -34,7 +34,7 @@ with peak load or spare resources on low level of utilization while also
 minimizing the number of scaling events because changing the cluster topology
 means additional computation.
 
-### Default behaviour:
+### Default behaviour
 
 Without any further configuration scaling would happen as follow:
 
@@ -59,7 +59,7 @@ Alfresco on Kubernetes.
 
 Below are ways to tweak the auto scaling behaviour for your own setup.
 
-#### Settings the CPU resources correctly.
+#### Settings the CPU resources correctly
 
 CPU Resources request is the basis of calculation for the cluster to trigger
 scaling events. It is then very important to make sure it is set appropriately

docs/guides/alfresco-transform-service.md

@@ -0,0 +1,5 @@
+---
+title: Alfresco Transform Service
+parent: Guides
+has_children: true
+---