Per discussion in: https://github.com/kubernetes/dashboard/issues/65

This change does only renaming, no functional modifications.

This is to show in a simple layout what the backend returns.

Based on mocks:
https://github.com/kubernetes/dashboard/blob/master/designs/11-11-2015/08_deploy%20form.png

This change implements both backend and frontend for the view. This is
the approach I'll follow in the future.

1. This is a model for mocks:
https://github.com/kubernetes/dashboard/blob/master/designs/11-11-2015/16_card%20variations.png
2. Did little renaming (used the word "microservice") until we agree what the list exactly shows.
3. The implementation is very basic and will evolve over time.

This is a simple end-to-end implementation for to make sure that the setup works.

The implementation is basically a test one. It'll to verify that
end-to-end setup of the application works.

After this change local development servers do not serve from the repository root. The reason is that the root contains .git folder which may include confidential information.

This is all boilerplate that sets up the page, with some example
content. This change alsu updates angular material to newer version.

This change makes it possible to run tests, integration tests and lint
on Travis CI. It also prepares a special Gulp task to perform the same
activities locally. This is handy when, e.g., sending a pull requrest.

This simple setup will be used for handling calls to the API, once
implemented.

It is a little bit overengineered. But I wanted to have go tests for
something. So I made it accept an interface.

Once unit and integration tests are hooked to travis, such errors should
not happen again.

This change is mostly boilerplate for the two views and cleanup of test
code that has been laying around.

Webpack is much faster and does not do extensive file processing. This
means that when there is a syntax error, webpack often works correctly.

One downside is that I had to disable ng-strict-di. Will work on this
later to reenable it.

This is a chrome that has Kubernetes-like color palette.

This is to have unified codebase from the beginning of the project.

This commit changes all occurences of word "console" to "dashboard".

The rename was required due to collision with an other project.

This change implements initial version of the chrome. It uses ui.router
for routing and state management. The reason to use this router is the
fact that it is more flexible than stock one. It also resembles Angular2
router, so hypothetical migration should be easier.

This change modifies a lot of JS, but this is only to prove that the
code works. Later changes will cleanup the JS more.

Added a few simple rules to the linter and fixed all errors through the
codebase. This will allow to wire it up to some automatic checks.

This is first iteration that works now. It is likely to evolve in the
future.

This is per gmarek's recommendation.

This is a simple implementaion of a HTTP server serving static files
from CWD. It'll be used for development for a next few weeks.

This can be tested with `# go build console.go` and then `# ./console
--port=8081`.

With this change advanced optimizations of the Closure Compiler work and
produce working output.

Was caused by malformed editor settings.

Next commits will use this configuration to lint the codebase.

This is a sample Angular application written in ES6 with modules. It has
sample unit and integration tests. It was generated with a help of
Yeoman.

Don't mind what the application does right now. I'll use it for a next
few days to verify that build system is working. Then it will be
revamped.