claude-code
b2737ec715
Phase 1 — internal linking: - Real [related] index (tags/keywords/category) in hugo.toml; rewrite related-posts.html to use .Related instead of "first 4 posts", which had left 12/20 posts with zero inbound links. - Add tags to 6 previously untagged posts. Phase 2 — de-cannibalization of the transactional cluster: - Soft-301 mechanism (redirectTo -> meta refresh + noindex,follow) in baseof. - xslt-online-editor-guide redirects to the app (pure duplicate of home). - xslt-validator-online retargeted informational; drop the "common errors" section that cannibalized the errors hub, link to it instead. - Migrate why-xslt-playground-online-editor into /about/ with an alias. - Remove the duplicate <h1> on the app landing page. Phase 3 — consolidate authority on the money domain: - baseURL -> https://xsltplayground.com/blog/ (served via NPM reverse proxy to GitHub Pages; subdomain will 301 to the subpath). - Rewrite internal blog links to /blog/... and cross-domain app links to xsltplayground.com/blog/... Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KZntQUfw463NW4ftgSjWw5
2.4 KiB
title, description, aliases
| title | description | aliases | |
|---|---|---|---|
| About XSLT Playground | The story behind XSLT Playground — a browser-based XSLT editor built for multi-parameter transforms, fast feedback, and practical debugging. |
|
XSLT Playground is a browser-based XSLT editor built for realistic workloads: multiple inputs and parameters, live execution, and timing hints so you can tune transforms without heavy desktop tooling.
Why I built it
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 — a tool that behaves like the lightweight browser utilities we all rely on. So I built XSLT Playground 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.
- Most online options 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 to debug patterns, base64decode.org to inspect payloads, and epochconverter.com for timestamps. They are fast, focused, and always there. XSLT deserved the same "open browser, get answers" experience — much like jqplay.org did for jq.
What it delivers
- Multi-input, parameter-rich execution that mirrors enterprise and integration workloads.
- Live runs and inline results so you can iterate without context switching.
- Rough timing so you can spot regressions and optimize hotspots.
- Zero install — it works in the browser, with Saxon HE on the backend for full XSLT 1.0 / 2.0 / 3.0 support.
What this site gives you
- Release notes and product updates.
- Short guides and a full XSLT & XPath function reference that mirror common integration tasks.
- Deployment options, including a Helm chart you can point at your own cluster.
Ready to try it? Open xsltplayground.com and run your next transform right now.