A full-stack Go starter kit with server-side rendering, HTMX, and an admin panel for rapid web development.
Pagoda is a starter kit for rapid full-stack web development in Go, providing a pre-configured foundation with an admin panel, authentication, and modern UI components. It solves the problem of bootstrapping production-ready web applications by integrating best practices and essential features out of the box.
Go developers building full-stack web applications who want a structured starting point with server-side rendering, an admin interface, and minimal JavaScript dependencies.
Developers choose Pagoda for its all-in-one approach, combining a robust backend with a dynamic admin panel and modern frontend interactions using HTMX, all while maintaining full control over the codebase without framework lock-in.
Rapid, easy full-stack web development starter kit and admin panel in Go
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides a dynamic UI to manage all database entities with automatic code generation, saving significant development time for CRUD operations and background task monitoring.
Combines HTMX for AJAX, Alpine.js for interactions, and DaisyUI for styling, enabling interactive UIs without writing JavaScript or CSS, as highlighted in the README examples.
Uses Gomponents for server-side HTML generation, offering compile-time checks and reusable components in pure Go, which enhances code reliability and developer experience.
Includes authentication, sessions, background tasks, caching, and form handling out of the box, reducing boilerplate code and accelerating project startup.
The admin interface is still in development, lacking features like inline validation, support for all field types (e.g., JSON), and exposed sorting or filters, as noted in the roadmap.
Requires installing additional tools like Ent code-generator, Air for live reloading, and Tailwind CLI, which adds complexity to the setup process and dev environment configuration.
Cache tagging implementation requires locking and has no size limit for tag indexes, which could lead to memory issues in high-load scenarios, as admitted in the caching section.
Being a starter kit rather than a framework, it has a smaller community and fewer third-party extensions compared to established frameworks, which might slow down problem-solving.