sitewide: replace getpebble.com links with equivalent rebble.io ones

Also trim trailing newlines, since my editor likes to automatically do that.

Signed-off-by: Ruby Iris Juric <[email protected]>

Author: Sorixelle

README.md

@@ -1,4 +1,4 @@
-# [developer.pebble.com][site]
+# [developer.rebble.io][site]
 
 [![Build static site](https://github.com/pebble-dev/developer.rebble.io/actions/workflows/build.yml/badge.svg)](https://github.com/pebble-dev/developer.rebble.io/actions/workflows/build.yml)
 
@@ -176,9 +176,8 @@ the text color, use `--fg-<COLOR>`.
 
 Trouble building the developer site? Read the [Troubleshooting](/docs/troubleshooting.md) page for some possible solutions.
 
-[site]: https://developer.pebble.com
+[site]: https://developer.rebble.io
 [markdown]: ./docs/markdown.md
 [slick]: http://kenwheeler.github.io/slick/
 [tinypng]: https://tinypng.com/
 [tinyjpg]: https://tinyjpg.com/
-[travis]: https://magnum.travis-ci.com/pebble/developer.getpebble.com

_config.yml

@@ -12,8 +12,8 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-url: https://developer.pebble.com
-https_url: https://developer.pebble.com
+url: https://developer.rebble.io
+https_url: https://developer.rebble.io
 baseurl:
 asset_path: /assets
 external_server: https://developer-api.getpebble.com
@@ -51,15 +51,15 @@ sass:
 
 # Helpful and easily changeable external links.
 links:
-  pebble: https://www.pebble.com
+  pebble: https://rebble.io
   jobs: https://www.pebble.com/jobs/
   twitter: https://twitter.com/pebbledev/
   cloudpebble: https://cloudpebble.net/
   cloudpebble_beta: https://beta.cloudpebble.net/
   devportal: https://dev-portal.rebble.io/
   site_repo: https://github.com/pebble-dev/developer.rebble.io
   community_resources_repo: https://github.com/pebble/community-resources/
-  github: https://github.com/pebble/
+  github: https://github.com/pebble-dev/
   forums: https://forums.pebble.com
   forums_developer: https://forums.pebble.com/c/development
   pebblekit_android: https://github.com/pebble/pebble-android-sdk/
@@ -71,7 +71,7 @@ links:
     cookies: https://www.pebble.com/legal/cookies/
   s3_assets: https://developer-assets.getpebble.com
   pebble_tool_root: https://s3.amazonaws.com/assets.getpebble.com/pebble-tool/
-  libpebble: https://github.com/pebble/libpebble2
+  libpebble: https://github.com/pebble-dev/libpebble2
   kickstarter3: https://www.kickstarter.com/projects/597507018/pebble-2-time-2-and-core-an-entirely-new-3g-ultra
   discord_invite: http://discord.gg/aRUAYFN
 

docs/environment.md

@@ -8,7 +8,7 @@ This overrides the `url` configuration parameter of Jeyll. Set this to the root
 of where the site will be hosted.
 
 ```
-URL=http://developer.pebble.com
+URL=https://developer.rebble.io
 ```
 
 ## HTTPS_URL
@@ -17,7 +17,7 @@ This overrides the `https_url` configuration parameter of Jeyll. Set this to
 the secure root of where the site will be hosted.
 
 ```
-HTTPS_URL=https://developer.pebble.com
+HTTPS_URL=https://developer.rebble.io
 ```
 
 ## PORT

source/_changelogs/2.0-BETA4.md

@@ -22,7 +22,7 @@ date: 2013-12-23
  * Applications written for Pebble 1.x are not compatible with SDK 2.0
  * If a 2.0 version of an application exists, the Pebble mobile applications will automatically install it when when a user upgrades her/his Pebble.
 
-**You can start uploading your application to the Pebble appstore TODAY - [Please do so](http://dev-portal.getpebble.com/)!**
+**You can start uploading your application to the Pebble appstore TODAY - [Please do so]({{ site.links.devportal }})!**
 
 ## What has changed since BETA3
 
@@ -99,4 +99,3 @@ Overview:
 ### Examples
 
  - Added a License to the examples
-

source/_changelogs/2.0-BETA5.md

@@ -21,7 +21,7 @@ date: 2014-01-10
  * Applications written for Pebble 1.x are not compatible with SDK 2.0
  * If a 2.0 version of an application exists, the Pebble mobile applications will automatically install it when when a user upgrades her/his Pebble.
 
-**You can start uploading your application to the Pebble appstore TODAY - [Please do so](http://dev-portal.getpebble.com/)!**
+**You can start uploading your application to the Pebble appstore TODAY - [Please do so]({{ site.links.devportal }})!**
 
 ## What has changed since BETA4
 

source/_guides/appstore-publishing/appstore-assets.md

@@ -22,15 +22,15 @@ order: 3
 ---
 
 A number of graphical assets are required when publishing an app on the
-[Developer Portal](https://dev-portal.getpebble.com/), such as a marketing
+[Developer Portal]({{ site.links.devportal }}), such as a marketing
 banners. The resources on this page serve to help developers give these assets a
 more authentic feel.
 
 
 ## Example Marketing Banners
 
-Example 
-[marketing banners](https://s3.amazonaws.com/developer.getpebble.com/assets/other/banner-examples.zip) 
+Example
+[marketing banners](https://s3.amazonaws.com/developer.getpebble.com/assets/other/banner-examples.zip)
 from existing apps may help provide inspiration for an app's appstore banner
 design. Readable fonts, an appropriate background image, and at least one framed
 screenshot are all recommended.
@@ -40,16 +40,16 @@ screenshot are all recommended.
 
 ![](/images/guides/appstore-publishing/perspective-right.png =400x)
 
-Use these 
-[blank PSD templates](https://s3.amazonaws.com/developer.getpebble.com/assets/other/banner-templates-design.zip) 
+Use these
+[blank PSD templates](https://s3.amazonaws.com/developer.getpebble.com/assets/other/banner-templates-design.zip)
 to start a new app marketing banner in Photoshop from a template.
 
 
 ## App Screenshot Frames
 
 Use these
-[example screenshot frames](https://s3.amazonaws.com/developer.getpebble.com/assets/other/pebble-frames.zip) 
+[example screenshot frames](https://s3.amazonaws.com/developer.getpebble.com/assets/other/pebble-frames.zip)
 for Pebble, Pebble Steel, Pebble Time, Pebble Time Steel, and Pebble Time Round
-to decorate app screenshots in marketing banners and other assets. 
+to decorate app screenshots in marketing banners and other assets.
 
 > Note: The screenshots added to the listing itself must not be framed.

source/_guides/appstore-publishing/index.md

@@ -24,8 +24,8 @@ hide_comments: true
 ---
 
 When a developer is happy that their app is feature-complete and stable, they
-can upload the compiled `.pbw` file to the 
-[Developer Portal](https://dev-portal.getpebble.com) to make it available on the
+can upload the compiled `.pbw` file to the
+[Developer Portal]({{ site.links.devportal }}) to make it available on the
 Pebble appstore for all users with compatible watches to share and enjoy.
 
 In order to be successfully listed in the Pebble appstore the developer must:

source/_guides/appstore-publishing/preparing-a-submission.md

@@ -20,8 +20,8 @@ guide_group: appstore-publishing
 order: 0
 ---
 
-Once a new Pebble watchface or watchapp has been created, the 
-[Pebble Developer Portal](https://dev-portal.getpebble.com/) allows the
+Once a new Pebble watchface or watchapp has been created, the
+[Pebble Developer Portal]({{ site.links.devportal }}) allows the
 developer to publish their creation to the appstore either publicly, or
 privately. The appstore is built into the official mobile apps and means that
 every new app can be found and also featured for increased exposure and
@@ -33,7 +33,7 @@ publicity.
 
 To build the appstore listing for a new app, the following resources are
 required from the developer. Some may not be required, depending on the type of
-app being listed. Read 
+app being listed. Read
 {% guide_link appstore-publishing/publishing-an-app#listing-resources "Listing Resources" %}
 for a comparison.
 
@@ -89,16 +89,16 @@ also download the companion app automatically.
 ## Timeline
 
 Developers that require the user of the timeline API will need to click 'Enable
-timeline' to obtain API keys used for pushing pins. See the 
+timeline' to obtain API keys used for pushing pins. See the
 {% guide_link pebble-timeline %} guides for more information.
 
 
 ## Promotion
 
 Once published, the key to growth in an app is through promotion. Aside from
-users recommending the app to each other, posting on websites such as the 
-[Pebble Forums](https://forums.getpebble.com/categories/watchapp-directory), 
-[Reddit](https://www.reddit.com/r/pebble), and [Twitter](https://twitter.com) 
+users recommending the app to each other, posting on websites such as the
+[Pebble Forums](https://forums.getpebble.com/categories/watchapp-directory),
+[Reddit](https://www.reddit.com/r/pebble), and [Twitter](https://twitter.com)
 can help increase exposure.
 
 

source/_guides/appstore-publishing/publishing-an-app.md

@@ -21,13 +21,13 @@ order: 1
 ---
 
 When an app is ready for publishing, the `.pbw` file needs to be uploaded to the
-Pebble [Developer Portal](https://dev-portal.getpebble.com/), where a listing is
+Pebble [Developer Portal]({{ site.links.devportal }}), where a listing is
 created. Depending on the type of app, different sets of additional resources
 are required. These resources are then used to generate the listing pages
-visible to potential users in the Pebble appstore, which is embedded within the Pebble mobile app. 
+visible to potential users in the Pebble appstore, which is embedded within the Pebble mobile app.
 
-You can also view the [watchfaces](http://apps.getpebble.com/en_US/watchfaces) 
-and [watchapps](http://apps.getpebble.com/en_US/watchapps) from a desktop 
+You can also view the [watchfaces](http://apps.rebble.io/en_US/watchfaces)
+and [watchapps](http://apps.rebble.io/en_US/watchapps) from a desktop
 computer, as well as perform searches and get shareable links.
 
 

source/_guides/best-practices/conserving-battery-life.md

@@ -41,7 +41,7 @@ apps are discussed in this guide, alongside suggestions to help avoid them.
 
 ## Battery Ratings
 
-Any app published in the [Developer Portal](https://dev-portal.getpebble.com)
+Any app published in the [Developer Portal]({{ site.links.devportal }})
 will have a battery grade associated with it, once a minimum threshold of data
 has been collected. This can be used to get a rough idea of how much battery
 power the app consumes. For watchfaces and apps that will be launched for long
@@ -64,7 +64,7 @@ A common cause of such a drain are long-running animations that cause frequent
 display updates. For example, a watchface that plays a half-second ``Animation``
 for every second that ticks by will drain the battery faster than one that does
 so only once per minute. The latter approach will allow a lot more time for the
-watch to sleep. 
+watch to sleep.
 
 ```c
 static void tick_handler(struct tm *tick_time, TimeUnits changed) {
@@ -106,7 +106,7 @@ accel_tap_service_subscribe(tap_handler);
 Many watchfaces unecessarily tick once a second by using the ``SECOND_UNIT``
 constant value with the ``TickTimerService``, when they only update the display
 once a minute. By using the ``MINUTE_UNIT`` instead, the amount of times the
-watch is woken up per minute is reduced. 
+watch is woken up per minute is reduced.
 
 ```c
 // Only tick once a minute, much more time asleep
@@ -131,7 +131,7 @@ sensors will also prevent the watch from going to sleep and consume more battery
 power. The ``AccelerometerService`` API features the ability to configure the
 sampling rate and number of samples received per update, allowing batching of
 data into less frequent updates. By receiving updates less frequently, the
-battery will last longer. 
+battery will last longer.
 
 ```c
 // Batch samples into sets of 10 per callback
@@ -160,11 +160,11 @@ instead present a list of previous inputs if appropriate to reduce usage of this
 API.
 
 ```c
-static void dictation_session_callback(DictationSession *session, DictationSessionStatus status, 
+static void dictation_session_callback(DictationSession *session, DictationSessionStatus status,
                                        char *transcription, void *context) {
   if(status == DictationSessionStatusSuccess) {
     // Display the dictated text
-    snprintf(s_last_text, sizeof(s_last_text), "Transcription:\n\n%s", 
+    snprintf(s_last_text, sizeof(s_last_text), "Transcription:\n\n%s",
                                                                 transcription);
     text_layer_set_text(s_output_layer, s_last_text);
 
@@ -181,7 +181,7 @@ static void dictation_session_callback(DictationSession *session, DictationSessi
 Hinted at above, frequent use of the ``AppMessage`` API to send and recieve data
 will cause the Bluetooth connection to enter a more responsive state, which
 consumes much more power. A small time after a message is sent, the connection
-will return back to a low-power state. 
+will return back to a low-power state.
 
 The 'sniff interval' determines how often the API checks for new messages from
 the phone, and should be let in the default ``SNIFF_INTERVAL_NORMAL`` state as