+1

site/content/_index.md

@@ -1,6 +1,6 @@
 ---
-title: "XSLT Lab"
+title: "XSLT Playground"
-description: "A Hugo-powered landing page that sits alongside the Helm chart repo."
+description: "Run and debug XSLT online with multi-parameter inputs, timing, and a lightweight UX."
 ---
 
-Welcome! This site is generated with Hugo and lives in the `site/` directory so the existing Helm chart artifacts stay untouched. Build it locally or publish the generated `docs/` folder to GitHub Pages for a simple web presence.
+Welcome to the home of [XSLT Playground](https://xsltplayground.com): a browser-based XSLT editor built for real-world transforms. Find release notes, how-tos, and deployment tips (including Helm) that help you get the most out of the playground without a heavyweight IDE.

site/content/about.md

@@ -1,8 +1,14 @@
 ---
 title: "About"
-description: "Why this repo exists and what you can do with it."
+description: "What XSLT Playground is and how this site supports it."
 ---
 
-The XSLT Lab repo hosts the Helm chart index and packaged chart so you can install the playground quickly. A minimal Hugo site now lives alongside the chart to collect documentation, changelogs, and useful links without interfering with the chart repository structure.
+[XSLT Playground](https://xsltplayground.com) is a browser-based XSLT editor built for realistic workloads: multiple inputs and parameters, live execution, and timing hints so you can tune your transforms without heavy desktop tooling.
 
-Use it to share how-tos, release notes, or background on how the playground is deployed. All content is Markdown, so you can edit it directly and rebuild the `docs/` output when you are ready to publish.
+This site exists to give you:
+
+- Release notes and product updates.
+- Short guides that mirror common integration tasks.
+- Deployment options, including a Helm chart you can point at your own cluster.
+
+Everything is Markdown in `site/content/`, and the generated output lives in `docs/` so you can publish easily via GitHub Pages alongside the chart index.

site/content/draft/¿Porque XSLT Playground?¿Necesita el mundo un editor de XSLT online?.md

@@ -0,0 +1,17 @@
+Desde el principio de mi experiencia profesional he estado muy ligado al mundo XPath y XSLT, principalmente por ser el estándar de transformación esencial del formato estándar durante gran parte de mi vida profesional, como es XML, pero siempre he sentido la necesidad de un editor xslt online potente que permita agilizar las tareas de depuración y optimización de las hojas XSLT.
+
+Durante mi carrera he utilizado o intentado diferentes editores para esta tarea. En mi carrera siempre tendrá un lugar especial XML Spy que a principios de los 2000 era como el editor de XML de referencia y permitía hacer una gran cantidad de tareas con los XML, pero la edición de los XSLT no era su fuerte.
+
+En momento opciones como JDeveloper, ese extinto IDE que tenia Oracle ofrecía algo bastante interesante desde el punto de vista de visualización de las hojas XSLT y poder ejecutarlas en aislamiento, cosas que luego cubriría la suite de Altova con productos como MapForce tambien, pero aun así, eran productos muy pesados que requerían de licencias y bastantes recursos para moverlas.
+
+Con la llegada del mundo web, los editores web simples para diferentes cuestiones cubrieron esa necesidad de un editor ligero que me permita hacer una tarea especifica de manera eficiente. No se si es algo generalizado, pero para mi sigo acudiendo a base64encoder para tratamiento de base64, o a epoch converter para la gestión de tiempos, o regex101 para la depuración de expresiones regulares.
+
+Luego ya con lenguajes mas complejos llegarons los diferentes playgrounds como JQ Playground para expresiones JQ y similares, y ahí es donde note que debería haber algo para XSLT. Y es que editores XSLT online existen, pero realmente no dan lo que creo que la gente que trabaja de manera continuo con XSLT necesita. Basicamente los editores se centran en una hoja XSLT que tiene un unico input relativamente sencillo y genera un output, ya esta.
+
+Pero normalmente cuando estas trabajando con XSLT la integración de diferentes fuentes de datos, es decir de diferentes parámetros, es fundamental, porque mas de una vez o especialmente si te dedicas a cuestiones de integración empresarial necesitas tener mas de una fuente, y eso simplemente no existe en el "mercado de editores xslt online".
+
+SI luego le sumamos la capacidad de que se vaya generando la respuesta segun haces modificaciones para mejorar la eficiencia, o tener un valor numerico del tiempo que tarda en ejecutarse para poder acomodarse a cuestiones de optimización mas carencias que están ahí.
+
+Y posiblemente esto viene porque el mercado es pequeño, porque la gente de trabaja con XSLT y que además recurre a recursos online, no esta buscando grandes cosas, pero yo realmente cree xsltplayground.com para mi, y si luego esto puede servir a mas gente pues bienvenido sea, pero realmente cree la aplicación que me hubiera gustado que existiese hace 5-10-15 años cuando creo que podría haberme hecho ahorrar una gran cantidad de horas, y espero que hoy se las ahorren a muchos desarrolladores o personas simplemente que trabajan con XSLT y que buscan un editor online ligero para hacer cierta depuración y optimización de sus hojas y que lo puedan hacer mientras disfrutan de una experiencia agradable. 
+
+Si consigo eso, habrá merecido la pena! 

site/content/posts/welcome-to-xslt-lab.md

@@ -1,15 +1,14 @@
 ---
-title: "Welcome to the XSLT Lab site"
+title: "Welcome to the XSLT Playground blog"
-description: "A short walkthrough of what this Hugo site gives you."
+description: "What you will find here and how it helps you get more from the online XSLT editor."
 date: 2025-02-28T00:00:00Z
----
 
-This repo now contains a Hugo site so you can publish notes, guides, and announcements next to the Helm chart.
+[XSLT Playground](https://xsltplayground.com) is a browser-first XSLT editor that lets you run transforms with multiple inputs and parameters, see results instantly, and spot performance hotspots without installing anything. This blog gathers the practical pieces you need around it.
 
-What you get:
+What you will find here:
 
-- A landing page that links to the chart index.
+- Product updates and release notes for the playground.
-- A posts section for updates and long-form guides.
+- XSLT debugging recipes tailored to multi-parameter, real-world scenarios.
-- A configurable menu and simple styling that lives entirely in this repo.
+- Deployment notes, including the Helm chart and self-hosting guidance.
 
-Run `hugo --source site --minify` to generate the static site into `docs/`, commit the output, and point GitHub Pages at the `docs` folder to go live.
+If you want to try it now, head straight to [xsltplayground.com](https://xsltplayground.com). If you want to contribute content, edit the Markdown in `site/content/` and rebuild the site with `hugo --source site --minify` to publish to `docs/`.

site/content/posts/why-xslt-playground-online-editor.md

@@ -0,0 +1,47 @@
+---
+title: "Why I built an XSLT online editor for real-world work"
+description: "The story behind XSLT Playground—an XSLT online editor tuned for multi-parameter transforms, fast feedback, and practical debugging."
+date: 2025-11-22T15:34:45Z
+---
+
+If you have spent years inside XPath and XSLT, you know the pain of juggling heavy desktop tools just to ship one transform. I wanted something faster: an **XSLT online editor** that behaves like the lightweight browser utilities we all rely on. That is why I created [XSLT Playground](https://xsltplayground.com), a web-based editor built for realistic, multi-input scenarios instead of the single-input demos most tools target.
+
+## The gap traditional editors left open
+
+- In the 2000s, XML Spy was the default XML IDE, but XSLT editing and debugging always felt bolted on.  
+- Oracle JDeveloper and later Altova tools like MapForce improved visualization and isolated execution, yet they remained heavy, licensed, and resource-hungry.  
+- Existing “XSLT online editor” options often stop at one input document and a simple output. Real integrations rarely look that tidy.
+
+## Inspired by the best small web utilities
+
+For quick daily tasks, I still open [regex101](https://regex101.com) to debug patterns, [base64decode.org](https://www.base64decode.org/) to inspect payloads, and [epochconverter.com](https://www.epochconverter.com/) for timestamps. They are fast, focused, and always there. XSLT deserved the same “open browser, get answers” experience.
+
+## What I actually needed in an online XSLT editor
+
+- **Multiple parameters and sources**: real transformations combine several XML fragments, parameters, and metadata—not just one tidy input.  
+- **Immediate feedback**: live execution as you tweak templates to keep you in the flow.  
+- **Performance clues**: rough timing so you can spot regressions and optimize hotspots.  
+- **Zero install**: works in the browser without heavyweight downloads.
+
+## What XSLT Playground delivers
+
+- Multi-input, parameter-rich execution that mirrors enterprise and integration workloads.  
+- Live runs and inline results so you can iterate without context switching.  
+- Lightweight UX that feels like other playgrounds (think [jqplay.org](https://jqplay.org)) but purpose-built for XSLT.  
+- Direct access at [xsltplayground.com](https://xsltplayground.com) whenever you need an **online XSLT editor**.
+
+## Who should try it
+
+- Engineers integrating XML across systems who need a reliable **XSLT online editor** for quick debugging.  
+- Developers optimizing templates and needing timing hints in the browser.  
+- Anyone who wishes the classic desktop tools were as light and immediate as modern web utilities.
+
+## Executive Summary
+
+- Tool: [XSLT Playground](https://xsltplayground.com) — browser-based **XSLT online editor** with multi-parameter inputs, live output, and timing.  
+- Problem: legacy editors are heavy, single-input, and slow to iterate.  
+- Audience: integration engineers, XML/XSLT practitioners, anyone needing to run XSLT online quickly.  
+- Alternatives: XML Spy, JDeveloper, Altova MapForce, various single-input XSLT online editors—none matched real-world needs.  
+- Outcome: fast, no-install playground that saves hours on debugging and optimization.
+
+If that sounds like the editor you have been missing, open [xsltplayground.com](https://xsltplayground.com) and run your next transform right now.

site/hugo.toml

@@ -1,13 +1,13 @@
 baseURL = "https://blog.xsltplayground.com/"
 languageCode = "en-us"
-title = "XSLT Lab"
+title = "XSLT Playground"
 paginate = 10
 publishDir = "../docs"
 enableRobotsTXT = true
 
 [params]
-subtitle = "Helm and XSLT playground with a lightweight docs site."
+subtitle = "Online XSLT editor built for real-world transformations."
-lead = "Articles, release notes, and pointers to the Helm repo all live here. Build locally or publish from the docs folder without disturbing existing chart artifacts."
+lead = "Run and debug XSLT online with multi-parameter inputs, timing hints, and fast feedback. This site hosts release notes, guides, and deployment options for XSLT Playground."
 
 [params.adsense]
 # Prefer setting ADSENSE_CLIENT and ADSENSE_INARTICLE_SLOT env vars when building if you don't want the values committed.

site/layouts/index.html

@@ -1,23 +1,24 @@
 {{ define "main" }}
 <section class="hero">
-  <p class="eyebrow">Static Site + Helm Repo</p>
+  <p class="eyebrow">Online XSLT Editor</p>
   <h1>{{ .Title }}</h1>
   <p class="lead">{{ .Params.description | default .Site.Params.lead }}</p>
   <div class="cta-row">
-    <a class="button" href="{{ "/posts/" | relURL }}">Read updates</a>
+    <a class="button" href="https://xsltplayground.com">Open the playground</a>
-    <a class="button ghost" href="{{ "/charts/index.yaml" | relURL }}">Helm repo index</a>
+    <a class="button ghost" href="{{ "/posts/" | relURL }}">Read updates</a>
+    <a class="button ghost" href="https://alexandrev.github.io/xslt-lab/index.yaml">Helm chart index</a>
   </div>
 </section>
 
 <section class="grid">
   <article class="card">
-    <p class="eyebrow">How this fits</p>
+    <p class="eyebrow">How the playground helps</p>
-    <h2>Side-by-side with your chart</h2>
+    <h2>Built for real XSLT work</h2>
-    <p>The Hugo source lives in <code>site/</code> and publishes to <code>docs/</code>, keeping the existing chart index and packages intact.</p>
+    <p>Run XSLT online with multiple inputs and parameters, see results as you type, and get timing hints to spot regressions before they hit production.</p>
     <ul class="checks">
-      <li>Markdown content</li>
+      <li>Multi-parameter transforms</li>
-      <li>No external theme dependency</li>
+      <li>Live execution and inline output</li>
-      <li>Ready for GitHub Pages</li>
+      <li>Timing to guide optimization</li>
     </ul>
   </article>
   <article class="card">