more comments
Finally ready to call this the official first version, v0.1.0
chore(grunt): set up git-changelog for automatic changelog generating

I like the AngularJS community's approach to generating a categorized changelog based on labelled commit types, and the git-changelog project was designed to allow others to implement the same system. It doesn't look like it's completely bug-free (yet), but it should give me a good starting point. See: https://github.com/rafinskipg/git-changelog
feat(layouts): refactor shared template code and added top navigation bar

There is now no more duplicated layout code (eg. header and footer) between the CMS and WWW codebases; those shared components now live in `views/common/`. This does mean they're coded in EJS and are rendered by Node instead of Angular, which I'm not thrilled about, but for the time being it's the best solution. The good news is that the mobile view especially looks a lot cleaner now, and is more user-friendly thanks to the sticky top navigation bar to help the user get around the site.
chore(git): ignore a file in preparation for release

For some reason git-changelog generates two changelog files instead of one. I'm going to auto-ignore the minimal version for now because I'm not sure what value it adds. Eventually, I think I'd like the minimal version to auto-update README.md, but I don't think that would work well in its current state.
chore(release): release v0.2.0

Although there isn't a ton of new functionality, I figured the layout refactor and added navigation bar change both the developer and user experiences enough to merit a release.
fix(signup/login): improve visual styling and message display

I copied the signup and login forms pretty much verbatim from a sample Foundation form I found, but I was never truly happy with the way they looked. I cleaned them up so that things align better now, and it looks better both on desktop and mobile.
chore(sails): add config/local.js.example file

Sails by default ignores the config/local.js file, which is probably the right course of action, but there should probably be an example file if anybody other than me wants to work on developing this at some point.
fix(MainController): use the appName setting to define the page title programmatically

I should probably look for other places where we should similarly be using `sails.config` to reference global settings data, but this seemed like the most obvious need to start with.
feat(signup): add optional ReCAPTCHA to the signup form, with a custom responsive theme

The CAPTCHA is optional; details on how to add your API keys have been added to the README file. If you don't add your API keys either to `process.env` or config/local.js, then ReCAPTCHA won't be initialized and the signup form will display as it always has: without the CAPTCHA. Additionally, since ReCAPTCHA doesn't ship by default with a responsive widget, the display is customized to ensure it displays properly at small breakpoint.

Credit for the responsive widget goes to https://github.com/chrisvanpatten/responsive-recaptcha