Pannonico is a static site generator I have been building around the way I actually want to work on static sites.
For many years I have been using...
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
This is a really compelling direction, especially because you’re not trying to turn static-site generation into another JavaScript framework.
The architectural choice to keep HTML/Markdown, layouts, partials, and structured data at the center while treating Vite as an optional first-class build component makes a lot of sense. It preserves the simplicity that made tools like Panini valuable while addressing the realities of modern frontend workflows.
The benchmark is particularly interesting. The 10,000-page results suggest Pannonico is already competitive with Hugo and ahead of Eleventy in several workloads, while the Vite integration demonstrates that the architecture can handle a more realistic asset pipeline without forcing an SPA model.
I also like the emphasis on predictable, “boring” software. For developer tooling, long-term stability, deterministic builds, excellent error messages, incremental builds, and reproducibility often matter more than having an enormous feature set.
The areas I’d be especially interested in watching as the project matures are incremental rebuild performance, caching strategy, determinism across environments, plugin/API stability, and how the MCP integration handles project context without making the development workflow unnecessarily complex.
25+ years of frontend experience combined with modern tooling and AI-assisted development is a strong foundation for this kind of project. It feels less like “another static generator” and more like an attempt to preserve the best parts of the old workflow while removing the friction accumulated over the years.
Definitely worth following as the beta evolves. If you're open to connecting with developers/teams interested in tooling and long-term collaboration, feel free to reach me on @TG_coolsoftDev. I’d be interested in staying connected and seeing where Pannonico goes.
Thanks Kane, lets be in touch. I don't use Twitter, if this is what you meant, but you can find me on BlueSky here bsky.app/profile/jovanovic.bsky.so... or on Github github.com/vsjov
I don't use it.
then how we can do real-time chat.
Send me your LinkedIn account, we can connect and chat through that platform. I am not using much else besides BlueSky and LinkedIn.
Really interesting project! I especially like the idea of keeping Vite as a first-class citizen without turning the whole site into a JS application.
I'm curious though: how does Pannonico handle the boundary between the static build pipeline and Vite? Do you let Vite own the asset pipeline while Pannonico handles the HTML generation, or do they share more of the build process?
Thanks! The boundary is deliberately manifest-based. Vite owns the frontend asset pipeline: the JS/TS/CSS module graph, plugins, code splitting, hashing, and imported assets. Pannonico owns content, templates, HTML generation, and the final site output.
For production, Pannonico can run the configured Vite build, read its manifest, expose the resolved asset URLs to Go templates, and publish the rendered pages and Vite artifacts as one output tree. Vite can also run externally; Pannonico can consume its existing output.
In development, Vite keeps ownership of its dev server and asset HMR, while Pannonico rebuilds content and HTML. So they share build coordination, but not transformation responsibilities. The handoff is the Vite manifest rather than HTML passing through Vite.
An update: dev.to/vlasterx/pannonico-06-how-a...
You can build dynamic websites using Magic Cloud - 100% open sauce, MIT licensed 😀
The Hyperlambda website itself is created and hosted in a Magic "cloudlet". I edit it using Claude, through Magic's built-in MCP connector. You can see how in the connector.
With the difference being that Magic also runs Hyperlambda (server-side!), allowing you to also create stuff such as (more or less) any full stack apps, in addition to "static frontends" (ofc) ...
Spam is not appreciated. This site desperately needs block option for shilling of this type.
A better solution?
I would like to get to know you better. Would you please contact me? t_g_@coolsoftDev