As others have suggested, looking through go's std library is a good idea as you will need to be familiar with it in any case. Use https://golang.org/pkg/ liberally to go from reading API documentation to code.
Look at https://golanglibs.com categories and pick the one that interests you or is something you already know a bunch about. Then pick something simple from that category.
There is a library that converts some python libs to go packages. This may also help as you can see how the mapping worked.
Finally, just pick up the Go book and start coding something you care about! Go's online documentation is quite good. I was able to bootstrap 3 high-school interns this way fairly well and they actually produced a fair bit of working code in 7 weeks. IMHO you should spend a significant part of your "study" time writing code. Read other code as and when you need it.
As others have suggested, looking through go's std library is a good idea as you will need to be familiar with it in any case. Use https://golang.org/pkg/ liberally to go from reading API documentation to code.
Look at https://golanglibs.com categories and pick the one that interests you or is something you already know a bunch about. Then pick something simple from that category.
There is a library that converts some python libs to go packages. This may also help as you can see how the mapping worked.
Finally, just pick up the Go book and start coding something you care about! Go's online documentation is quite good. I was able to bootstrap 3 high-school interns this way fairly well and they actually produced a fair bit of working code in 7 weeks. IMHO you should spend a significant part of your "study" time writing code. Read other code as and when you need it.