Most golang backends I've seen meanwhile use or switched to using the "gin" framework to build their APIs. A lot of them also have conventions for the frontend

Most golang backends I've seen meanwhile use or switched to using the "gin" framework to build their APIs. A lot of them also have conventions for the frontend, where the assets usually are stored in /public, so they can be go:embed later as an embed.FS instance into the binary. Having said that, there's plenty of examples on github. I'd recommend to take a look at bigger projects or templates and understand how they structured their packages and abstraction levels. E.g. go-admin comes to mind [1] [1] https://github.com/GoAdminGroup/go-admin https://github.com/GoAdminGroup/go-admin [2] https://github.com/gin-gonic/gin https://github.com/gin-gonic/gin