A lightweight, minimalist Go template library based on html/template for building web applications.
Goview is a template library for Go web applications that extends the standard html/template package with additional structure and features. It solves the problem of organizing templates in larger applications by providing layout support, partial includes, and framework integrations while keeping the familiar Go templating syntax.
Go developers building server-rendered web applications who need more organization than basic html/template files but want to avoid heavy, opinionated template engines.
Developers choose Goview because it adds just enough structure to the standard library's templating system—like layouts and partials—without introducing new syntax or breaking compatibility with existing html/template knowledge.
Goview is a lightweight, minimalist and idiomatic template library based on golang html/template for building Go web application.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Built directly on Go's html/template with no external dependencies, ensuring compatibility and minimal overhead for Go web applications.
Offers dedicated support packages for Gin, Iris, Echo, and Chi, simplifying setup and reducing boilerplate code as shown in the examples.
Provides master layouts and include syntax for partials, enabling consistent page structures and reusable components without breaking from Go idioms.
Configurable caching for production with optional auto-reload in development, balancing speed and flexibility during the development cycle.
Allows running separate template engines for different application sections like frontend and backend, useful for multi-tenant or modular apps.
Partials must be explicitly listed in the config array, lacking glob pattern support or automatic discovery, as admitted in the TODO section.
While custom functions can be added, there are no pre-built helpers for common tasks like formatting or pagination, requiring extra development effort.
Separate supports for different framework versions (e.g., Echo v3 vs v4) can lead to compatibility issues and maintenance overhead.
Lacks features like nested layouts, internationalization, or asset pipeline integration, making it less suitable for complex front-end needs.