Added comment
Added, a loading hook that will show the loading template until the post subscription is loaded. Since it is global this process will once occur once.
The subsciption is now being handled by the lib/router.js in the waitOn function.
Added the sacha:spin package, and the include template that connects the spin-loading package.
Created a postPage Template and connected the route for the post page
Added info about Data contexts
Forgot the undersocre on the id so there was not defined path.
Added a discuss button that takes you to the indv. post page. The path is defined in lib/router.js
Updated Meteor, and Iron router
Clearified comment
Added account packages. Moved the header to a seperate template to clear up the orginization. Also creates a configure file for the accounts that is located at helpers/config.js. Need be you can spedify the login/sing-up configuration
Just using this as a code playground
Created the post submit functionality. That inclued a post submit template plage and a post submit event function that puts the generated post into the  DB and then uses Router.go callback to bring you to the post page
Removed the insecure package, thus had to make an allow function, to allow logged in users the ablity to submit posts
Created a access denied template, that is connected with the onBeforeAction call, tided directly with the postSubmit route. When said route is clicked it will call the requireLogin function that checks if the user is logged in. If the user is not logged in, it will use iron routers paused buit-in func to stop the route from doing anything and display the accsess denied template.
Modified the requireLogin function to make it a smother tranz, it now checks to see if the user is currently loggin in and if they are then it will display the loading template
Added an spacebar if statment to hide the post submit link. This is the equivalent of Meteor.user()
Brief method desicription added
Updated methods, with call function
Since we are tying to add a timestamp/user passed into the post we are going to do it on the server-side. We do this by doing a Call, and we pass the name of the method 'post', and then we pass an argument to the call which in this call is post. If everything is a-ok then it will render the post page. Additionaly, we removed the posts.allow since the posting will now be handeled on the server-side so there is no need for this check anymore.