Merge lp:~dholbach/snapcraft/integrate-snappy-tutorials-build-snaps into lp:~snappy-dev/snapcraft/core

[Daniel Holbach]

Integrate all relevant information from https://developer.ubuntu.com/snappy/tutorials/build-snaps/ so it will be easier to maintain the docs for us. Fixed some other small issues along the way.

[lp:~dholbach/snapcraft/integrate-snappy-tutorials-build-snaps]

262. By Daniel Holbach on 2015-10-28

fix typo - thanks David Callé

[Sergio Schvezov (sergiusens)]

thanks!

review: Approve

=== modified file 'docs/intro.md'
--- docs/intro.md	2015-10-22 14:14:28 +0000
+++ docs/intro.md	2015-10-28 15:21:31 +0000
@@ -63,9 +63,9 @@
 under the `./stage` directory.
 
 This `./stage` directory is useful for building outside code that isn't in the
-`snapcraft.yaml` recipe against the snap contents. For example, you might build a
-local project against the libraries in `./stage` by running
-`snapcraft shell make`. Though in general, you are encouraged to add even local
+`snapcraft.yaml` recipe against the snap contents. For example, you might 
+build a local project against the libraries in `./stage` by running `snapcraft 
+shell make`. Though in general, you are encouraged to add even local
 projects to snapcraft.yaml with a local `source:` path.
 
 ### Snap
@@ -75,15 +75,18 @@
 area which may include some development files not destined for your package.
 
 The Snappy metadata information about your project will also now be placed in
-`./snap/meta`.
+`./snap/meta`. Snapcraft takes care of generating all the meta-data Snappy
+expects. For a breakdown of what this is, have a look at our [Snappy developer
+reference](https://developer.ubuntu.com/snappy/guides/packaging-format-apps/).
 
 This `./snap` directory is useful for inspecting what is going into your snap
 and to make any final post-processing on snapcraft's output.
 
 ### Assemble
 
-The final step builds a snap package out of the `snap` directory. This `.snap` file
-can be uploaded to the Ubuntu Store and published directly to Snappy users.
+The final step builds a snap package out of the `snap` directory. This `.snap` 
+file can be uploaded to the Ubuntu Store and published directly to Snappy 
+users.
 
 # Next
 

=== modified file 'docs/your-first-snap.md'
--- docs/your-first-snap.md	2015-10-01 08:54:15 +0000
+++ docs/your-first-snap.md	2015-10-28 15:21:31 +0000
@@ -275,8 +275,8 @@
       golang-static-http:
         plugin: go
         source: git://github.com/mikix/golang-static-http
-      fswebcam:
-        plugin: ubuntu
+        stage-packages:
+         - fswebcam
       glue:
         plugin: copy
         files:
@@ -300,10 +300,29 @@
     cd snapcraft/examples
 
 In `examples/` you can find a diverse set of examples which should help you
-get started on your own projects.
+get started on your own projects. To get a good overview of the snapcraft 
+features used in these examples, check out 
+[this article](snapcraft-advanced-features.md).
 
 If you should have any more questions, ask us on
 
  * `#snappy` on `irc.freenode.net` or
- * the [snappy-app-devel](https://lists.ubuntu.com/mailman/listinfo/snappy-app-devel)
-   mailing list
+ * the 
+   [snappy-app-devel](https://lists.ubuntu.com/mailman/listinfo/snappy-app-devel)
+   mailing list.
+   We recommend you subscribe to this mailing list where discussions around 
+   snap apps take place, this will keep you up to date with new capabilities 
+   for your snappy app, and best practices from fellow developers.
+
+### Publish your app to snappy users
+
+We'll be happy to help you on the mailing list to build a snappy package of 
+anything that you are interested in. Choose a good name for it, and you can
+very easily share it in 
+[ubuntu myapps](https://myapps.developer.ubuntu.com/dev/click-apps/?format=snap)
+where you go to share it with other snappy users.
+
+This is the same underlying hub that we use for Ubuntu phone apps, but 
+snappy is a new iteration of that system. It only takes minutes from time of 
+upload to being available to end users. The goal is to deliver your app 
+directly to users instantly — you push a new version, they get it.