- - - -- - -# Downloading and hosting the files on your own - -This options is for those who want to work with angular offline, or want to host the angular files -on their own servers. - -If you navigate toMy Angular App - - - - - -
-
-Now let's take a closer look at that code, and see what is going on behind
-the scenes.
-
-The first line of interest defines the `ng` namespace, which makes
-`angular` work across all browsers (especially important for IE):
-
-- -- -The next line downloads the `angular` script, and instructs `angular` to process -the entire HTML page when it is loaded: - -
- -- -(For details on what happens when `angular` processes an HTML page, -see {@link guide.bootstrap Bootstrap}.) - -Finally, this line in the `` of the page is the template that describes -how to display our greeting in the UI: - -
- Hello {{'World'}}!
-
-
-Note the use of the double curly brace markup (`{{ }}`) to bind the expression to
-the greeting text. Here the expression is the string literal 'World'.
-
-Next let's look at a more interesting example, that uses `angular` to
-bind a dynamic expression to our greeting text.
-
-# Hello - Hello {{yourname}}! -
-
-These are some of the important points to note from this example:
-
-* The text input {@link angular.widget widget} called `yourname` is bound to a model variable called
- `yourname`.
-* The double curly braces notation binds the variable `yourname` to the
- greeting text.
-
-* You did not need to explicitly register an event listener or define an event
- handler for events!
-
-Now try typing your name into the input box, and notice the immediate change to
-the displayed greeting. This demonstrates the concept of `angular`'s
-{@link guide.data-binding bi-directional data binding}. Any changes to the input field are immediately
-reflected in the model (one direction), and any changes to the model are
-reflected in the greeting text (the other direction).
-
-
-# Anatomy of an `angular` App
-
-This section describes the 3 parts of an `angular` app, and explains how they
-map to the Model-View-Controller design pattern:
-
-## Templates
-
-Templates, which you write in HTML and CSS, serve as the View. You add elements,
-attributes, and markup to HTML, which serve as instructions to the `angular`
-compiler. The `angular` compiler is fully extensible, meaning that with angular
-you can build your own declarative language on top of HTML!
-
-## Application Logic and Behavior
-
-Application Logic and Behavior, which you define in JavaScript, serve as the
-Controller. With `angular` (unlike with standard AJAX applications) you don't
-need to write additional listeners or DOM manipulators, because they are built-in.
-This feature makes your application logic very easy to write, test, maintain, and
-understand.
-
-## Scope
-
-The Model consists of one or more JavaScript objects, arrays, or primitive types.
-These are referenced from the scope. There are no restrictions on what the Model
-can be or what structure it should have. The only requirement is that it is
-referenced by the scope.
-
-The following illustration shows the parts of an `angular` application and how they
-work together:
-
-
-
-In addition, `angular` comes with a set of Services, which have the following
-properties:
-
-* The services provided are very useful for building web applications.
-* You can extend and add application-specific behavior to services.
-* Services include Dependency-Injection, XHR, caching, URL routing,
- and browser abstraction.
-
-# Where To Go Next
-
-* For additional hands-on examples of using `angular`, including more source
- code that you can copy and paste into your own pages, take a look through
- the `angular` {@link cookbook Cookbook}.
-
-* For explanations of the `angular` concepts presented in the examples on this
- page, see the {@link guide Developer Guide}.
diff --git a/docs/content/intro/testimonials.ngdoc b/docs/content/intro/testimonials.ngdoc
deleted file mode 100644
index 2e333f4b..00000000
--- a/docs/content/intro/testimonials.ngdoc
+++ /dev/null
@@ -1,33 +0,0 @@
-@ngdoc overview
-@name Testimonials
-@description
-
-
-## John Hardy
-> Also I want to pass on my compliments to Misko and Igor for this fantastic project. I'm currently
-> rewriting a server-side web application to use this system. I am constantly astounded at how much
-> simpler it is to do it this way and I still consider myself a learner.
-
-> This is without question the most productive approach to building webapps that I have seen.
-
-> The last time I had a coding epiphany was discovering the power and simplicity of JQuery. This is
-> way better than that.
-
-> I'm interested in promoting this library as widely as possible. I understand that you are still
-> developing it and I still have a long way to go before I really understand everything but I think
-> you really have something here.
-
-
-## Jerry Jeremiah
-> angular is the best thing I have used in a long time. I am having so much fun, even thought it is
-> probably obvious that dynamic web sites are new to me (my experience is more in the back end
-> embedded world...)
-
-
-## Dobrica Pavlinusic
-> Thanks to great help I received at this list, I was basically able to accomplish my goal to write
-> simple conference submission application within a week of first git clone of angular source from
-> github.
-
-> I think it might be useful to summarize my experience here, especially for people who are still
-> wondering if angular is worth a try. Executive summary is: **yes it is!**
\ No newline at end of file
diff --git a/docs/content/misc/contribute.ngdoc b/docs/content/misc/contribute.ngdoc
new file mode 100644
index 00000000..43d17283
--- /dev/null
+++ b/docs/content/misc/contribute.ngdoc
@@ -0,0 +1,233 @@
+@ngdoc overview
+@name Contributing
+@description
+
+
+# Open Source
+
+`Angular` is an open source project licensed under the {@link
+http://github.com/angular/angular.js/blob/master/LICENSE MIT license}. Your contributions are
+always welcome. When working with `angular` source base, please follow the guidelines provided on
+this page.
+
+* Contributing to Source Code
+* Applying Code Standards
+* Checking Out and Building `Angular`
+* Submitting Your Changes
+
+
+
+
+# Contributing to Source Code
+
+We'd love for you to contribute to our source code and to make `angular` even better than it is
+today! Here are the guidelines we'd like you to use:
+
+* Major changes that you intend to contribute to the project must be discussed first on our {@link
+https://groups.google.com/forum/?hl=en#!forum/angular mailing list} so that we can better
+coordinate our efforts, prevent duplication of work, and help you to craft the change so that it
+is successfully accepted upstream.
+* Small changes and bug fixes can be crafted and submitted to Github as a pull
+request.
+
+
+
+
+# Applying Code Standards
+
+To ensure consistency throughout the source code, keep these rules in mind as you are working:
+
+* All features or bug fixes must be tested by one or more specs.
+* All public API methods must be documented with ngdoc, an extended version of jsdoc (we added
+support for markdown and templating via `@ngdoc` tag). To see how we document our APIs, please
+check out the existing ngdocs.
+* With the exceptions listed below, we follow the rules contained in {@link
+http://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml Google's JavaScript Style
+Guide}:
+
+ * Do not use namespaces: Instead, we wrap the entire `angular` code base in an anonymous closure
+and export our API explicitly rather than implicitly.
+ * Wrap all code at 100 characters.
+ * Instead of complex inheritance hierarchies, we prefer simple objects. We use prototypical
+inheritance only when absolutely necessary.
+ * We love functions and closures and, whenever possible, prefer them over objects.
+ * To write concise code that can be better minified, internally we use aliases that map to the
+external API. See our existing code to see what we mean.
+ * We don't go crazy with type annotations for private internal APIs unless it's an internal API
+that is used throughout `angular`. The best guidance is to do what makes the most sense.
+
+
+
+# Checking Out and Building Angular
+
+The `angular` source code is hosted at {@link http://github.com Github}, which we also use to
+accept code contributions. Several steps are needed to check out and build `angular`:
+
+
+## Installation Dependencies
+
+Before you can build `angular`, you must install or configure the following dependencies on your
+machine:
+
+* {@link http://rake.rubyforge.org Rake}: We use Rake as our build system, which is pre-installed
+on most Macintosh and Linux machines. If that is not true in your case, you can grab it from the
+Rake website.
+
+* {@link http://nodejs.org Node.js}: We use Node to generate the documentation and to run a
+development web server. Depending on your system, you can install Node either from source or as a
+pre-packaged bundle.
+
+* Java: The Java runtime is used to run {@link http://code.google.com/p/js-test-driver
+JsTestDriver} (JSTD), which we use to run our unit test suite. JSTD binaries are part of the
+`angular` source base, which means there is no need to install or configure it separately.
+* Git: The {@link http://help.github.com/mac-git-installation Github Guide to Installing Git} is
+quite a good source for information on Git.
+
+
+## Creating a Github Account and Forking Angular
+
+To create a Github account, follow the instructions {@link https://github.com/signup/free here}.
+Afterwards, go ahead and {@link http://help.github.com/forking fork} the {@link
+https://github.com/angular/angular.js main angular repository}.
+
+
+## Building `Angular`
+
+To build `angular`, you check out the source code and use Rake to generate the non-minified and
+minified `angular` files:
+
+1. To clone your Github repository, run:
+
+ git clone git@github.com:+ + + ++ + +# Downloading and hosting the files on your own + +This options is for those who want to work with angular offline, or want to host the angular files +on their own servers. + +If you navigate toMy Angular App + + + + + +
+
+Now let's take a closer look at that code, and see what is going on behind
+the scenes.
+
+The first line of interest defines the `ng` namespace, which makes
+`angular` work across all browsers (especially important for IE):
+
++ ++ +The next line downloads the `angular` script, and instructs `angular` to process +the entire HTML page when it is loaded: + +
+ ++ +(For details on what happens when `angular` processes an HTML page, +see {@link guide.bootstrap Bootstrap}.) + +Finally, this line in the `` of the page is the template that describes +how to display our greeting in the UI: + +
+ Hello {{'World'}}!
+
+
+Note the use of the double curly brace markup (`{{ }}`) to bind the expression to
+the greeting text. Here the expression is the string literal 'World'.
+
+Next let's look at a more interesting example, that uses `angular` to
+bind a dynamic expression to our greeting text.
+
+# Hello + Hello {{yourname}}! +
+
+These are some of the important points to note from this example:
+
+* The text input {@link angular.widget widget} called `yourname` is bound to a model variable called
+ `yourname`.
+* The double curly braces notation binds the variable `yourname` to the
+ greeting text.
+
+* You did not need to explicitly register an event listener or define an event
+ handler for events!
+
+Now try typing your name into the input box, and notice the immediate change to
+the displayed greeting. This demonstrates the concept of `angular`'s
+{@link guide.data-binding bi-directional data binding}. Any changes to the input field are immediately
+reflected in the model (one direction), and any changes to the model are
+reflected in the greeting text (the other direction).
+
+
+# Anatomy of an `angular` App
+
+This section describes the 3 parts of an `angular` app, and explains how they
+map to the Model-View-Controller design pattern:
+
+## Templates
+
+Templates, which you write in HTML and CSS, serve as the View. You add elements,
+attributes, and markup to HTML, which serve as instructions to the `angular`
+compiler. The `angular` compiler is fully extensible, meaning that with angular
+you can build your own declarative language on top of HTML!
+
+## Application Logic and Behavior
+
+Application Logic and Behavior, which you define in JavaScript, serve as the
+Controller. With `angular` (unlike with standard AJAX applications) you don't
+need to write additional listeners or DOM manipulators, because they are built-in.
+This feature makes your application logic very easy to write, test, maintain, and
+understand.
+
+## Scope
+
+The Model consists of one or more JavaScript objects, arrays, or primitive types.
+These are referenced from the scope. There are no restrictions on what the Model
+can be or what structure it should have. The only requirement is that it is
+referenced by the scope.
+
+The following illustration shows the parts of an `angular` application and how they
+work together:
+
+
+
+In addition, `angular` comes with a set of Services, which have the following
+properties:
+
+* The services provided are very useful for building web applications.
+* You can extend and add application-specific behavior to services.
+* Services include Dependency-Injection, XHR, caching, URL routing,
+ and browser abstraction.
+
+# Where To Go Next
+
+* For additional hands-on examples of using `angular`, including more source
+ code that you can copy and paste into your own pages, take a look through
+ the `angular` {@link cookbook Cookbook}.
+
+* For explanations of the `angular` concepts presented in the examples on this
+ page, see the {@link guide Developer Guide}.
diff --git a/docs/content/misc/testimonials.ngdoc b/docs/content/misc/testimonials.ngdoc
new file mode 100644
index 00000000..2e333f4b
--- /dev/null
+++ b/docs/content/misc/testimonials.ngdoc
@@ -0,0 +1,33 @@
+@ngdoc overview
+@name Testimonials
+@description
+
+
+## John Hardy
+> Also I want to pass on my compliments to Misko and Igor for this fantastic project. I'm currently
+> rewriting a server-side web application to use this system. I am constantly astounded at how much
+> simpler it is to do it this way and I still consider myself a learner.
+
+> This is without question the most productive approach to building webapps that I have seen.
+
+> The last time I had a coding epiphany was discovering the power and simplicity of JQuery. This is
+> way better than that.
+
+> I'm interested in promoting this library as widely as possible. I understand that you are still
+> developing it and I still have a long way to go before I really understand everything but I think
+> you really have something here.
+
+
+## Jerry Jeremiah
+> angular is the best thing I have used in a long time. I am having so much fun, even thought it is
+> probably obvious that dynamic web sites are new to me (my experience is more in the back end
+> embedded world...)
+
+
+## Dobrica Pavlinusic
+> Thanks to great help I received at this list, I was basically able to accomplish my goal to write
+> simple conference submission application within a week of first git clone of angular source from
+> github.
+
+> I think it might be useful to summarize my experience here, especially for people who are still
+> wondering if angular is worth a try. Executive summary is: **yes it is!**
\ No newline at end of file
--
cgit v1.2.3