Update developer portal documentation

Author: Willow-Systems

_config.yml

@@ -73,7 +73,8 @@ links:
   pebble_tool_root: https://s3.amazonaws.com/assets.getpebble.com/pebble-tool/
   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
+  discord_invite: https://rebble.io/discord
+  rebble_tos: https://rebble.io/tos/
 
 # Jekyll collections.
 collections:

source/_guides/appstore-publishing/index.md

@@ -15,7 +15,7 @@
 
 title: Appstore Publishing
 description: |
-  How to get your app ready for going live in the Pebble appstore.
+  How to get your app ready for going live in the Rebble appstore.
 guide_group: appstore-publishing
 menu: false
 permalink: /guides/appstore-publishing/
@@ -26,9 +26,9 @@ 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]({{ site.links.devportal }}) to make it available on the
-Pebble appstore for all users with compatible watches to share and enjoy.
+Rebble appstore for all users with compatible watches to share and enjoy.
 
-In order to be successfully listed in the Pebble appstore the developer must:
+In order to be successfully listed in the Rebble appstore the developer must:
 
 * Provide all required assets and marketing material.
 
@@ -38,11 +38,10 @@ In order to be successfully listed in the Pebble appstore the developer must:
 
 * Build their app with a non-beta SDK.
 
-* Ensure their app complies with the various legal agreements.
+* Ensure their app complies with the various [legal agreements]({{ site.links.rebble_tos }}).
 
 Information on how to meet these requirements is given in this group of guides,
-as well as details about available analytical data for published apps and
-example asset material templates.
+as well as details about example asset material templates.
 
 
 ## Contents

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

@@ -27,9 +27,9 @@ 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
 publicity.
 
-> Note: An app can only be published privately while it is not already published
-> publicly. If an app is already public, it must be unpublished before it can be
-> made private.
+# > Note: An app can only be published privately while it is not already published
+# > publicly. If an app is already public, it must be unpublished before it can be
+# > made private.
 
 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
@@ -80,6 +80,8 @@ releases.
 
 ## Companion Apps
 
+> This functionality is coming to the Rebble Developer Portal in a future release.
+
 If your app requires an Android or iOS companion app to function, it can be
 listed here by providing the name, icon, and URL that users can use to obtain
 the companion app. When a user install the watchapp, they will be prompted to
@@ -96,9 +98,7 @@ timeline' to obtain API keys used for pushing pins. See the
 ## 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 [Reddit](https://www.reddit.com/r/pebble) or the [Rebble Discord Server]({{ site.links.discord_invite }})
 can help increase exposure.
 
 

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

@@ -21,7 +21,7 @@ order: 1
 ---
 
 When an app is ready for publishing, the `.pbw` file needs to be uploaded to the
-Pebble [Developer Portal]({{ site.links.devportal }}), where a listing is
+Rebble [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.
@@ -50,103 +50,69 @@ resources are before creating the listing.
 
 ## Publishing a Watchface
 
-1. After logging in, click 'Add a Watchface'.
+1. After logging in to the Developer Portal, click '+ New App'. Press 'Next'.
 
-2. Enter the basic details of the watchface, such as the title, source code URL,
-   and support email (if different from the one associated with this developer
-   account):
+2. Enter the basic details of the Watchface, such as the title, type,
+   and a description:
 
     ![face-title](/images/guides/appstore-publishing/face-title.png)
 
-3. Click 'Create' to be taken to the listing page. This page details the status
-   of the listing, including links to subpages, a preview of the public page,
-   and any missing information preventing release.
+3. Click 'Next' to be taken to the images page. Here you should upload screenshots for each platform your Watchface supports.
+    ![add-images](/images/guides/appstore-publishing/new-add-image.png)
 
-    ![face-listing](/images/guides/appstore-publishing/face-listing.png)
+   Further down the page is the option to upload a banner. During inital submission, you can provide one banner. After
+   your app is submitted, you will be able to provide up to 3 banners per platform if desired. Press 'Next'.
 
-4. The status now says 'Missing: At least one published release'. Click 'Add a
-   release' to upload the `.pbw`, optionally adding release notes:
+4. The next step is to optionally provide a website link and a source code link. Both fields can be left blank if desired.
 
-    ![face-release](/images/guides/appstore-publishing/face-release.png)
+    ![add-source](/images/guides/appstore-publishing/new-add-source.png)
 
-5. Click 'Save'. After reloading the page, make the release public by clicking
-   'Publish' next to the release:
+5. Click 'Next'. The final page requires you to provide release notes for your first release, as well as the .pbw file.
 
-    ![face-release-publish](/images/guides/appstore-publishing/face-release-publish.png)
+    ![face-release-publish](/images/guides/appstore-publishing/new-add-release.png)
 
-6. The status now says 'Missing: A complete X asset collection' for
-   each X supported platform. Click 'Manage Asset Collections', then click
-   'Create' for a supported platform.
-
-7. Add a description, up to 5 screenshots, and optionally a marketing banner
-   before clicking 'Create Asset Collection'.
-
-    ![face-assets](/images/guides/appstore-publishing/face-assets.png)
-
-8. Once all asset collections required have been created, click 'Publish' or
-   'Publish Privately' to make the app available only to those viewing it
-   through the direct link. Note that once made public, an app cannot then be
-   made private.
-
-9. After publishing, reload the page to get the public appstore link for social
-   sharing, as well as a deep link that can be used to directly open the
-   appstore in the mobile app.
+   Once you have submitted this information, and you are happy with the submission, press 'Publish App to Store' to submit your app!
 
 
 ## Publishing a Watchapp
 
-1. After logging in, click 'Add a Watchapp'.
+1. After logging in to the Developer Portal, click '+ New App'. Press 'Next'.
 
-2. Enter the basic details of the watchapp, such as the title, source code URL,
-   and support email (if different from the one associated with this developer
-   account):
+2. Enter the basic details of the App, such as the title, type, category and a description:
 
-    ![app-title](/images/guides/appstore-publishing/app-title.png)
+    ![face-title](/images/guides/appstore-publishing/new-add-watchapp.png)
 
-3. Select the most appropriate category for the app, depending on the features
-   it provides:
-
-    ![app-category](/images/guides/appstore-publishing/app-category.png)
-
-4. Upload the large and small icons representing the app:
-
-    ![app-icons](/images/guides/appstore-publishing/app-icons.png)
+3. Click 'Next' to be taken to the images page. Here you should upload screenshots for each platform your App supports.
+    ![add-images](/images/guides/appstore-publishing/new-add-image.png)
 
-5. Click 'Create' to be taken to the listing page. This page details the status
-   of the listing, including links to subpages, a preview of the public page,
-   and any missing information preventing release.
+   Further down the page is the section to upload a banner. During inital submission, you can provide one banner. After
+   your app is submitted, you will be able to provide up to 3 banners per platform if desired.
 
-    ![app-listing](/images/guides/appstore-publishing/app-listing.png)
+   You must also provide a large icon and small icon for your Watch App.
 
-6. The status now says 'Missing: At least one published release'. Click 'Add a
-   release' to upload the `.pbw`, optionally adding release notes:
+   ![add-banners](/images/guides/appstore-publishing/new-add-banner.png)
 
-    ![app-release](/images/guides/appstore-publishing/app-release.png)
+4. The next step is to optionally provide a website link and a source code link. Both fields can be left blank if desired.
 
-7. Click 'Save'. After reloading the page, make the release public by clicking
-   'Publish' next to the release:
+    ![face-release](/images/guides/appstore-publishing/new-add-source.png)
 
-    ![face-release-publish](/images/guides/appstore-publishing/face-release-publish.png)
+5. Click 'Next'. The final page requires you to provide release notes for your first release, as well as the .pbw file.
 
-8. The status now says 'Missing: A complete X asset collection' for
-   each X supported platform. Click 'Manage Asset Collections', then click
-   'Create' for a supported platform.
+    ![face-release-publish](/images/guides/appstore-publishing/new-add-release.png)
 
-9. Add a description, up to 5 screenshots, optionally up to three header images,
-   and a marketing banner before clicking 'Create Asset Collection'.
+   Once you have submitted this information, and you are happy with the submission, press 'Publish App to Store' to submit your app!
 
-    ![app-assets](/images/guides/appstore-publishing/app-assets.png)
 
-10. Once all asset collections required have been created, click 'Publish' or
-    'Publish Privately' to make the app available only to those viewing it
-    through the direct link.
-
-11. After publishing, reload the page to get the public appstore link for social
-    sharing, as well as a deep link that can be used to directly open the
-    appstore in the mobile app.
+## Publishing a Companion App
 
+<div class="alert alert--fg-white alert--bg-orange">
+{% markdown %}
+**Legacy Section**
 
-## Publishing a Companion App
+The Rebble Developer Portal does not yet support companion apps. The legacy Pebble documentation is currently preserved here for reference.
+If you wish to publish or update a companion app, please get in touch via [Discord]({{ site.links.discord_invite }}).
+{% endmarkdown %}
+</div>
 
 > A companion app is one that is written for Pebble, but exists on the Google
 > Play store, or the Appstore. Adding it to the Pebble appstore allows users to