Transition Docs (parse-community#424)

* Removes the links to parse.com

* Fixes broken links on new repo

* concat H1 section name with H2 to avoid link conflicts

Author: flovilmart

README.md

@@ -1,6 +1,6 @@
 # Parse Docs
 
-These are the markdown sources for all of the [Parse SDK guides](https://parseplatform.github.io/#sdks). The content for the guides is stored in this repo, and we use Jekyll to generate a static site that is hosted on GitHub Pages.
+These are the markdown sources for all of the [Parse SDK guides](https://parse-community.github.io/#sdks). The content for the guides is stored in this repo, and we use Jekyll to generate a static site that is hosted on GitHub Pages.
 
 ## Repository Structure
 

_config.yml

@@ -10,15 +10,20 @@ name: Parse Open Source Docs
 title: Parse Docs
 email: [email protected]
 description: The open source GitHub page for the Parse platform.
-baseurl: /docs # the subpath of your site, e.g. /blog
-url: "https://parseplatform.github.io/docs" # the base hostname & protocol for your site
-repository: parseplatform/docs
+url: "https://docs.parseplatform.org" # the base hostname & protocol for your site
+repository: parse-community/docs
 facebook_username: parseit
 twitter_username:  parseit
 github_username:   parseplatform
 stackoverflow_tag: parse.com
 serverfault_tag:   parse
 support_url: https://www.parse.com/help
+apis:
+  osx: https://parse-community.github.io/Parse-SDK-iOS-OSX/api
+  android: https://parse-community.github.io/Parse-SDK-Android/api
+  js: https://parse-community.github.io/Parse-SDK-JS/api
+  php: https://parse-community.github.io/parse-php-sdk/namespaces/Parse.html
+  dotnet: https://parse-community.github.io/Parse-SDK-dotNET/api
 
 # Build settings
 markdown: kramdown

_includes/android/getting-started.md

@@ -1,6 +1,6 @@
 # Getting Started
 
-Note that we support Android 2.3 and higher. You can also check out our [API Reference](/Parse-SDK-Android/api/) for more detailed information about our SDK.
+Note that we support Android 2.3 and higher. You can also check out our [API Reference]({{ site.apis.android }}) for more detailed information about our SDK.
 
 ## Installation
 **Step 1:** Download `Parse-SDK-Android`

_includes/android/handling-errors.md

@@ -2,4 +2,4 @@
 
 Many of the methods on `ParseObject`, including `save()`, `delete()`, and `get()` will throw a `ParseException` on an invalid request, such as deleting or editing an object that no longer exists in the cloud, or when there is a network failure preventing communication with the Parse Cloud. You will need to catch and deal with these exceptions.
 
-For more details, look at the [Android API](https://parse.com/docs/android/api/).
+For more details, look at the [Android API]({{ site.apis.android }}).

_includes/android/user-interface.md

@@ -4,7 +4,7 @@ At the end of the day, users of your application will be interacting with Androi
 
 ## ParseLoginUI
 
-If you are using Parse to manage users in your mobile app, you are already familiar with the `ParseUser`  class. At some point in your app, you might want to present a screen to log in your `ParseUser`.  Parse provides an open-source [ParseLoginUI](https://github.com/ParsePlatform/ParseUI-Android) library that does exactly this.  Please note ParseLoginUI is not included with the Parse Android SDK; you need to import this library from maven or from our Git repository into your project. Check the README.md of the [ParseLoginUI](https://github.com/ParsePlatform/ParseUI-Android) for detail steps.
+If you are using Parse to manage users in your mobile app, you are already familiar with the `ParseUser`  class. At some point in your app, you might want to present a screen to log in your `ParseUser`.  Parse provides an open-source [ParseLoginUI](https://github.com/parse-community/ParseUI-Android) library that does exactly this.  Please note ParseLoginUI is not included with the Parse Android SDK; you need to import this library from maven or from our Git repository into your project. Check the README.md of the [ParseLoginUI](https://github.com/parse-community/ParseUI-Android) for detail steps.
 
 This library contains an Android login activity that is ultra-customizable and easy to integrate with your app.  You can configure the look and feel of the login screens by either specifying XML configurations or constructing an Intent in code.  In this guide, we first provide several ways to integrate with the login library.  Then, we describe in detail how to customize the login screens.
 
@@ -42,7 +42,7 @@ When `ParseLoginActivity` finishes, your caller activity will receive either:
 *   `RESULT_OK`: The user successfully logged in. `ParseUser.getCurrentUser()` will be populated.
 *   `RESULT_CANCELLED`: The user pressed the back button. If the user fails to log in or sign up, the only way to return to the previous screen is by pressing the back button.
 
-We've provided a sample app, [ParseLoginSampleBasic](https://github.com/ParsePlatform/ParseUI-Android) for this use case.  This sample app is a simple profile viewer.  If you are not logged in, `SampleProfileActivity` prompts you to log in.  Clicking on the login button in `SampleProfileActivity` launches the `ParseLoginActivity`, which prompts the user for login credentials.  If the user successfully logs in, `ParseLoginActivity` will automatically finish itself and return `RESULT_OK`.  Then, `SampleProfileActivity` will display the user's name and a logout button.
+We've provided a sample app, [ParseLoginSampleBasic](https://github.com/parse-community/ParseUI-Android) for this use case.  This sample app is a simple profile viewer.  If you are not logged in, `SampleProfileActivity` prompts you to log in.  Clicking on the login button in `SampleProfileActivity` launches the `ParseLoginActivity`, which prompts the user for login credentials.  If the user successfully logs in, `ParseLoginActivity` will automatically finish itself and return `RESULT_OK`.  Then, `SampleProfileActivity` will display the user's name and a logout button.
 
 ![]({{ '/assets/images/basic_login.png' | prepend: site.baseurl }})
 
@@ -61,7 +61,7 @@ public class SampleDispatchActivity extends ParseLoginDispatchActivity {
 }
 ```
 
-We've provided another sample app, [ParseLoginSampleWithDispatchActivity](https://github.com/ParsePlatform/ParseUI-Android) for this use case.  The `SampleProfileActivity` in this app cannot function without a logged-in user, so it is protected by `SampleDispatchActivity`.
+We've provided another sample app, [ParseLoginSampleWithDispatchActivity](https://github.com/parse-community/ParseUI-Android) for this use case.  The `SampleProfileActivity` in this app cannot function without a logged-in user, so it is protected by `SampleDispatchActivity`.
 
 ![]({{ '/assets/images/login_with_dispatch.png' | prepend: site.baseurl }})
 
@@ -147,7 +147,7 @@ For the Facebook permission array, you also need to have this in your `res/value
 
 ### Configure by Code
 
-You can configure the `ParseLoginActivity` by code using the ParseLoginBuilder.  You specify the options on the builder, and then call `build()` to generate an `Intent` that can be used to start the `ParseLoginActivity`.  We've provided a sample app, [ParseLoginSampleCodeCustomization](https://github.com/ParsePlatform/ParseUI-Android) demonstrating this use case.  The options in `ParseLoginBuilder` are the same as those in activity metadata customization.  If you specify options in both code and activity metadata, the options in code take precedence.
+You can configure the `ParseLoginActivity` by code using the ParseLoginBuilder.  You specify the options on the builder, and then call `build()` to generate an `Intent` that can be used to start the `ParseLoginActivity`.  We've provided a sample app, [ParseLoginSampleCodeCustomization](https://github.com/parse-community/ParseUI-Android) demonstrating this use case.  The options in `ParseLoginBuilder` are the same as those in activity metadata customization.  If you specify options in both code and activity metadata, the options in code take precedence.
 
 ```java
 ParseLoginBuilder builder = new ParseLoginBuilder(ProfileActivity.this);
@@ -176,7 +176,7 @@ You can override any layout resources by having files with the same name as thos
 *   `com_parse_ui_parse_signup_fragment.xml`: You can add additional input fields in the signup form here.  If you do, you also need add code to `ParseSignupFragment` to copy that data into the `ParseUser` object.
 *   `com_parse_ui_parse_login_help_fragment.xml`: You can change the message for password reset.
 
-We've provided another sample app, [ParseLoginSampleLayoutOverride](https://github.com/ParsePlatform/ParseUI-Android) showing how to do this.  This sample app only has a Facebook login button in `com_parse_ui_parse_login_fragment.xml`, and adds a background image to the login screens.
+We've provided another sample app, [ParseLoginSampleLayoutOverride](https://github.com/parse-community/ParseUI-Android) showing how to do this.  This sample app only has a Facebook login button in `com_parse_ui_parse_login_fragment.xml`, and adds a background image to the login screens.
 
 ## ParseQueryAdapter
 

_includes/arduino/getting-started.md

@@ -1,10 +1,10 @@
 # Getting Started
 
-If you haven't installed the SDK yet, please [head over to the QuickStart guide](https://parse.com{{ page.quickstart }}#embedded/arduino) to install the SDK in the Arduino IDE. Note that this SDK requires the Arduino Yún and the Arduino IDE v1.6.0+.
+If you haven't installed the SDK yet, please [head over to the QuickStart guide]({ page.quickstart }}#embedded/arduino) to install the SDK in the Arduino IDE. Note that this SDK requires the Arduino Yún and the Arduino IDE v1.6.0+.
 
 The Parse platform provides a complete backend solution for your hardware device. Our goal is to totally eliminate the need for writing server code or maintaining servers.
 
-Note that the Arduino SDK only contains a subset of Parse features found in mobile and desktop. This allows the SDK to be smaller in size and more performant, making it suitable for constrained embedded environments. The Arduino SDK is fully open source, and anyone can contribute to make it better, or make their own changes if necessary. Check out the[ GitHub repository](https://github.com/ParsePlatform/parse-embedded-sdks) for more information.
+Note that the Arduino SDK only contains a subset of Parse features found in mobile and desktop. This allows the SDK to be smaller in size and more performant, making it suitable for constrained embedded environments. The Arduino SDK is fully open source, and anyone can contribute to make it better, or make their own changes if necessary. Check out the[ GitHub repository](https://github.com/parse-community/parse-embedded-sdks) for more information.
 
 ## Initialization
 

_includes/arduino/sample-app.md

@@ -1,3 +1,3 @@
 # Sample App
 
-We prepared a [sample app](https://github.com/ParsePlatform/Anydevice) that demonstrates how to provision connected devices using a companion phone app such that connected devices can securely access user-specific data on the Parse Cloud. This sample app also demonstrates how to send push notifications between the phone app and connected devices.
+We prepared a [sample app](https://github.com/parse-community/Anydevice) that demonstrates how to provision connected devices using a companion phone app such that connected devices can securely access user-specific data on the Parse Cloud. This sample app also demonstrates how to send push notifications between the phone app and connected devices.

_includes/cloudcode/cloud-code-advanced.md

@@ -146,4 +146,4 @@ The response object passed into the `success` and `error` will contain:
 * **`buffer`** - The raw byte representation of the response body.
 * **`text`** - The raw response body.
 * **`data`** - The parsed response, if Cloud Code knows how to parse the content-type that was sent.
-* **`cookies`** - The cookies sent by the server. They are [Parse.Cloud.Cookie](https://parse.com/docs/js/api/classes/Parse.Cloud.HTTPResponse.html) objects.
+* **`cookies`** - The cookies sent by the server. They are [Parse.Cloud.Cookie]({{ site.apis.js }}/classes/Parse.Cloud.HTTPResponse.html) objects.

_includes/cloudcode/cloud-code.md

@@ -210,7 +210,7 @@ If `response.error` is called, the `Review` object will not be saved, and the cl
 
 One useful tip is that even if your mobile app has many different versions, the same version of Cloud Code applies to all of them. Thus, if you launch an application that doesn't correctly check the validity of input data, you can still fix this problem by adding a validation with `beforeSave`.
 
-If you want to use `beforeSave` for a predefined class in the Parse JavaScript SDK (e.g. [Parse.User](https://parse.com/docs/js/api/symbols/Parse.User.html)), you should not pass a String for the first argument. Instead, you should pass the class itself:
+If you want to use `beforeSave` for a predefined class in the Parse JavaScript SDK (e.g. [Parse.User]({{ site.apis.js }}/symbols/Parse.User.html)), you should not pass a String for the first argument. Instead, you should pass the class itself:
 
 ```javascript
 Parse.Cloud.beforeSave(Parse.User, function(request, response) {
@@ -260,11 +260,11 @@ Parse.Cloud.afterSave("Comment", function(request) {
 
 The client will receive a successful response to the save request after the handler terminates, regardless of how it terminates. For instance, the client will receive a successful response even if the handler throws an exception. Any errors that occurred while running the handler can be found in the Cloud Code log.
 
-If you want to use `afterSave` for a predefined class in the Parse JavaScript SDK (e.g. [Parse.User](https://parse.com/docs/js/api/symbols/Parse.User.html)), you should not pass a String for the first argument. Instead, you should pass the class itself.
+If you want to use `afterSave` for a predefined class in the Parse JavaScript SDK (e.g. [Parse.User]({{ site.apis.js }}/symbols/Parse.User.html)), you should not pass a String for the first argument. Instead, you should pass the class itself.
 
 # beforeDelete Triggers
 
-You can run custom Cloud Code before an object is deleted. You can do this with the `beforeDelete` method. For instance, this can be used to implement a restricted delete policy that is more sophisticated than what can be expressed through  [ACLs](https://parse.com/docs/js/api/symbols/Parse.ACL.html). For example, suppose you have a photo album app, where many photos are associated with each album, and you want to prevent the user from deleting an album if it still has a photo in it. You can do that by writing a function like this:
+You can run custom Cloud Code before an object is deleted. You can do this with the `beforeDelete` method. For instance, this can be used to implement a restricted delete policy that is more sophisticated than what can be expressed through  [ACLs]({{ site.apis.js }}/symbols/Parse.ACL.html). For example, suppose you have a photo album app, where many photos are associated with each album, and you want to prevent the user from deleting an album if it still has a photo in it. You can do that by writing a function like this:
 
 ```javascript
 Parse.Cloud.beforeDelete("Album", function(request, response) {
@@ -287,7 +287,7 @@ Parse.Cloud.beforeDelete("Album", function(request, response) {
 
 If `response.error` is called, the `Album` object will not be deleted, and the client will get an error. If `response.success` is called, the object will be deleted normally. Your code should call one of these two callbacks.
 
-If you want to use `beforeDelete` for a predefined class in the Parse JavaScript SDK (e.g. [Parse.User](https://parse.com/docs/js/api/symbols/Parse.User.html)), you should not pass a String for the first argument. Instead, you should pass the class itself.
+If you want to use `beforeDelete` for a predefined class in the Parse JavaScript SDK (e.g. [Parse.User]({{ site.apis.js }}/symbols/Parse.User.html)), you should not pass a String for the first argument. Instead, you should pass the class itself.
 
 
 # afterDelete Triggers
@@ -318,7 +318,7 @@ The `afterDelete` handler can access the object that was deleted through `reques
 
 The client will receive a successful response to the delete request after the handler terminates, regardless of how it terminates. For instance, the client will receive a successful response even if the handler throws an exception. Any errors that occurred while running the handler can be found in the Cloud Code log.
 
-If you want to use `afterDelete` for a predefined class in the Parse JavaScript SDK (e.g. [Parse.User](https://parse.com/docs/js/api/symbols/Parse.User.html)), you should not pass a String for the first argument. Instead, you should pass the class itself.
+If you want to use `afterDelete` for a predefined class in the Parse JavaScript SDK (e.g. [Parse.User]({{ site.apis.js }}/symbols/Parse.User.html)), you should not pass a String for the first argument. Instead, you should pass the class itself.
 
 # beforeFind Triggers
 

_includes/common/security.md

@@ -474,13 +474,13 @@ There are some special classes in Parse that don't follow all of the same securi
 
 ## Data Integrity in Cloud Code
 
-For most apps, care around keys, class-level permissions, and object-level ACLs are all you need to keep your app and your users' data safe. Sometimes, though, you'll run into an edge case where they aren't quite enough. For everything else, there's [Cloud Code](https://parse.com/docs/cloudcode/guide#cloud-code).
+For most apps, care around keys, class-level permissions, and object-level ACLs are all you need to keep your app and your users' data safe. Sometimes, though, you'll run into an edge case where they aren't quite enough. For everything else, there's [Cloud Code](/docs/cloudcode/guide#cloud-code).
 
 Cloud Code allows you to upload JavaScript to Parse's servers, where we will run it for you. Unlike client code running on users' devices that may have been tampered with, Cloud Code is guaranteed to be the code that you've written, so it can be trusted with more responsibility.
 
 One particularly common use case for Cloud Code is preventing invalid data from being stored. For this sort of situation, it's particularly important that a malicious client not be able to bypass the validation logic.
 
-To create validation functions, Cloud Code allows you to implement a `beforeSave` trigger for your class. These triggers are run whenever an object is saved, and allow you to modify the object or completely reject a save. For example, this is how you create a [Cloud Code beforeSave trigger](https://parse.com/docs/cloudcode/guide#cloud-code-beforesave-triggers) to make sure every user has an email address set:
+To create validation functions, Cloud Code allows you to implement a `beforeSave` trigger for your class. These triggers are run whenever an object is saved, and allow you to modify the object or completely reject a save. For example, this is how you create a [Cloud Code beforeSave trigger](/docs/cloudcode/guide#cloud-code-beforesave-triggers) to make sure every user has an email address set:
 
 ```js
 Parse.Cloud.beforeSave(Parse.User, function(request, response) {
@@ -493,7 +493,7 @@ Parse.Cloud.beforeSave(Parse.User, function(request, response) {
 });
 ```
 
-Our [Cloud Code guide](https://parse.com/docs/cloudcode/guide#cloud-code) provides instructions on how to upload this trigger to our servers.
+Our [Cloud Code guide](/docs/cloudcode/guide#cloud-code) provides instructions on how to upload this trigger to our servers.
 
 Validations can lock down your app so that only certain values are acceptable. You can also use `afterSave` validations to normalize your data (e.g. formatting all phone numbers or currency identically). You get to retain most of the productivity benefits of accessing Parse data directly from your client applications, but you can also enforce certain invariants for your data on the fly.