As part of the new website, we'll add a Getting Started guide for developers who are new to Go and have decided to try Go kit as their introduction to microservices. They want fast feedback cycles and plug-and-play code wherever possible. The guide should assume no microservice knowledge and provide gentle introductions to concepts, with links to further information as appropriate.

As part of the new website, we'll add a Getting Started guide for developers who have a good deal of experience with microservices and frameworks in other languages, and have decided to try Go kit as their introduction to Go. They will need additional help with Go idioms, and comparing/contrasting concepts they're already familiar with against Go kit's domain language.

Right now to contribute to this repo, the instructions have you edit the files in _src, run make to generate the site, then commit both. A contribute has to remember to generate the final output, and the reviewers need to look at both (and check that the html pages are generated from the same markdown revision).

We can change master to contain only the source files, and use Travis CI's GitHub Pages Deployment to deploy to the gh-pages branch automatically.

I think this would make it easier to contribute to the website, and easier for reviewers to review changes.

I'm happy to make the changes and contribute the .travis.yml, if this is something you agree with.

I am Chinese gopher,We want to translation gokit.io to go-kit.cn . Can we do that?
Sorry, I did not find the email address .

Bug report

The stringsvc1, stringsvc2, stringsvc3, addsvc/cmd/addcli and package profilesvc/client links under https://gokit.io/examples/stringsvc.html are pointing to wrong place.

I saw this PR that updates the example links but I guess, https://gokit.io/examples/stringsvc.html is missed.

Example screenshot

• Introduction — Understanding Go kit key concepts
  • Transport, Endpoint, Service
  • Middlewares in general
  • Endpoint Middleware, Service Middleware
• Dependency Injection — How do I wire up my Component Graph?
• Configuration — How should Go kit services be configured?
• Persistence — How should Go kit services manage persistence?
  • Repository pattern
  • e.g. In-Memory & PostgreSQL
• Caching — How should Go kit services interface with cache systems?
• Logging — How should Go kit services manage logs?
• Metrics — How should Go kit services be instrumented?
• Service Discovery — How should Go kit services interact with service discovery systems?
• Templating — What if Go kit services want to render web pages?
• How do I decide where to place a bit of functionality?

I'm trying to follow the tutorials, specifically https://github.com/go-kit/go-kit.github.io/blob/source/_src/examples/stringsvc.md, and it refers stuff that seems to have been changed.

For example, metrics.TimeHistogram does not seem to exist anymore.