The source for the Ember.js Guides.
Please see CONTRIBUTING.md.
The Guides' content is in the source
folder. The left nav bar is produced from
data/pages.yml
. lib
contains Middleman plugins, and spec
contains tests
for those plugins.
The Guides are built with Middleman, which runs on Ruby 1.9.3 or newer (2.0.0 recommended).
During build, Middleman will require Aspell to look for misspellings. On Macs, it can be installed via Homebrew:
brew install aspell --with-lang-en
On Windows, you can download an installer, but unfortunately it is unmaintained. On Linux, you can install with your distribution's package manager. On all platforms, you can also build the most recent version from source.
To get started:
git clone git://github.com/emberjs/guides.git
cd guides
bundle
bundle exec middleman
Then visit http://localhost:4567/.
If you have a false hit during spellchecking, you can add the word to /data/spelling-exceptions.txt
.
Words are line separated and case insensitive.
For Windows developers using RubyInstaller, you'll need to download the DevKit and install it using instructions: https://github.com/oneclick/rubyinstaller/wiki/Development-Kit
After you have a proper install, you can then run:
gem install bundler wdm tzinfo-data
gem update listen middleman
If you get an error like this when doing a gem update (or bundle install):
Unable to download data from https://rubygems.org/ - SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (https://rubygems.org/latest_specs.4.8.gz)
- Follow the instructions on this post to install the trust cert.
- Create an environment variable with a name of
SSL_CERT_FILE
(System > Advanced system settings > Environment variables > then "New" under system variables) and set the value to the full path of the cert you installed in step 1. The value should look something likeC:\Ruby21\lib\ruby\2.1.0\rubygems\ssl_certs\AddTrustExternalCARoot-2048.pem
. - Close your shell and re-open, so it loads the new environment variable.
- Try again
- If the error still happens, try running
gem update --system
After these workarounds, you should finally be able to run bundle exec middleman
. You may be prompted by Windows Firewall; Click "Allow access" and you'll be in business!