I’ve been engaged on ZIN Engine — a light-weight server + templating engine that lets me write plain .html and nonetheless use issues like loops, API knowledge, varieties, and dynamic content material — with out touching a framework or construct step.
It began as a private resolution to construct quicker, cleaner web sites utilizing simply HTML/CSS/JS — and now I’m sharing it with the neighborhood to discover the place it may possibly go subsequent.
Core options
- Serve any folder on port 9001 (or use behind NGINX)
- Constructed-in
sitemap.xml,robots.txt,.env,.zinignore - Sensible templates: Nested layouts utilizing
template.html - Clear URLs like
/about→about.html - Variable rendering:
{ "fallback" } - URL rewriting by way of
zin.config
Zin Tags
<zin-time />→ Date, time, math & timezone formatting<zin-include />→ Embrace partials and even.mdrecordsdata<zin-data />→ Load from MySQL, APIs, JSON, CSV, Google Sheets<zin-repeat />→ Loop over dynamic knowledge<zin-form />→ Safe kind + Google reCAPTCHA- Plus:
<zin-set />,<zin-random />,<zin-crypto />and extra
Why I’m sharing?
It’s nonetheless underneath improvement, however It’s usable and works nice for me, however I need to enhance its internals (particularly optimization & parsing). I’d be grateful for those who strive it out, break it, recommend concepts, or assist form what it might turn into.
Recognize all of your ideas, concepts, or contributions ![]()
Let’s maintain plain HTML highly effective.
1 Like
I see an emoji-filled README with no code. I feel the actual query persons are going to have (assuming you really get a repo up someplace) is: why use this over htmx? Additionally the go reddit sub has been flooded with open supply initiatives written by LLMs so one of many first issues I’ve been checking these days is to ensure there’s some commit historical past. The place’s your code?
2 Likes
Thanks for the suggestions.
ZIN is a private venture I work on in my spare time, so issues transfer regularly. The core repo is open right here for those who’re curious: https://github.com/zin-engine/core. I normally push updates as I iterate on options or internals.
HTMX – I actually respect what it does. ZIN takes a distinct strategy, focusing extra on server-side simplicity utilizing Go, and not using a construct step or additional tooling. Not meant to switch something, simply exploring a distinct route I’ve discovered helpful.
Completely satisfied to listen to ideas or concepts you probably have any. At all times open to useful enter.
That hyperlink doesn’t work. I’m questioning you probably have a repo that’s by chance personal. Attempt viewing that hyperlink from a browser the place you aren’t logged in to GitHub to see what we’re seeing.
Repo visibility’s been up to date. It was personal throughout preliminary share, must be good now.
1 Like
A fast part on how you can use it with some code examples would actually assist. For a brand new instrument I’d say much less is extra. A single README file that has all the things you want to get began can be higher than a bunch of recordsdata unfold throughout a number of folders and repos.
Additionally, being Home windows solely is sort of a constraint contemplating most servers are Linux.
Thanks for the suggestions, Adam. I’ll trim down the pointless noise within the repo and add clearer documentation with a fast demo.
As for Linux assist, I’m already engaged on it and will probably be rolled out quickly.
1 Like
HTMX is already the undisputed commonplace for HTML-over-the-wire in Go. Inventing customized markup tags (<zin-...>) is preventing the unsuitable battle.
The true problem within the Go neighborhood isn’t changing HTMX—it’s how you can scale HTMX when constructing superior, multi-modular methods (enterprise ERPs, desktop utilities, and mobile-first apps) the place easy HTML partial swaps aren’t sufficient on their very own.
For these advanced use circumstances, Hyperstack https://github.com/hyperlibs/hyperstack naturally emerges because the Go-native extension:
- 100% Go Customary Library: Kind-safe Go Part DSL (
VStack,HStack,DataTable), zero CGo, zero third-party dependencies, single-binary distribution. - Immediate 0ms Reactivity: Mild alerts (
HxBolt) deal with native tabs, toggles, and modals client-side with out firing pointless HTTP/WebSocket roundtrips to the Go server. - Enterprise-Grade: Handles 10k-row virtualized grids, dwell Go channel SSE streaming, and 0–9 spatial layer stacking for desktop/cell viewports with zero Node.js/npm tooling.
- Full Linux/macOS/Home windows Parity: Verified with 168 exams and actual byte-for-byte bundle budgets.
HTMX gives the hypermedia basis; an structure like Hyperstack makes it viable for high-complexity, multi-modular utility improvement in pure Go.
1 Like

