axadrn

4 ms·

1. 1.▲
   Show HN: TemplUI v1.7.0 – UI components for Go and templ, now with import mode(github.com)

   1 points by axadrn 7mo ago|0 comments
2. 2.▲
   Show HN: goilerplate and templUI Pro, two products for Go and templ developers(goilerplate.com)

   2 points by axadrn 7mo ago|0 comments
3. 3.▲
   Show HN: Deeploy v0.3.0 – terminal-first VPS app deployment tool(deeploy.sh)

   1 points by axadrn 8mo ago|0 comments
4. 4.▲
   Show HN: Deeploy v0.2.0 – Self-hosted PaaS with terminal UI(deeploy.sh)

   1 points by axadrn 8mo ago|0 comments
5. 5.▲
   Show HN: deeploy 0.1 – Terminal-first deployment platform (self-hosted)(github.com)

   1 points by axadrn 9mo ago|0 comments
6. 6.▲
   Show HN: goilerplate – A SaaS boilerplate for Go and templ and Htmx(goilerplate.com)

   6 points by axadrn 11mo ago|2 comments
7. 7.▲
   by axadrn 1y ago

   Thanks for your feedback. I cannot reproduce it. If the problem persists, I would be happy if you create a detailed issue on GH, thanks!
8. 8.▲
   by axadrn 1y ago

   Nice to hear, happy coding! =)
9. 9.▲
   by axadrn 1y ago

   Yeah, totally fair question. Originally, I had templUI components available via Go module imports, but there were a few real issues: - Tailwind v4+ with CSS-only config needs hardcoded paths to `.templ` files. That clashed in teams where Go
10. 10.▲
    by axadrn 1y ago

    Thanks for the kind feedback! I totally get the appeal of daisyUI – super quick to drop in and great for prototyping. With TemplUI, I’m aiming for a more minimal, dependency-free setup – no extra Tailwind plugins or runtime JS unless absolu
11. 11.▲
    by axadrn 1y ago

    I took another look and we do explain what templ is on our introduction page: https://templui.io/docs/introduction#built-on-strong-foundat... "Templ - Type-safe templating for Go" with a link to templ.guide.
12. 12.▲
    by axadrn 1y ago

    Fair point – I’ll make sure to link to https://templ.guide more prominently. Thanks for the heads-up!
13. 13.▲
    by axadrn 1y ago

    You're right – HTMX works everywhere by default. By “HTMX support” I just mean: the JS logic in components (e.g. tooltips, modals) auto-reinitializes after HTMX swaps. So you can use components inside HTMX-driven UIs without worrying a
14. 14.▲
    by axadrn 1y ago

    Is TS actually a thing? ^^
15. 15.▲
    by axadrn 1y ago

    Appreciate that! Always happy to find common ground.
16. 16.▲
    by axadrn 1y ago

    The CLI is just a small Go binary – you can install it once via `go install` and then run `templui add icon`. It helps keep things consistent as the library evolves. But yeah, I get that some folks prefer manual imports – all good!
17. 17.▲
    by axadrn 1y ago

    THIS actually!
18. 18.▲
    by axadrn 1y ago

    Totally fair – stable, fast, boring tech is often the best kind of tech. templ’s more for folks who want to stay in Go but need a smoother frontend experience for modern UI needs.
19. 19.▲
    by axadrn 1y ago

    Mostly for building typed web UIs in Go – instead of using html/template, which isn’t typed and feels oldschool. templ makes Go feel way more modern for frontend work.
20. 20.▲
    by axadrn 1y ago

    You are welcome! Happy coding! =)
21. 21.▲
    Show HN: templUI – The UI Kit for templ (CLI-based, like shadcn/UI)(templui.io)

    62 points by axadrn 1y ago|34 comments