File Structure

File Structure

Note: Highlighting the most relevant folders/files below.



Contains a list of all meteor packages installed for the app.
The ones that have a : (e.g. twbs:boostrap) mean that they are third-party packages.
Packages like [email protected] and [email protected] mean they are native Meteor packages.
You can search for meteor packages on


Contains the client-side code.


We use SASS. If you want to create a new SASS file, name it '_yourfile.scss' and be sure to @import it in style.scss.
For a quick introduction to SASS, please read


Contains the dictionary for keywords defined throughout the app.
You'll find use case examples sprinkled throughout the HTML files underneath client/templates. They follow a bracket format with an underscore at the begininng, like {{_ "keyword"}}.
For example, <h4 class="modal-title text-center">{{_ "start_a_hangout"}}</h4> on line 6 in client/templates/hangout/hangout-clone.html points to "start_a_hangout": "Start a Hangout", on line 24 in i18n/en.i18n.json.
So the meteor app will render {{_ "start_a_hangout"}} as "Start a Hangout" text on the front-end.
The "Start a hangout" text appears on multiple buttons throughout the website; if we ever wanted to change this text globally, we'd only need to tweak the i18n/en.i18n.json file.
es.i18n.json contains Spanish translations.


Key files in here: collections.js (defines all the collections) and routes.js (defines the routes).


Contains email notification HTML tempaltes and the meta tags for SEO.


Contains the images directory.


Contains server-side javascript code, including publications.


All the files we don't want to push.


Code of Conduct for the project.

README for the project.


This file holds the settings you're running when you type meteor --settings settings-development.json to run the app. Note that it contains dev (not production) API keys.
Last modified 3yr ago