Skip to content
Han Ngo edited this page Apr 10, 2015 · 2 revisions

Golang Guides

Welcome to the open-source Golang Guides. Our goal is to become the central crowdsourced resource for complete and up-to-date Golang content and tutorials. Just take me to the notes!

Golang Vietnam

We have guides for everyone whether you are beginner, intermediate or advanced. We got you covered. We don't waste time with the "theoretical approach" from a book. We cover exactly the things we use every day as we are developing apps for contracts.

Need Help? Please join the slack groups for these guides where you can post related questions.

Motivation

Ever been frustrated finding information on outdated one-off blog posts and tutorials that has since become irrelevant? How many times were you googling only to find your answer only on a 2 year old StackOverflow post? We believe there's got to be a better way. Why not have the community work together to create useful and detailed documentation for every aspect of Go (or any platform)? There's absolutely no reason that we should have to make do with outdated, vague or un-editable content anymore.

Overview

The cliffnotes below are categorized by their topic, so you can easily find guides on related topics whether that is views, styling, testing, or using sensors. If you see an error, incorrect explanation or deprecated solution, why not contribute back and make these cliffnotes better for the next person? That in a nutshell is the core spirit of this initiative. Check out the list of contributors to this project.

Disclaimer: We have scoured the web endlessly for content while creating these guides and adapted content from many source that had hidden gems of information. At the bottom of each guide, there are citations for the content we used. We don't claim the content is original (although we did develop quite a bit ourselves), but unlike those other sources listed, it is freely community editable. We have openly adapted, modified and brought together this content from all the sources we could find for the benefit of every engineer.

Read more about [us and our vision] for all this. If you want to contribute to this guide, please read the Contributing Guidelines.

Getting Started

Totally new to Go? Start here.