Features listed here are the same as on Shout repo, in same order, participating to the feeling of fork with nothing new. Instead of listing features here, we should refer to the website and improve it to make it as current as possible (there was some recent action there, and more coming, so it is reasonable to point there).
Also, this "Why the fork?" section was useful right when we forked, but now it gives unnecessary and lengthy information (it is now the most verbose section of the README!). The Lounge has enough momentum as that point to be treated as its own project.
Finally, shortening this section moves the screenshot back up on the page, and mobile view now has more context in the description.
- Remove minified libs and compiled templates
- Add a `prepublish` script to build assets, that run on `npm install`
and right before publishing
See https://docs.npmjs.com/misc/scripts
- Include these compiled assets to the `.gitignore` file
- Add an empty .npmignore to make sure the compiled assets are not
ignored when publishing
https://docs.npmjs.com/misc/developers#keeping-files-out-of-your-package
- Update the README to reflect changes in development
Note that the Travis CI configuration does not need any tweaking
because it cleans up all extra and changed files, up to publishing on
npm. That is, right before `prepublish` gets run.
See https://docs.travis-ci.com/user/deployment/npm#Releasing-build-artifacts
Hosting Shout on Heroku (free tier) doesn't really work that well. The reason is that Heroku seems to be powering down inactive dynos, causing Shout to disconnect.
While Heroku will still be supported, the install instructions will be moved to the documentation instead.
