Introducing LWDK - A Framework Stack Connecting Vite/Vue and Golang for productivity

213 views
Skip to first unread message

Tulio Rodrigues de Freitas Nascimento

unread,
Jun 21, 2025, 7:21:52 PMJun 21
to golang-nuts

Hi everyone! :waving_hand:
My name is Túlio, I’m 29 years old and from Brazil. I’m developing a web development stack called LWDK, built in Go, that aims to bring automation concepts—similar to what Artisan does for Laravel—into the Go ecosystem.

The stack is installable via CLI, written entirely in Go, and designed to simplify and speed up full-stack web development with Vue (via Vite) and Go.

I’ve created a website where you can download the tool and see it in action: https://lwdk.site13.com.br.
It includes an automatic translation widget for other languages, and I’m currently working on full internationalization of the tool.

While it’s not open source yet (as I’m still working on its core), I plan to make it open in the future. All help is welcome, and if you’re interested in the idea or want to be part of the project, feel free to reach out!

Key features:
  • One command creates a full project structure (frontend + backend)
  • Live reload for both frontend and backend
  • Separation of concerns with clean structure using the [create] command
  • [make:route] generates backend routes automatically in Go
  • [db:sync] syncs and creates database structures with optional pre-sets (great for debugging)
  • And more to come!

:package: Download and learn more: https://lwdk.site13.com.br

Let me know what you think or if you’d like to contribute. Thanks! :raising_hands:

Brian Candler

unread,
Jun 22, 2025, 6:20:58 AMJun 22
to golang-nuts
I observed that you already announced this a few days ago:

If you didn't get any reply to the first announcement, maybe it's because there are already so many other projects working in this space, e.g.

Also, some Go programmers prefer not to work with a "framework" but just directly code to the Go standard library. This article is quite old but still relevant:

Tulio Rodrigues de Freitas Nascimento

unread,
Jun 22, 2025, 9:49:23 AMJun 22
to golang-nuts

Hi Brian,

Thank you for the feedback — I really appreciate the heads-up!

Just to clarify: in the previous message I mentioned that I was developing the stack, while this latest post was to inform that it is now available for download.
So the intention wasn't to repost due to lack of response, but rather to share that it’s finally usable.

That said, I completely understand your point and will definitely take a closer look at the projects you mentioned — although I had done some research, I didn’t come across anything that actually connects and automates both backend (Go) and frontend (Vue 3) in a unified structure, allowing them to communicate seamlessly.

That’s exactly the goal of LWDK: to provide a minimal yet productive environment that makes fullstack web development with Go viable and organized.

Thanks again for the note!

Best,
Túlio

Brian Candler

unread,
Jun 22, 2025, 10:54:37 AMJun 22
to golang-nuts
I'm afraid I don't fully understand: you said "it’s not open source yet", but at the same time it's "available for download", which makes it unclear what you're offering. Binary downloads only? Source code but with a non-OSS license?

I can only speak for myself, but if it's binary download only, I would discount it completely on that basis. It takes a lot of effort to set up a tight enough sandbox to run untrusted code from a developer who is unknown to me.

Tulio Rodrigues de Freitas Nascimento

unread,
Jun 22, 2025, 11:28:23 AMJun 22
to golang-nuts

Hey Brian, I totally understand your perspective — it's valid and actually very important. You're right to be cautious when it comes to running binaries from unknown sources.
 
At the moment, the repository is private, but I’ve been seriously considering making it public/open source soon.
 
Out of curiosity, would you be interested in taking a look at the source code for testing or reviewing purposes? I’d be happy to give you access if that’s something you'd be open to.

Brian Candler

unread,
Jun 22, 2025, 2:09:17 PMJun 22
to golang-nuts
Not really into web development here, sorry. And I do participate in some open source projects, but not private ones.

Shaun Houlihan

unread,
Jun 23, 2025, 2:48:15 PMJun 23
to golang-nuts
Hi Tulio,

I think there is definitely room for tooling that simplifies full stack development with Go (Go + JS/TS framework). It is definitely something I've thought about building, having done this kind of full-stack development myself. (well, actually, I have built little tools for various tasks but nothing for public consumption).

Realistically, though, I think to have any chance of catching on, the tool/framework is going to need to be open source and posted on Github.

Also: you may want to be careful about calling it a "framework" - many Go developers are pretty touchy about that word 😂 (and perhaps for good reason). I'm not entirely clear on the details of it from skimming your website but it looks like most of the functionality is tooling for generating code in Go+Vue, correct?

Best,
Shaun

Tulio Rodrigues de Freitas Nascimento

unread,
Jun 23, 2025, 3:15:13 PMJun 23
to golang-nuts
Hi Shaun,

Thanks a lot for your thoughtful feedback — I really appreciate it!

You're absolutely right: at this stage, it's more of a CLI tool that generates code, not a framework in the traditional sense. The goal is to organize fullstack projects, keeping frontend and backend clearly separated while allowing them to communicate seamlessly.

In the near future, I plan to support schema-based code generation, so the tool can generate backend (Go) and frontend (Vue + Pug) code automatically from templates — including routes, pages, models, and even syncing with the database.

There is a GitHub repository, but it’s currently private. I'm working on cleaning up the code and documenting everything properly. My goal is definitely to make it public soon, hopefully in the next couple of weeks if everything goes well.

By the way — your suggestion to avoid the word "framework" and use something like "stack" instead is perfect 😂  
Go developers do get a bit twitchy with that word, and you're right, maybe for good reason! I'm definitely adopting "stack" moving forward. Thanks for that tip!

The idea behind this tool is simple: to make fullstack web development with Go and Vue more practical and productive. It's not about reinventing anything — just creating helpful shortcuts for building modern apps in a more organized and efficient way.

Thanks again for your support and interest!

Best regards,  
Túlio
Reply all
Reply to author
Forward
0 new messages