#About the book

This book was written to teach how to develop web applications in Go for newbies.

You will create a to do list application as you go ahead in the book. The book aims to teach concepts based on simple yet real examples and not some dummy examples.

There is a code section available in the Github repo. If you are reading somewhere other than github, here's the link to the Github Repo

Read Online Download PDF

##Code The book comes with corresponding code, please use it to understand the book completely, the book is just plain old theory if you do not check the code out.

##Contributing I don't profess to be a God of either Go or webdev or anything in general, and I don't claim that this is the best book for learning how to build web appplications with Go, but I do believe that good things happen when people collaborate, so pull requests are not only appreciated, but they are welcome.

I got feedback from a reddit user that maybe it is too early for me to start writing this book, decades ago, a young student from the University of Helsinki had an endless debate with Andrew Tannenbaum over comp.minix, it was about monolithic kernels, had the student listened to Andrew Tannenbaum, the world probably would not have had Linux. This is the whole point of open source projects, a little initiative from everyone goes a long way.

##Philosophy

• Through this book we want to teach how to develop web applications in Go. We expect the reader to know the basics of Go but we assume the reader knows nothing about how to write web applications
• The book shall comprise of chapters, if the topic is huge and doesn't fit into one chapter, then we split into multiple chapters, if possible.
• Each chapter should be split into logical parts or sections with a meaningful title which'll teach the reader something.
• Every concept should be accompanied by the Go code (if there is any), for sneak peek type sections write the Go pseudo code, writing just the necessary parts of the code and keeping everything else.
• The code shouldn't be more than 80 characters wide because in the PDF versions of the book the code is invisible.
• Brevity is the soul of wit, so keep the description as small as possible. But this doesn't mean that we should just assume that the reader knows the concept and skip it in such cases do explain the concept.
• In the todo list manager which we are creating, we'll strive to implement as much functionality as possible to give a taste of practical Go programming to the reader, but we should mention as a note the other way, suppose you re-implement a function like ParseGlob by listing all html files and using ParseFiles to parse them, we should mention about the function ParseGlob
• The main title should have one #, sections should have 3 #'s note should have 6 #'s (note should have a title too)
• Multi line code should have three tabs indentation, single line of code can be indented using tabs or by backticks.

Written with love in India.

#License:

Book License: CC BY-SA 3.0 License

#Note:

1. The Go Programming Basics section has been adapted from build-web-application-with-golang by astaxie Links were updated to refer the correct aspects of the current book, titles were updated to fit into this book.
2. The gopher in the cover page is taken from https://golang.org/doc/gopher/appenginegophercolor.jpg without modifications.

Links

• Next section: Installation and Tools