Better repository/examples layout

[paddycarey]

How can we better organise the examples in the repository to make them easier to navigate and find?

Do we add an extra level of organisation and group examples by language/format with sub-folders for tooling types? e.g. examples/python/cli instead of examples/python-cli

[lskillen]

I think the following structure makes sense (so we can link it from on-site easily):

/examples/
  /<package-format>/
    /<build-system>/
      /<method/type>/

E.g. For Maven it might be something like:

/examples/maven/maven/cloudsmith-cli/
/examples/maven/maven/native/
/examples/maven/maven/wagon/
/examples/maven/leiningen/cloudsmith-cli/
/examples/maven/leiningen/native/
/examples/maven/leiningen/wagon/
/examples/maven/sbt/cloudsmith-cli/
/examples/maven/sbt/wagon/
/examples/maven/sbt/native/

Each level will require a README.md to point users in the right direction (just examples):

/examples/maven/README.md:

# Language

## Scala

The "sbt" directory provides examples for building, uploading and retrieving packages using sbt.

/examples/maven/sbt/README.md:

# Sbt Version

## 0.x

Versions before 1.x require the use of the <link>Cloudsmith Maven Wagon</link> in order to upload packages. The "wagon" directory provides an example of integrating with Cloudsmith, and will allow you to use the native "sbt publish" functionality. You can also use the Cloudsmith CLI instead, as shown in the "cloudsmith-cli" example.

/examples/maven/sbt/native/README.md

# How To Build

You can build the sbt native project by doing the following:

Comments on a post card. :-)