Skip to content
This repository was archived by the owner on May 4, 2022. It is now read-only.

Commit 55b0ada

Browse files
committed
README
1 parent fded25c commit 55b0ada

File tree

2 files changed

+123
-119
lines changed

2 files changed

+123
-119
lines changed

README.md

+4-119
Original file line numberDiff line numberDiff line change
@@ -1,122 +1,7 @@
1-
[![Circle CI](https://circleci.com/gh/driftyco/ionic.svg?style=svg)](https://circleci.com/gh/driftyco/ionic)
1+
## Ionic 1.x
22

3-
[![NPM](https://nodei.co/npm/ionic.png?stars&downloads)](https://nodei.co/npm/ionic/)
3+
This is the repo for Ionic 1.x. If you're looking for the latest version (>= 2.0) of Ionic, please visit the main [Ionic](https://github.com/driftyco/ionic) repo.
44

5-
Looking for our [documentation](http://ionicframework.com/docs/)?
5+
For new apps, we *strongly* recommend the [latest version of Ionic](https://github.com/driftyco/ionic) which comes with the latest version of Angular, many new components, enhanced performance, and more.
66

7-
# What is Ionic?
8-
9-
[Ionic](http://ionicframework.com/) is the open source HTML5 Mobile Framework for building amazing, cross-platform hybrid native apps and mobile websites with HTML, JavaScript, and CSS. If you know how to build or design websites, you will be able to build a real mobile app with Ionic!
10-
11-
We built Ionic because we wanted a framework that focused on building high quality hybrid native apps and mobile web apps using open web technologies we loved. The same technology the world has been using for decades to build websites, desktop applications, and now mobile and tablet apps. We wanted this framework to be obsessive about great design and performance, and work on multiple platforms without changing a thing.
12-
13-
We rejected the idea that web mobile apps had to be clunky, slow, and non-native. We believed that we could bring the best of the web together with the best of the native platforms without sacrificing the power, accessibility, and portability of the open web.
14-
15-
Above all, we built Ionic to be the easiest way for the next generation of developers to get into mobile and start building apps that compete with the best on the app store, and do it affordably.
16-
17-
Today, Ionic powers over 1.5 million mobile apps and websites (and even some desktop apps!), built by small startups up to Fortune 50 companies. Ionic developers come from hundreds of countries around the world, and have helped build a community that boasts hundreds of monthly meetings, conference talks, and workshops; an incredibly active [forum](http://forum.ionicframework.com) and [Theme and Plugin Marketplace](https://market.ionic.io); and some pretty [amazing apps](http://showcase.ionicframework.com/).
18-
19-
## Quick Start
20-
21-
To start using ionic, you have two options: copy over the built JS and CSS files, or
22-
use the `ionic` tool ([ionic-cli](https://github.com/driftyco/ionic-cli)) which can be installed through npm (recommended): _(You may need to prefix the command with `sudo` depending on your OS and setup.)_
23-
24-
Additionally, we have a desktop GUI tool that we recently released called [Ionic Lab](http://lab.ionic.io). If you try it, let us know what you think!
25-
26-
To get started with the CLI flow, fire up your terminal and run:
27-
28-
```bash
29-
npm install -g ionic
30-
```
31-
32-
Then, you can start a new ionic project by running:
33-
34-
```bash
35-
ionic start myproject
36-
```
37-
38-
### Manual Start
39-
40-
If you'd rather do everything by hand, you can grab all the files for Ionic below:
41-
42-
- Download the latest **stable** release from:
43-
* The `release` folder of this repository
44-
* Ionic CDN: [Latest Release](http://code.ionicframework.com/)
45-
* Using bower: `bower install ionic`
46-
* For [Meteor](https://www.meteor.com/) applications: `meteor add driftyco:ionic`
47-
- Download the **bleeding edge just-from-master release** from:
48-
* Ionic CDN: [Nightly Build](http://code.ionicframework.com/#nightly)
49-
* Using bower: `bower install driftyco/ionic-bower#master`
50-
51-
Once you have a release, use `js/ionic.js`, `js/ionic-angular.js`, and `css/ionic.css`.
52-
53-
For most cases, you'll need AngularJS as well. This is bundled in `js/angular/` and `js/angular-ui/`.
54-
55-
## Platform Support
56-
57-
Ionic currently supports Android 4.1 and above, iOS 8 and above, and Windows 10. We continue to monitor market share and adjust our support based on worldwide usage.
58-
59-
## Demos
60-
61-
- [Ionic Codepen.io Demos](http://codepen.io/ionic/public-list)
62-
63-
64-
## Community
65-
66-
* Follow [@ionicframework on Twitter](https://twitter.com/ionicframework)
67-
* Subscribe to the [Ionic Newsletter](http://ionicframework.com/subscribe/)
68-
* Have a question that's not a feature request or bug report? [Discuss on the Ionic Forum](http://forum.ionicframework.com/)
69-
* Read our [Blog](http://blog.ionic.io/)
70-
* Have a feature request or find a bug? [Submit an issue](http://ionicframework.com/submit-issue/)
71-
* Join our Community Slack Group! [Ionic Worldwide](http://ionicworldwide.herokuapp.com/)
72-
* [Ionic Team](http://ionic.io/team)
73-
74-
## Development
75-
76-
* `npm install && npm install -g gulp protractor` to setup
77-
* (if you wish to run end-to-end tests): `webdriver-manager update --chrome` to install the webdriver.
78-
* `gulp` or `gulp build` to build
79-
* `gulp docs` to generate docs (read Documentation below for how to test docs locally).
80-
* `gulp build --release` to build with minification & strip debugs
81-
* `gulp watch` to watch and rebuild on change
82-
* `gulp karma` to test one-time
83-
* `gulp karma-watch` to test and re-run on source change
84-
* `gulp snapshot` to test e2e tests locally (run `gulp demos` first to generate e2e tests). Be sure to run `./node_modules/.bin/webdriver-manager update --chrome` to first install the chrome webdriver dependency.
85-
86-
### Documentation
87-
88-
* Documentation is generated into `./../ionic-site`. To test documentation properly, follow these steps:
89-
1. Clone ionic-site into `./../ionic-site`
90-
- `git clone [email protected]:driftyco/ionic-site ./../ionic-site`
91-
2. Start jekyll, telling it to rebuild whenever the site changes
92-
- `cd ./../ionic-site && jekyll serve -w`
93-
3. Go back to project root and build the docs
94-
- `gulp docs [--doc-version=(versionName|nightly)]`
95-
4. Open localhost:4000 and see your changes! Re-run `gulp docs` again whenever you change something, and jekyll will update the site
96-
97-
### Demos / Kitchen Sink
98-
99-
* The demo site is generated into `dist/ionic-demo`. To test the demos, follow these steps:
100-
1. Run `gulp demos [--demo-version=(versionName|nightly)]`
101-
2. Start an http server from `dist/ionic-demo`:
102-
- `cd dist/ionic-demo && python -m SimpleHTTPServer`
103-
3. Navigate to `http://localhost:8000/{versionName|nightly}` and use the demos
104-
4. Run `gulp demos` again whenever you change the demos
105-
106-
### Commit Conventions
107-
108-
* Uses these [commit conventions](https://github.com/ajoslin/conventional-changelog)
109-
110-
### Pushing New Release of Ionic
111-
112-
- Almost all of the logic for releasing Ionic is done on the Travis server
113-
- To push a new release:
114-
1. Update package.json version to new version
115-
2. Generate changelog with `gulp changelog`
116-
3. Go through the changelog, and fix any mistakes or clarify any unclear commit messages
117-
4. Commit package.json and CHANGELOG.md and push to master
118-
- Travis will detect that this commit changed the version in package.json and push out all necessary for this new release (tags, release files, site config, ...)
119-
120-
## LICENSE
121-
122-
Ionic is licensed under the MIT Open Source license. For more information, see the LICENSE file in this repository.
7+
For more information on Ionic 1.x, please read the [original README.md](README_OLD.md)

README_OLD.md

+119
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,119 @@
1+
2+
Looking for our [documentation](http://ionicframework.com/docs/)?
3+
4+
# What is Ionic?
5+
6+
[Ionic](http://ionicframework.com/) is the open source HTML5 Mobile Framework for building amazing, cross-platform hybrid native apps and mobile websites with HTML, JavaScript, and CSS. If you know how to build or design websites, you will be able to build a real mobile app with Ionic!
7+
8+
We built Ionic because we wanted a framework that focused on building high quality hybrid native apps and mobile web apps using open web technologies we loved. The same technology the world has been using for decades to build websites, desktop applications, and now mobile and tablet apps. We wanted this framework to be obsessive about great design and performance, and work on multiple platforms without changing a thing.
9+
10+
We rejected the idea that web mobile apps had to be clunky, slow, and non-native. We believed that we could bring the best of the web together with the best of the native platforms without sacrificing the power, accessibility, and portability of the open web.
11+
12+
Above all, we built Ionic to be the easiest way for the next generation of developers to get into mobile and start building apps that compete with the best on the app store, and do it affordably.
13+
14+
Today, Ionic powers over 1.5 million mobile apps and websites (and even some desktop apps!), built by small startups up to Fortune 50 companies. Ionic developers come from hundreds of countries around the world, and have helped build a community that boasts hundreds of monthly meetings, conference talks, and workshops; an incredibly active [forum](http://forum.ionicframework.com) and [Theme and Plugin Marketplace](https://market.ionic.io); and some pretty [amazing apps](http://showcase.ionicframework.com/).
15+
16+
## Quick Start
17+
18+
To start using ionic, you have two options: copy over the built JS and CSS files, or
19+
use the `ionic` tool ([ionic-cli](https://github.com/driftyco/ionic-cli)) which can be installed through npm (recommended): _(You may need to prefix the command with `sudo` depending on your OS and setup.)_
20+
21+
Additionally, we have a desktop GUI tool that we recently released called [Ionic Lab](http://lab.ionic.io). If you try it, let us know what you think!
22+
23+
To get started with the CLI flow, fire up your terminal and run:
24+
25+
```bash
26+
npm install -g ionic
27+
```
28+
29+
Then, you can start a new ionic project by running:
30+
31+
```bash
32+
ionic start myproject
33+
```
34+
35+
### Manual Start
36+
37+
If you'd rather do everything by hand, you can grab all the files for Ionic below:
38+
39+
- Download the latest **stable** release from:
40+
* The `release` folder of this repository
41+
* Ionic CDN: [Latest Release](http://code.ionicframework.com/)
42+
* Using bower: `bower install ionic`
43+
* For [Meteor](https://www.meteor.com/) applications: `meteor add driftyco:ionic`
44+
- Download the **bleeding edge just-from-master release** from:
45+
* Ionic CDN: [Nightly Build](http://code.ionicframework.com/#nightly)
46+
* Using bower: `bower install driftyco/ionic-bower#master`
47+
48+
Once you have a release, use `js/ionic.js`, `js/ionic-angular.js`, and `css/ionic.css`.
49+
50+
For most cases, you'll need AngularJS as well. This is bundled in `js/angular/` and `js/angular-ui/`.
51+
52+
## Platform Support
53+
54+
Ionic currently supports Android 4.1 and above, iOS 8 and above, and Windows 10. We continue to monitor market share and adjust our support based on worldwide usage.
55+
56+
## Demos
57+
58+
- [Ionic Codepen.io Demos](http://codepen.io/ionic/public-list)
59+
60+
61+
## Community
62+
63+
* Follow [@ionicframework on Twitter](https://twitter.com/ionicframework)
64+
* Subscribe to the [Ionic Newsletter](http://ionicframework.com/subscribe/)
65+
* Have a question that's not a feature request or bug report? [Discuss on the Ionic Forum](http://forum.ionicframework.com/)
66+
* Read our [Blog](http://blog.ionic.io/)
67+
* Have a feature request or find a bug? [Submit an issue](http://ionicframework.com/submit-issue/)
68+
* Join our Community Slack Group! [Ionic Worldwide](http://ionicworldwide.herokuapp.com/)
69+
* [Ionic Team](http://ionic.io/team)
70+
71+
## Development
72+
73+
* `npm install && npm install -g gulp protractor` to setup
74+
* (if you wish to run end-to-end tests): `webdriver-manager update --chrome` to install the webdriver.
75+
* `gulp` or `gulp build` to build
76+
* `gulp docs` to generate docs (read Documentation below for how to test docs locally).
77+
* `gulp build --release` to build with minification & strip debugs
78+
* `gulp watch` to watch and rebuild on change
79+
* `gulp karma` to test one-time
80+
* `gulp karma-watch` to test and re-run on source change
81+
* `gulp snapshot` to test e2e tests locally (run `gulp demos` first to generate e2e tests). Be sure to run `./node_modules/.bin/webdriver-manager update --chrome` to first install the chrome webdriver dependency.
82+
83+
### Documentation
84+
85+
* Documentation is generated into `./../ionic-site`. To test documentation properly, follow these steps:
86+
1. Clone ionic-site into `./../ionic-site`
87+
- `git clone [email protected]:driftyco/ionic-site ./../ionic-site`
88+
2. Start jekyll, telling it to rebuild whenever the site changes
89+
- `cd ./../ionic-site && jekyll serve -w`
90+
3. Go back to project root and build the docs
91+
- `gulp docs [--doc-version=(versionName|nightly)]`
92+
4. Open localhost:4000 and see your changes! Re-run `gulp docs` again whenever you change something, and jekyll will update the site
93+
94+
### Demos / Kitchen Sink
95+
96+
* The demo site is generated into `dist/ionic-demo`. To test the demos, follow these steps:
97+
1. Run `gulp demos [--demo-version=(versionName|nightly)]`
98+
2. Start an http server from `dist/ionic-demo`:
99+
- `cd dist/ionic-demo && python -m SimpleHTTPServer`
100+
3. Navigate to `http://localhost:8000/{versionName|nightly}` and use the demos
101+
4. Run `gulp demos` again whenever you change the demos
102+
103+
### Commit Conventions
104+
105+
* Uses these [commit conventions](https://github.com/ajoslin/conventional-changelog)
106+
107+
### Pushing New Release of Ionic
108+
109+
- Almost all of the logic for releasing Ionic is done on the Travis server
110+
- To push a new release:
111+
1. Update package.json version to new version
112+
2. Generate changelog with `gulp changelog`
113+
3. Go through the changelog, and fix any mistakes or clarify any unclear commit messages
114+
4. Commit package.json and CHANGELOG.md and push to master
115+
- Travis will detect that this commit changed the version in package.json and push out all necessary for this new release (tags, release files, site config, ...)
116+
117+
## LICENSE
118+
119+
Ionic is licensed under the MIT Open Source license. For more information, see the LICENSE file in this repository.

0 commit comments

Comments
 (0)