chore: add script for fixing documentation issues and enhance workflow

- Introduced fix-docs.sh script to create lowercase copies of documentation files and fix Liquid template syntax.
- Updated test-docs-generation.yml to execute the new script during the documentation generation process.
- Added new index and feature markdown files to improve documentation structure and navigation for code-based and configuration-based features.

Author: mokhld

.github/scripts/docs/fix-docs.sh

@@ -0,0 +1,38 @@
+#!/bin/bash
+# fix-docs.sh - Quick script to fix documentation issues
+
+echo "🔄 Fixing documentation files..."
+
+# Create lowercase copies and fix links
+for dir in code-based configuration-based; do
+  echo "Processing $dir directory..."
+  cd "features/$dir" || exit 1
+  
+  # Create lowercase versions of all uppercase files
+  for file in *.md; do
+    if [[ "$file" == *[A-Z]* ]]; then
+      lowercase=$(echo "$file" | tr '[:upper:]' '[:lower:]')
+      echo "  Creating lowercase copy: $lowercase"
+      cp "$file" "$lowercase"
+      
+      # Fix the Liquid templates in both files
+      for target in "$file" "$lowercase"; do
+        # Replace {{ with {% raw %}{{ and }} with }}{% endraw %}
+        sed -i.bak -E 's/\{\{([^}]*)\}\}/\{% raw %\}\{\{\1\}\}\{% endraw %\}/g' "$target"
+        rm -f "$target.bak"
+      done
+    fi
+  done
+  
+  # Fix links to uppercase files
+  for file in *.md; do
+    # Update links to other docs to use lowercase
+    sed -i.bak -E 's/\(([^)]*)(PAGE_[A-Z_]+)(\.md)?\)/(\1\L\2\E\3)/g' "$file"
+    sed -i.bak -E 's/\(\.\.\/([^)]*)(PAGE_[A-Z_]+)(\.md)?\)/(\.\.\1\L\2\E\3)/g' "$file"
+    rm -f "$file.bak"
+  done
+  
+  cd ../.. || exit 1
+done
+
+echo "✅ Documentation files fixed!"

.github/workflows/test-docs-generation.yml

@@ -90,6 +90,14 @@ jobs:
           ../.github/scripts/docs/fix-schema-links.sh
           cd ..
 
+      - name: Fix Liquid templates and create lowercase files
+        run: |
+          echo "🔄 Fixing Liquid templates and creating lowercase files..."
+          cd site-src
+          chmod +x ../.github/scripts/docs/fix-docs.sh
+          ../.github/scripts/docs/fix-docs.sh
+          cd ..
+
       - name: Create Jekyll configuration
         run: |
           echo "🔄 Creating Jekyll configuration files..."

docs/features/code-based/CUSTOM_SERVICES.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: Custom Services
+parent: Code-based Features
+grand_parent: Features
+---
+
 # Overriding DXT logic with custom services
 
 ## Customising where forms are loaded from

docs/features/code-based/index.md

@@ -0,0 +1,11 @@
+---
+layout: default
+title: Code-based Features
+parent: Features
+has_children: true
+---
+
+# Code-based Features
+
+- [Custom Services](custom_services)
+- [Page Views](page_views)

docs/features/configuration-based/PAGE_EVENTS.md

@@ -1,10 +1,17 @@
+---
+layout: default
+title: Page Events
+parent: Configuration-based Features
+grand_parent: Features
+---
+
 # Page events
 
 Page events are a configuration-based way of triggering an action on an event trigger. For example, when a page loads, call an API and retrieve the data from it.
 
 DXT's forms engine is a frontend service, which should remain as lightweight as possible with business logic being implemented in a backend/BFF API. Using page events, DXT can call your API and use the tailored response downstream, such a page templates to display the response value.
 
-The downstream API response becomes available under the `{{ context.data }}` view model attribute for view templates, so it can be used when rendering a page. This attribute is directly accessible by our [page templates](./../configuration-based/PAGE_TEMPLATES.md) feature and our Nunjucks-based views.
+The downstream API response becomes available under the `{% raw %}{{ context.data }}{% endraw %}` view model attribute for view templates, so it can be used when rendering a page. This attribute is directly accessible by our [page templates](./../configuration-based/PAGE_TEMPLATES.md) feature and our Nunjucks-based views.
 
 ## Architecture
 

docs/features/configuration-based/PAGE_TEMPLATES.md

@@ -1,3 +1,10 @@
+---
+layout: default
+title: Page Templates
+parent: Configuration-based Features
+grand_parent: Features
+---
+
 # Page templates
 
 Page templates are a configuration-based way of adding dynamic content to the form UI, such as displaying the answer to a question, or some data from your API. This feature is only used for presentation purposes.

docs/features/configuration-based/index.md

@@ -0,0 +1,11 @@
+---
+layout: default
+title: Configuration-based Features
+parent: Features
+has_children: true
+---
+
+# Configuration-based Features
+
+- [Page Events](page_events)
+- [Page Templates](page_templates)

docs/features/index.md

@@ -0,0 +1,12 @@
+---
+layout: default
+title: Features
+nav_order: 4
+has_children: true
+permalink: /features/
+---
+
+# DXT Features
+
+- [Configuration-based Features](configuration-based/)
+- [Code-based Features](code-based/)