| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| Name | Name | Last commit date | ||
|---|---|---|---|---|
Repo for the ionicframework.com site. To preview local Ionic changes, follow the instructions at the Ionic repo.
gulp watch uses LiveReload. You may have to up your max file limit with the following command:
ulimit -n 7000
Run npm install
Install gems (Jekyll and kramdown): npm run bundle-install
This will re-construct your Gemfile.lock for the specific platform you are developing on and exclude it from Git. If you need to make a change to the Gemfile, or are updating gems, you will need to remove the Gemfile.lock from .git/info/exclude.
Run gulp watch (after the first run, this is the only step needed)
Ionic v1 and v2 now automatically deploy their changes to an Ionic staging server. Ionic team members are given permission to the staging and production servers in Heroku. V1 and V2 docs changes go as follows:
3rd part libraries should be concatonated in to the site bundle by adding them via package.json and specifying what files to include in the assets/3rd-party-libs.json file.
Changes to master are automatically deployed to ionic-site-staging.herokuapp.com/. Periodically, the core framework will inspect staging and promote it to ionicframework.com.
Occasionally, people get a Jekyll error the first time they run gulp watch. Try deleting Gemfile.lock and re-running bundle install and then try again. Be sure to set your local git to exclude the changed Gemfile.lock file.
| Back | FazBrowse Home | New Git URL |