Nibbl 2.0 is made up of 5 major file components:
.meteor
client
server
lib
public
.meteor
This folder contains the meteor framework algorithm required by each Meteor JS system to link to the system. All code within this folder was derived from the installation of Meteor as Nibbl’s main framework. All documentation on Meteor can be found on their website documentation page, http://docs.meteor.com/#/basic/.
client
Contains all client side code that can be accessed by the client and is rendered on the website browser. Client contains four main subsections. 

The *.html files subsection; that contains numerous files each containing a HTML template that executes a fragment of code. 

The Stylesheets folder that contains *.css files that dictate the styling of those HTML templates. 

The JavaScript folder that contains the *.js files. Each *.js file contains template helpers, template events or template rendered functions. The template helpers are used to define Meteor functions or variables that can be used by the *.html files.  The template events describe Meteor events and their appropriate functions, such as a button click resulting in a particular action. The template rendered functions are automatically called when the intended template in a *.html file is rendered.

A local collection is also kept client side for purposes of speed and efficiency. This is the miniMongo database. All schemas that are within the MongoDB collections are replicated onto miniMongo.
server
It contains all server-side code that is not directly accessible to the client. All code contained in this section runs on the server. Contained within this are three main subcomponents.

The main collections. This contains all the database information on Nibble 2.0. Some of the main collections that may be mentioned in documentation are the userData, friends, conversation, notifications, messages, blogPosts and blogCategories collections. The difference between the server database and the local one, is the presence of collection allow, deny, update, insert and remove functions within the server-side database. These functions are server controlled and used to regulate data manipulation in the databases.

serverMethods are contained within *.js files. These are meteor methods that can be run on the client when a meteor call is used. These methods run on the server for purposes of efficiency or safety, at which point the server returns the results to the client. Example of these methods are the searchFriends() and returnResults() for the friends and blog search respectively.

twitterKeys.json file contains the Twitter keys needed to access Nibbl’s page on Twitter. This is then used for Twitter feeds.
lib
This component contains all language files used in localization and the route files used by Meteor to find templates in files. The i18n folder contains 6 main language files english, spanish, portugese, german, italian and french. The routes folder contains the router.js that has routing information used by Meteor.
public
Resources used by Nibble 2.0 are contained within this folder. They include images and sound files. Images are used in various places throughout the system. The sound files are used by the sound template for notification sounds.