A CLI tool to scaffold modern web apps with Go backends and htmx/Alpine.js frontends using popular CSS frameworks.
Gowebly is a CLI tool that automates the creation of modern web applications. It sets up a project with a Go backend and a frontend using htmx, hyperscript, or Alpine.js paired with popular CSS frameworks. It solves the problem of tedious, manual project configuration, enabling developers to start building features immediately.
Developers and teams building full-stack web applications who want a production-ready setup without spending time on initial configuration. It's particularly useful for those adopting Go with modern, lightweight frontend technologies.
Developers choose Gowebly because it provides a comprehensive, opinionated stack out of the box, supports multiple Go frameworks and CSS tools, and includes DevOps-ready Docker configurations. It dramatically reduces project setup time from hours to minutes.
🔥 A next-generation CLI tool that makes it easy to create amazing web applications with Go on the backend, using htmx, hyperscript or Alpine.js, and the most popular CSS frameworks on the frontend.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Generates a complete, production-ready project with Go backend, htmx frontend, and CSS framework in one command, as shown in the quick start GIF and documentation.
Supports multiple Go web frameworks (Fiber, Gin, Echo, etc.) and CSS frameworks (Tailwind CSS, Bootstrap, etc.), allowing customization within an opinionated stack.
Includes built-in live-reload via Air, golangci-lint config, and Docker/Compose files, streamlining development and deployment from the start.
Runs on Linux, Windows, and macOS with extensive multi-language documentation, making it accessible to a wide range of developers.
Forces the use of Go with htmx/Alpine.js frontends; deviating to other stacks like React requires significant manual configuration, undermining the tool's automation benefits.
Maintains separate branches for v1, v2, and v3, indicating potential breaking changes and complexity in managing updates, as noted in the README's versioning note.
Focuses on web applications only, lacking built-in support for common needs like database setup or API-only projects, requiring additional manual work.