THIS FILE NEEDS TO BE MOVED

I don't know where this new page should go. have supplied markdown.

content/docs/app-server.md

@@ -4,67 +4,97 @@ title: Server API for Apps
 
 ## Server API for Apps
 
+Users interact with their own server primarily through apps. They can set permissions for different apps to limit the scope of access and control over the server.
+
 ### GET /profile
 
+Apps can request the user's profile from the server.
+
 {get_profile example}
 
 
 ### PUT /profile/:type
 
+Apps can add or edit information in a user's profile including adding new profile info types. Users choose which apps have permission to make edits and additions to different sections of their profiles.
+
 {update_profile example}
 
 
 ### POST /followings
 
+Apps can tell a server to follow another entity.
+
 {create_following example}
 
 
 ### GET /followings
 
+Apps can also retrieve a list of the entities currently being followed.
+
 {get_followings example}
 
 
 ### GET /followings/:id
 
+Apps can request information on the relationship with a specific entity being followed.
+
 {get_followings example}
 
 
 ### DELETE /followings/:id
 
+Apps can request the server stop following a specific entity.
+
 {delete_following example}
 
 
 ### GET /followers
 
+Apps can get a list of current followers.
+
 {get_followers example}
 
 
 ### GET /followers/:id
 
+Apps can request information on a specific follower.
+
 {get_follower example}
 
 
 ### DELETE /followers/:id
 
+Apps can end the user's relationship with a follower.
+
 {delete_follower example}
 
 ### POST /posts
 
+Apps can create posts by sending them to the server. The server will then send notifications to any entities with permission to see the post and who either requested the post type in their following request or who were mentioned in the post.
+
 {create_post example}
 
 ### GET /posts
 
+Apps can retrieve posts.
+
 {get_posts example}
 
 
 ### GET /posts/:id
 
+Apps can retrieve a specific post.
+
 {get_post example}
 
 ### Post Attachments
 
+Apps can create a new post with an attachment and send both to the server. Files and binary data are usually transferred as attachments to posts.
+
 {create_post_with_attachments example}
 
 #### GET /posts/:post_id/attachments/:name
 
+Apps can retrieve attachments from a specific post by name from the server.
+
 {get_post_attachment example}

content/helptent.md

@@ -0,0 +1,54 @@
+##How you can help Tent
+<span class="lead">Tent is still very young and needs your help. Everyone has different skills and interests that can help.</span>
+
+###Everyone
+####Start using Tent
+Like all social services, the more people who use Tent, the more useful it is to everyone. Either by self-hosting or using a hosting provider, get your Tent server set up and keep it up to date with the most recent software version.
+
+####Promote Tent
+Tell people you know about Tent! Put a link to Tent on your website, advertise your Tent server on your business card and email signature. Give a talk about Tent at your local tech or organization meetup. Email the developers behind your favorite services and ask them to support Tent!
+    
+####Translate 
+The Tent.io and Tent Docs into your native language. Either fork the docs on [Github](https://github.com/tent/tent.io) or [email us](mailto:contact@tent.io).
+  
+###Designers
+####Design for Tent apps and hosts
+The world needs well designed Tent services. Great apps start with great design and UIs. Many apps and hosting providers also support "skins" or "themes" and would love your contribution and help!
+    
+####Design for Core Tent Apps 
+The Admin and Status apps need your help. They are open source projects created by the Tent Team and community. Since there aren't any designers on the Team (yet!) those applications are ripe for a redesign. Both apps are on Tent's [github](http://github.com/tent) where you can share your submissions.
+    
+####Design Tent.io
+Tent.io could use a facelift. Our wishlist includes: diagrams clearly explaining tent to non-technical newcomers, a short (30 second-1.5 minute) Intro to Tent video, and official Tent logo (that users and apps can display and we can put on logo merch). Keep in mind that you must sign over ownership of anything official you create for http://Tent.io. Fan art is great, but official logos and design need to be the exclusive property of the organization running Tent.io for legal reasons.
+
+###Developers
+
+####Develop Tent Apps
+Tent enables new kinds of communication and sharing, developers can unlock that potential. Add Tent support to open and commercial apps or start from scratch. The protocol is still evolving, so stay in touch with the community as you develop.
+    
+####Create Tent Libraries
+Tent needs client libraries for
+ - C
+ - C++
+ - C#/.NET
+ - Clojure
+ - Common Lisp
+ - Erlang
+ - Go
+ - Java
+ - Javascript
+ - Lua
+ - Objective-C
+ - Perl
+ - PHP
+ - Python
+ - Scala
+    
+Existing client libraries need regular maintenance to keep up with Tent as it evolves.
+  
+####Write Tutorials
+Developers coming to Tent need a place to start. Blog articles, Tutorials, Getting Started guides, and code samples are still in short supply. Consider creating 
+  
+####Contribute to the Tent Core
+Tent has many open source elements that need your help and accept pull requests. Applications include tentd, the reference server implementation, TentStatus, a Tent microblogging app, and TentAdmin, a server administration app. Most of these apps were developed to demonstrate basic functionality and shipped with a limited feature set. Additions, changes, and forks are welcome. The documentation accompanying these projects and the Tent protocol are also community curated. All can be found on the [Tent github](http://github.com/tent/). Each has a list of TODO priorities in the readme. 
+