\
**Category:** vNext\
**Created:** [August 18, 2026, 9:02am UTC](https://discourse.aurelia.io/t/aurelia-html-based-router/6748 "2026-08-18T09:02:24Z")\
**Posts on this page:** 3\
**Page:** 1
**Author:**  [@bigopon](https://discourse.aurelia.io/u/bigopon)\
**Post date:** [August 18, 2026, 9:02am UTC](https://discourse.aurelia.io/t/aurelia-html-based-router/6748/1 "2026-08-18T09:02:24Z")
I’ve published an experimental implementation of this RFC [[RFC] template based routing · Issue #2038 · aurelia/aurelia · GitHub](https://github.com/aurelia/aurelia/issues/2038)
at [aurelia-router-html on npm](https://www.npmjs.com/package/aurelia-router-html).
The docs, examples, and an in-browser playground are available at [aurelia-router-html.netlify.app](https://aurelia-router-html.netlify.app/). I’d love people to try it in real applications and share feedback, edge cases, and issues.
---
**Author:**  [@bigopon](https://discourse.aurelia.io/u/bigopon)\
**Post date:** [August 20, 2026, 12:42pm UTC](https://discourse.aurelia.io/t/aurelia-html-based-router/6748/2 "2026-08-20T12:42:58Z")
I’ve added & tighten various features, the router is quite feature complete, ish. It probably won’t be lacking for any “normal” applications 🤞 😃
---
**Author:**  [@maggardduntz8118](https://discourse.aurelia.io/u/maggardduntz8118)\
**Post date:** [November 7, 2026, 8:07pm UTC](https://discourse.aurelia.io/t/aurelia-html-based-router/6748/3 "2026-11-07T20:07:44Z")
“Feature complete, ish” is a fair caveat for an experimental router. The interesting part is the template-based routing itself, since that changes how routes are declared compared to the usual config objects. When you say normal applications probably won’t find gaps, I’d be curious which edge cases you already know are thin — nested routes, guards, or redirects are usually where experimental routers show their seams first. Feedback from real apps will surface the rest, but naming the known weak spots upfront tends to get more useful reports.