diff --git a/docs/angular.attrMarkup.ngdoc b/docs/content/api/angular.attrMarkup.ngdoc
similarity index 100%
rename from docs/angular.attrMarkup.ngdoc
rename to docs/content/api/angular.attrMarkup.ngdoc
diff --git a/docs/angular.directive.ngdoc b/docs/content/api/angular.directive.ngdoc
similarity index 100%
rename from docs/angular.directive.ngdoc
rename to docs/content/api/angular.directive.ngdoc
diff --git a/docs/angular.element.ngdoc b/docs/content/api/angular.element.ngdoc
similarity index 100%
rename from docs/angular.element.ngdoc
rename to docs/content/api/angular.element.ngdoc
diff --git a/docs/angular.filter.ngdoc b/docs/content/api/angular.filter.ngdoc
similarity index 100%
rename from docs/angular.filter.ngdoc
rename to docs/content/api/angular.filter.ngdoc
diff --git a/docs/angular.formatter.ngdoc b/docs/content/api/angular.formatter.ngdoc
similarity index 100%
rename from docs/angular.formatter.ngdoc
rename to docs/content/api/angular.formatter.ngdoc
diff --git a/docs/angular.markup.ngdoc b/docs/content/api/angular.markup.ngdoc
similarity index 100%
rename from docs/angular.markup.ngdoc
rename to docs/content/api/angular.markup.ngdoc
diff --git a/docs/angular.ngdoc b/docs/content/api/angular.ngdoc
similarity index 100%
rename from docs/angular.ngdoc
rename to docs/content/api/angular.ngdoc
diff --git a/docs/angular.service.ngdoc b/docs/content/api/angular.service.ngdoc
similarity index 100%
rename from docs/angular.service.ngdoc
rename to docs/content/api/angular.service.ngdoc
diff --git a/docs/angular.validator.ngdoc b/docs/content/api/angular.validator.ngdoc
similarity index 100%
rename from docs/angular.validator.ngdoc
rename to docs/content/api/angular.validator.ngdoc
diff --git a/docs/angular.widget.ngdoc b/docs/content/api/angular.widget.ngdoc
similarity index 100%
rename from docs/angular.widget.ngdoc
rename to docs/content/api/angular.widget.ngdoc
diff --git a/docs/cookbook.buzz.ngdoc b/docs/content/cookbook/buzz.ngdoc
similarity index 100%
rename from docs/cookbook.buzz.ngdoc
rename to docs/content/cookbook/buzz.ngdoc
diff --git a/docs/cookbook.deeplinking.ngdoc b/docs/content/cookbook/deeplinking.ngdoc
similarity index 100%
rename from docs/cookbook.deeplinking.ngdoc
rename to docs/content/cookbook/deeplinking.ngdoc
diff --git a/docs/cookbook.form.ngdoc b/docs/content/cookbook/form.ngdoc
similarity index 100%
rename from docs/cookbook.form.ngdoc
rename to docs/content/cookbook/form.ngdoc
diff --git a/docs/cookbook.formadvanced.ngdoc b/docs/content/cookbook/formadvanced.ngdoc
similarity index 100%
rename from docs/cookbook.formadvanced.ngdoc
rename to docs/content/cookbook/formadvanced.ngdoc
diff --git a/docs/cookbook.helloworld.ngdoc b/docs/content/cookbook/helloworld.ngdoc
similarity index 100%
rename from docs/cookbook.helloworld.ngdoc
rename to docs/content/cookbook/helloworld.ngdoc
diff --git a/docs/cookbook.ngdoc b/docs/content/cookbook/index.ngdoc
similarity index 100%
rename from docs/cookbook.ngdoc
rename to docs/content/cookbook/index.ngdoc
diff --git a/docs/cookbook.mvc.ngdoc b/docs/content/cookbook/mvc.ngdoc
similarity index 100%
rename from docs/cookbook.mvc.ngdoc
rename to docs/content/cookbook/mvc.ngdoc
diff --git a/docs/guide.bootstrap.ngdoc b/docs/content/guide/bootstrap.ngdoc
similarity index 100%
rename from docs/guide.bootstrap.ngdoc
rename to docs/content/guide/bootstrap.ngdoc
diff --git a/docs/guide.data-binding.ngdoc b/docs/content/guide/data-binding.ngdoc
similarity index 100%
rename from docs/guide.data-binding.ngdoc
rename to docs/content/guide/data-binding.ngdoc
diff --git a/docs/guide.expression.ngdoc b/docs/content/guide/expression.ngdoc
similarity index 100%
rename from docs/guide.expression.ngdoc
rename to docs/content/guide/expression.ngdoc
diff --git a/docs/guide.compiler.ngdoc b/docs/content/guide/guide.compiler.ngdoc
similarity index 100%
rename from docs/guide.compiler.ngdoc
rename to docs/content/guide/guide.compiler.ngdoc
diff --git a/docs/guide.css.ngdoc b/docs/content/guide/guide.css.ngdoc
similarity index 100%
rename from docs/guide.css.ngdoc
rename to docs/content/guide/guide.css.ngdoc
diff --git a/docs/guide.di.ngdoc b/docs/content/guide/guide.di.ngdoc
similarity index 100%
rename from docs/guide.di.ngdoc
rename to docs/content/guide/guide.di.ngdoc
diff --git a/docs/guide.ngdoc b/docs/content/guide/index.ngdoc
similarity index 100%
rename from docs/guide.ngdoc
rename to docs/content/guide/index.ngdoc
diff --git a/docs/guide.overview.ngdoc b/docs/content/guide/overview.ngdoc
similarity index 100%
rename from docs/guide.overview.ngdoc
rename to docs/content/guide/overview.ngdoc
diff --git a/docs/guide.template.ngdoc b/docs/content/guide/template.ngdoc
similarity index 100%
rename from docs/guide.template.ngdoc
rename to docs/content/guide/template.ngdoc
diff --git a/docs/guide.testing.ngdoc b/docs/content/guide/testing.ngdoc
similarity index 100%
rename from docs/guide.testing.ngdoc
rename to docs/content/guide/testing.ngdoc
diff --git a/docs/contribute.ngdoc b/docs/content/intro/contribute.ngdoc
similarity index 100%
rename from docs/contribute.ngdoc
rename to docs/content/intro/contribute.ngdoc
diff --git a/docs/downloading.ngdoc b/docs/content/intro/downloading.ngdoc
similarity index 100%
rename from docs/downloading.ngdoc
rename to docs/content/intro/downloading.ngdoc
diff --git a/docs/faq.ngdoc b/docs/content/intro/faq.ngdoc
similarity index 100%
rename from docs/faq.ngdoc
rename to docs/content/intro/faq.ngdoc
diff --git a/docs/started.ngdoc b/docs/content/intro/started.ngdoc
similarity index 100%
rename from docs/started.ngdoc
rename to docs/content/intro/started.ngdoc
diff --git a/docs/testimonials.ngdoc b/docs/content/intro/testimonials.ngdoc
similarity index 100%
rename from docs/testimonials.ngdoc
rename to docs/content/intro/testimonials.ngdoc
diff --git a/docs/tutorial.ngdoc b/docs/content/tutorial/index.ngdoc
similarity index 100%
rename from docs/tutorial.ngdoc
rename to docs/content/tutorial/index.ngdoc
diff --git a/docs/tutorial.step_00.ngdoc b/docs/content/tutorial/step_00.ngdoc
similarity index 96%
rename from docs/tutorial.step_00.ngdoc
rename to docs/content/tutorial/step_00.ngdoc
index dbe38285..e506fcaf 100755
--- a/docs/tutorial.step_00.ngdoc
+++ b/docs/content/tutorial/step_00.ngdoc
@@ -1,4 +1,3 @@
-
@workInProgress
@ngdoc overview
@name Tutorial: Step 0
@@ -16,7 +15,7 @@
The following sample code is our starting point. It is a static HTML page that displays next to
nothing, but it has everything we need to proceed. You can think of this bit of code as our
-prototype template, consisting of basic HTML tags with a pair of angular specific attributes.
+prototype template, consisting of basic HTML tags with a pair of angular specific attributes.
__`app/index.html`:__
diff --git a/docs/tutorial.step_01.ngdoc b/docs/content/tutorial/step_01.ngdoc
similarity index 81%
rename from docs/tutorial.step_01.ngdoc
rename to docs/content/tutorial/step_01.ngdoc
index d96eaeb3..e22adc20 100755
--- a/docs/tutorial.step_01.ngdoc
+++ b/docs/content/tutorial/step_01.ngdoc
@@ -1,20 +1,20 @@
-@workInProgress
+@workInProgress
@ngdoc overview
@name Tutorial: Step 1
@description
Now that we have the basic ingredients in place, let's add some basic information about two cell
-phones to our app.
+phones to our app.
Note: We will usually include only the new code that we added for each step. In this and
subsequent examples, we will leave out code from the previous step that hasn't changed, for
@@ -23,7 +23,7 @@ example:
...
...
-
+
Let's add the following code to `index.html`:
__`app/index.html`:__
@@ -53,18 +53,18 @@ __`app/index.html`:__
## Discussion:
-* It's a static web page! We displayed info about two phones! Yay.
+* It's a static web page! We displayed info about two phones! Yay.
* For those of you playing along at home on your own web servers, did you switch to Step 1 and
-refresh your browsers?
+refresh your browsers?
- * __{@link tutorial Using Git:}__
+ * __{@link tutorial Using Git:}__
From your `angular-phonecat` directory, run this command:
git checkout step-1
- * __{@link tutorial Using Snapshots:}__
+ * __{@link tutorial Using Snapshots:}__
From `[install directory]/sandbox`, run this command:
@@ -78,11 +78,11 @@ into a dynamic web app.
@@ -41,7 +41,7 @@ __`app/index.html`:__
Our data __Model__ (a short list of phones in object literal notation) is instantiated within our
-__Controller__ function (`PhoneListCtrl`):
+__Controller__ function (`PhoneListCtrl`):
__`app/js/controllers.js`:__
@@ -84,7 +84,7 @@ enclosed in curly braces: `{{phone.name}}` and `{{phone.snippet}}`:
* The `ng:repeat="phone in phones"` statement in the `
` tag is an angular repeater. It
tells angular to create a `
` element for each phone in the phones list, using the first
- `
` tag as the template.
+ `
` tag as the template.
* The curly braces around `phone.name` and `phone.snippet` are an example of {@link
angular.markup angular markup}. The curly braces are shorthand for the angular directive
@@ -97,11 +97,11 @@ enclosed in curly braces: `{{phone.name}}` and `{{phone.snippet}}`:
* __Controller:__ At this point, it doesn't appear as if our controller is doing very much
controlling, but it is playing a crucial role: providing context for our data model so we can
establish data-binding between the model and the view. Note in the following how we connected the
-dots between our presentation, data, and logic components:
+dots between our presentation, data, and logic components:
* The name of our controller function (in the JavaScript file `controllers.js`) matches the
{@link angular.directive.ng:controller ng:controller} directive in the `` tag
- (`PhoneListCtrl`).
+ (`PhoneListCtrl`).
* We instantiated our data within the scope of our controller function, and our template
binding points are located within the block bounded by the `
We did a lot of work in laying the foundation of our app in the last step, so now we'll do
something simple, and add full text search. We will also write an end-to-end test, because a good
end-to-end test is a good friend. It stays with your app, keeps an eye on it, and quickly detects
-regressions.
+regressions.
__`app/index.html`:__
@@ -72,7 +72,7 @@ following:
keeps the two in sync.
In this example, the data that you type into the input box (named __`query`__) is immediately
-available as a filter input in the list repeater (`phone in phones.$filter(`__`query`__`)`).
+available as a filter input in the list repeater (`phone in phones.$filter(`__`query`__`)`).
Whenever the data model changes and this change causes the input to the repeater to change, the
repeater will efficiently update the DOM to reflect the current state of the model.
@@ -97,12 +97,12 @@ your browser. This end-to-end test shows the following:
@@ -21,7 +21,7 @@ angular.service.$xhr $xhr} service to make this easy.
The addition of the `$xhr` service to our app gives us the opportunity to talk about {@link
guide.di Dependency Injection} (DI). The use of DI is another cornerstone of the angular
philosophy. DI helps make your web apps well structured, loosely coupled, and ultimately easier to
-test.
+test.
__`app/js/controllers.js:`__
[
{
- "age": 4,
+ "age": 4,
...
- "carrier": "T-Mobile",
- "id": "motorola-defy-with-motoblur",
- "imageUrl": "http://google.com/phone/image/small/640001",
- "name": "Motorola DEFY\u2122 with MOTOBLUR\u2122",
+ "carrier": "T-Mobile",
+ "id": "motorola-defy-with-motoblur",
+ "imageUrl": "http://google.com/phone/image/small/640001",
+ "name": "Motorola DEFY\u2122 with MOTOBLUR\u2122",
"snippet": "Are you ready for everything life throws your way?"
- },
+ },
…
]
@@ -93,7 +93,7 @@ __`test/e2e/scenarios.js`__:
{@link angular.markup double-curly brace markup} in the href attribute values. These represent
attribute bindings, and work the same way as the bindings we saw in previous steps.
-* Note also the use of the {@link angular.directive.ng:src ng:src} directive in the `` tag.
+* Note also the use of the {@link angular.directive.ng:src ng:src} directive in the `` tag.
That directive prevents the browser from treating the angular `{{ exppression }}` markup
literally, as it would do if we tried to use markup in a regular `src` attribute. Use `ng:src` to
keep the browser from eagerly making an extra http request to an invalid location.
@@ -103,11 +103,11 @@ views we will implement in the upcoming steps.
Our app is slowly growing and becoming more complex. Up until now, the app provided our users with
just one view (the list of all phones), and all of our template code was located in the
`index.html` file. The next step in building our app is the addition of a view that will show
-detailed information about each of the devices in our list.
+detailed information about each of the devices in our list.
To add the detailed view, we could expand the `index.html` file to contain template code for both
views, but that would get messy very quickly. Instead, we are going to turn the `index.html`
@@ -142,13 +142,13 @@ two new View templates:
* __The Controller(s).__ We now have a new root controller (`PhoneCatCtrl`) and two
sub-controllers (`PhoneListCtrl` and `PhoneDetailCtrl`). These inherit the model properties and
-behavior from the root controller.
+behavior from the root controller.
* __`$route.`__ The root controller's job now is to set up the `$route` configuration:
* When the fragment part of the URL in the browser ends in "/phones", `$route` service
grabs the `phone-list.html` template, compiles it, and links it with a new scope that is
- controlled by our `PhoneListCtrl` controller.
+ controlled by our `PhoneListCtrl` controller.
* When the URL ends in "/phones/:phoneId", `$route` compiles and links the
`phone-detail.html` template as it did with `phone-list.html`. But note the use of the
@@ -170,12 +170,12 @@ behavior from the root controller.
-
{@link tutorial.step_00 Previous}
+
{@link tutorial.step_06 Previous}
{@link http://angular.github.com/angular-phonecat/step-7/app Live Demo
}
In this step, we have determined that the built-in angular display filters ({@link
angular.filter.number number}, {@link angular.filter.currency currency}, {@link
angular.filter.date date}, etc.) don't handle what we want to do, so we get to create our own
-custom {@link angular.filter filter}.
+custom {@link angular.filter filter}.
In the previous step, the details page displayed either "true" or "false" to indicate whether
certain phone features were present or not. Our custom "checkmark" filter replaces those text
@@ -25,7 +25,7 @@ strings with glyphs: ✓ for "true", and ✘ for "false".
Our filter code lives in `app/js/filters.js`:
-__`app/index.html`:__
+__`app/index.html`:__
...
@@ -37,7 +37,7 @@ __`app/index.html`:__
In the phone details template, we employ our filter for angular expressions whose values are
"true" or "false"; `{{ [phone_feature] | checkmark }}`:
-__`app/partials/phone-detail.html`:__
+__`app/partials/phone-detail.html`:__
{{phone.name}}
@@ -86,23 +86,23 @@ describe('checkmark filter', function() {
* This example shows how easy it is to roll your own filters for displaying data. As explained in
the "Writing your own Filters" section of the {@link angular.filter angular.filter} page, you
-simply register your custom filter function on to the `angular.filter` function.
+simply register your custom filter function on to the `angular.filter` function.
* In this example, our filter name is "checkmark"; our input is either "true" or "false", and we
return one of two unicode characters we have chosen to represent true or false (`\u2713` and
-`\u2718`).
+`\u2718`).
* We created a new unit test to verify that our custom filter converts boolean values to unicode
characters.
-
{@link tutorial.step_00 Previous}
+
{@link tutorial.step_08 Previous}
{@link http://angular.github.com/angular-phonecat/step-9/app Live Demo
}
diff --git a/docs/tutorial.step_10.ngdoc b/docs/content/tutorial/step_10.ngdoc
similarity index 100%
rename from docs/tutorial.step_10.ngdoc
rename to docs/content/tutorial/step_10.ngdoc
diff --git a/docs/tutorial.step_11.ngdoc b/docs/content/tutorial/step_11.ngdoc
similarity index 95%
rename from docs/tutorial.step_11.ngdoc
rename to docs/content/tutorial/step_11.ngdoc
index 34ba7b02..e383f406 100644
--- a/docs/tutorial.step_11.ngdoc
+++ b/docs/content/tutorial/step_11.ngdoc
@@ -1,4 +1,4 @@
-@workInProgress
+@workInProgress
@ngdoc overview
@name Tutorial: Step 11
@description
@@ -15,11 +15,11 @@ Code Diff}
And so we arrive at the last step of this tutorial. Here we define a custom service that
-represents a {@link http://en.wikipedia.org/wiki/Representational_State_Transfer RESTful} client.
+represents a {@link http://en.wikipedia.org/wiki/Representational_State_Transfer RESTful} client.
Using this client we can make xhr requests for data in an easier way, without having to deal with
the lower-level {@link angular.service.$xhr $xhr} APIs, HTTP methods and URLs.
-__`app/index.html`.__
+__`app/index.html`.__