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
- Install jekyll:
bundle install - Run
npm install - 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:
- Change the content of the docs as necessary.
- Optionally preview the changes by running
gulp docsin the Ionic v1/2 repo, andgulp watchin ionic site, which should be a sibling directory of theionicandionic2repos. - Commit and push changes
- Sit back. The Ionic v1 CI tasks and the Ionic v2 CI tasks will generate the new docs and push them to the
ionic-siterepo. Theionic-siteCI tasks will then build them and automatically deploy them to the staging server. - Preview changes on the staging server and promote the changes to production if all looks well. Be sure to give the site a quick look over to make sure things look good.
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.
- Follow @ionicframework on Twitter.
- Subscribe to the Ionic Newsletter.
- Have a question that's not a feature request or bug report? Discuss on the Ionic Forum.
- Read our Blog.
- Have a feature request or find a bug? Submit an issue.
Max Lynch
Ben Sperry
Adam Bradley