Document use of Cloud Native Buildpacks

[c0d1ngm0nk3y]

Preview: https://cnb-docs-preview.cfapps.sap.hana.ondemand.com/buildpacks

Note that the content of this page changes!

part-of: #310

[pspinrad]

Hi @c0d1ngm0nk3y -- good idea to create a sub-level for buildpacks in the table of contents, but it would cause trouble to move all the source files themselves down a level, because they're linked to from lots of other places in the CF docs and elsewhere on the web, so all of those URLs would no longer work.
WDYT would be a good strategy for adding Cloud Native buildpack pages without messing with existing file structure? /cnb subdirectory, or cnb filename prefix or suffix?
Re: terminology, in the Tanzu docs, for example this page, we're using terminology "Cloud Foundry buildpacks" and "Cloud Native buildpacks" to differentiate between the older and newer buildpack types. "Classical" here refers to the CF buildpacks in that terminology, right?

[pspinrad]

Hi @c0d1ngm0nk3y -- thanks for your continued work on this. I'm not merging yet here or in docs-book-cloudfoundry because the build pipeline is still broken, sorry for delay! Once that's fixed, can publish all this great new stuff and verify that it all works.

[anthonydahanne]

Typo:

Suggested change

	You can the [paketo](https://paketo.io/) buildpacks as one implementaion of Cloud Native Buildpacks. You will find buildpacks for the most popular languages, like
	You can use the [paketo](https://paketo.io/) buildpacks as one implementation of Cloud Native Buildpacks. You will find Paketo buildpacks for the most popular languages, like

[anthonydahanne]

Suggested change

	In this case <em>all</em> buildpacks must `detect` and `build` is called in the given order.
	In this case <em>all</em> buildpacks must run `detect` and `build` in the given order.

[anthonydahanne]

@pivotal-david-osullivan apparently I don't have approving rights here; could you please approve?
I've reviewed it, just few typos to fix
Thanks!