

-
Isn't that basically Templ [0] then? But Templ has that extra build step for preprocessing and converting back to plain Go files.
For me, gomponents is the middle ground. You don't get everything, but quite a lot of JSX-like feel. I was inspired by JSX after all. :) [1] Although I called it GOX back then… :D
[0]: https://templ.guide
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
That’s awesome! I have a very similar project Dovetail, that tries to nudge you into making things accessible.
https://github.com/RoyalIcing/Dovetail
-
If you mean “action=/foo” for a “form” tag, there is an “Action” attribute: https://github.com/maragudk/gomponents/blob/main/html/attrib...
-
gomponents is just a glorified string builder, so it's more or less like writing HTML in Go that gets output from the server. So you put event handlers on your elements like you normally would, write scripts and include JS like you normally would, etc.
That said, there's gomponents-htmx [0] for easy integration with HTMX.
[0]: https://github.com/maragudk/gomponents-htmx
-
gomponents-starter-kit
A starter kit for building a web app with gomponents, HTMX, and TailwindCSS in Go.
Yep, this exactly. And the starter kit mentioned is here, for anyone curious: https://github.com/maragudk/gomponents-starter-kit
-
storybook
Storybook is the industry standard workshop for building, documenting, and testing UI components in isolation
Not the OP but I think he meant the one at https://storybook.js.org
-
It's the same with the Ginkgo testing library: "After the package books_test declaration we import the ginkgo and gomega packages into the test's top-level namespace by performing a . dot-import. Since Ginkgo and Gomega are DSLs this makes the tests more natural to read."
https://onsi.github.io/ginkgo/
-
Nutrient
Nutrient – The #1 PDF SDK Library, trusted by 10K+ developers. Other PDF SDKs promise a lot - then break. Laggy scrolling, poor mobile UX, tons of bugs, and lack of support cost you endless frustrations. Nutrient’s SDK handles billion-page workloads - so you don’t have to debug PDFs. Used by ~1 billion end users in more than 150 different countries.