[!NOTE]
Beta: Datapages is ready for production use.
APIs are close to stable but can still change.
A Templ + Go + Datastar web framework and toolset for building GUI apps and web application in pure Go - no matter whether it's a real-time collaborative dynamic web app, a simple HTMX-style website, or an installable local-first GUI app.
Datapages will provide your coding agents with the skills and CLI tools they need to generate well performing, resource-efficient apps and keep the code base coherent and maintainable, lowering token-usage, reducing potential for bugs and vulnerabilities as well as slowing the accumulation of technical debt.
Focus on your business logic
Datapages parses your app source packages, lints them, reports errors, and generates all the wiring and boilerplate. Routing, sessions and authentication, SSE streams, per-tab server-side state, CSRF protection, type-safe URL and action helpers, Prometheus metrics, JavaScript service workers etc. - so your application code stays clean and takes full advantage of Go's strong static typing and high performance.
Examples
counter: Real-time counter built twice in one module, bare bones as app/simple and polished as app/fancy. Bare bones starting point, and the example of a module that builds more than one application.
todolist: Real-time collaborative todo list with per-tab server-side state (Most Tao conform example).
calculator: Hybrid calculator app that runs both as a multi-client server and single-client Desktop app.
classifieds: Full-featured classifieds marketplace with sessions, auth, Prometheus metrics, Grafana dashboards and load testing.
webcomponents: Landing page with vanilla and Lit-based Web Components bundled via esbuild through a custom watcher.
sqlitesessions: Custom sessions.Manager implementation backed by SQLite via sqinn-go (no cgo).
fast-shim: A cached placeholder shown immediately and replaced with the live response.
offline-cache: Service worker support with handler-cached pages, a PageOffline fallback, and tickets available without a connection.
file-upload: Chunked file uploads to disk that can be paused, resumed and continued after a reload or a server restart, with server-enforced transfer limits.
See SPECIFICATION.md for the full source package specification, including handler signatures, parameters, return values, events, sessions, and modules.
Modules
Datapages ships pluggable modules with swappable implementations:
The reason I built Datapages is that the combination of Datastar + Go + Templ is my preferred way of writing server-centric web applications. But in every project I used this tech stack for I kept repeating the same code patterns and solving the same problems over and over again. I realized many developers are repeating the same patterns too and struggle with the common pitfalls:
How to handle SSE streams correctly?
How to use NATS effectively?
How to approach security and authentication?
How to configure a convenient hot-reload for development?
How to keep the code maintainable over time, especially when you add more developers and/or AI assistants?
How to keep AI coding assistants from drifting too much?
How to achieve optimal performance and a good UX for endusers?
Your Datastar frontends are your rocket to extraterrestrial worlds of the internet.
The further you want to go, the heavier a rocket you'll require. Hence, you need powerful boosters to get it off the ground and overcome Earth's gravity. Such boosters exist in the form of awesome templates like zangster300/northstar, which will quickly get your rocket to the stratosphere and beyond. But power alone is not enough — you also need good stabilizing fins and thrust vectoring to keep your rocket steady as it flies. I felt like this part was lacking in the Go ecosystem of Datastar. By enforcing a common structure of types, methods and other conventions with tooling, Datapages provides not only the power but also the stability your rocket needs to stay in flight for long and consume as little brain fuel as possible.
Not only does Datapages allow you to start quickly with datapages init and jump straight into building your application, but it also continuously supports you keeping accidental complexity low by:
Providing a Datastar Tao oriented architecture as a good default while preserving enough flexibility to go beyond if you need to.
Providing datapages gen to generate all boilerplate code consistently and guide you and your AI coding agents.
Providing datapages lint that can be used in CI/CD workflows for extensive static code analysis.
Providing datapages watch to give you an interactive hot-reload environment for a fast feedback loop with error reporting directly in the browser preview.
Agentic coding is a big topic right now and likely here to stay. But LLMs tend to drift over time and introduce accidental complexity.
So for AI to be used more effectively I wanted to provide the skills and instructions necessary for agents to know how to deal with this tech stack and call into Datapages CLI help them when they drift by providing them with useful feedback.
Who This Is For
Datapages is a good fit if you:
Already write your backend in Go and want to build your web frontend in the same language and toolchain.
Are building a server-rendered application, where the server owns the data; not a local-first offline-capable SPA.
Already use Datastar and want a Go framework to help you ship faster with less code while preserving maintainability.
Already use Templ and want a full framework built around it.
Use HTMX, idiomorph and Alpine.js, and instead want a single cohesive stack with a smaller bundle size and less spaghetti-code.
Don't want to maintain a separate REST/GraphQL API just to feed your frontend.
Want to deploy as a single, statically compiled binary that makes the most of your hardware.
Want to develop hybrid desktop apps in Go and HTML5 (see Calculator example)
Contributing
See CONTRIBUTING.md for development setup and commands, and AGENTS.md for code style, testing conventions, commit message format and project structure.
datapages (romshark/datapages)
Choose a tag and it will appear here. With no tags selected, all catalog projects are shown.
Searching Database…
Choose a tag and it will appear here. With no tags selected, all catalog projects are shown.
这是什么？Datapages 是一个 Web 框架和工具集，让你用纯 Go 在 Templ + Go + Datastar 技术栈上构建 GUI 和 Web 应用——可以是实时协作的 Web 应用、简单的服务端渲染网站，也可以是可安装的本地优先 GUI 应用。
它和我自己动手把 Datastar 和 Go 接起来有什么不同？它会解析你的源代码包，自动生成那些你本来要在每个项目里手动写的接缝代码：路由、SSE 流、每个标签页的服务端状态、CSRF 防护、Prometheus 指标和 service worker——这样你的代码保持干净，还能充分利用 Go 的静态类型。
我想试试，第一条命令是什么？用 datapages init 生成一个应用骨架；开发时 datapages gen 负责生成样板代码，datapages watch 提供热重载，出错信息会直接显示在浏览器预览里。
Datapages 是一个 Web 框架和工具集，让你用纯 Go 在 Templ + Go + Datastar 技术栈上构建 GUI 和 Web 应用——可以是实时协作的 Web 应用、简单的服务端渲染网站，也可以是可安装的本地优先 GUI 应用。