Gin Framework
Gin is a fine web framework, but it does not handle the front-end (AFAIK, at least), so that’s up to you. Which means you’ll still have to handle the front-end in Javascript.
BTW, if you are looking for web frameworks that handle more of the front-end, look at Buffalo. But still, you’ll likely have to write Javascript.
Will Go become “full-stack?”
I cannot speak for the Go team.
However, I can read the tea leaves. In my estimation — based on the past 10+ years — I would say there is less than a 1% chance the Go team has any plans to optimize Go for front-end development, other than to support WebAssembly.
But hey, I could be wrong!
Why use Go vs. Node?
Why build backend and front-end in different languages? It lets you use the best tool for each job.
With Go you get compiled code in a single executable for ease of deployment, and in most cases faster execution. And you also get type safety, which you don’t get in Javascript (although you can get it with TypeScript.)
Avoid Dependency Hell
Further, you don’t have dependency hell in GoLang anywhere near the way you do with Node; no node_modules
directory with an infinite number of files and directories (I exaggerate. Well, only a little):

This blog post from a member of the Go team explains in detail why Node dependency management is such as problem and why GoLang is so much better (Note: Read the whole post, not just these headline because reading only the headline might give you the wrong impression of what the problem is.)
Different folks, different strokes
But like Sibert said, it sounds like you’ve already know what you want and that is you want to go with some form of JavaScript. If using the same language is most important to you then have at it. At the end of the day both approaches will allow you to create websites; what works best for you is what works best for you.
But I can say that — having done web development for 20+ years — I really enjoy coding in Go whereas dealing with Javascript and especially Node was always painful to me. So much so that I decided to focus exclusively on backend development (and DevOps) in the past year, and so I no longer do front-end dev, pretty much at all.
For me, life is so much nicer now! And the pay is a lot better, too. 
So it’s up to you to choose what you want. Sibert and I tag-teamed to answer your questions and we’ve given you plenty to go on; now the choice is yours.
P.S. A 3rd Option
But before you go, you might consider a third option. Not as great as Go on the backend, IMO, but better than dealing with Javascript and Node:
#fwiw
Again, hope this helps.
-Mike