The "Standard Go Project Layout" is not an official standard nor is its use suggested by Go. Its shortcomings don't imply shortcomings in Go.

This issue doesn't constitute an actual proposal; it doesn't propose how to make such a change in a way that's compatible with existing requirements. It doesn't contribute anything new over #58519 (nor #58525). That makes this issue unactionable.

This is still relevant, considering the Standard Go Project Layout[...] Please don‘t come up with hacks like an embedding script in ., this defeats the purpose of the Standard Layout.

Do be aware that the so-called "Standard Go Project Layout" is anything but a standard; you should take it with a hefty punch of salt when citing it as a motivation.

The official Go Docs do recommend a similar layout.

The current go:embed limitation does indeed collide with the layout recommendation (section Server project): https://go.dev/doc/modules/layout

My proposal referred to another, which was closed prematurely. You don‘t have to reinvent the wheel…

Related Issues

• proposal: embed: allow embeding files in a parent directory #58519 (closed)
• proposal: embed: treat `/` as module's root in `go:embed` directive #58525 (closed)

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}