Rename Developer Portal to Developer Dashboard throughout documentation

ericmigi · claude · ericmigi · commit a35d3d936dc7 · 2025-11-24T10:43:40.000-08:00
Updated all references from "Developer Portal" to "Developer Dashboard" across guides, blog posts, and community documentation to reflect the new terminology. This includes: - 8 guide files in appstore-publishing, best-practices, events-and-services, and pebble-timeline - 12 blog posts from 2013-2015 - 3 other files including more/index.html and event documentation All occurrences were updated while preserving case sensitivity (Developer Dashboard for capitalized, developer dashboard for lowercase). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
diff --git a/source/_guides/appstore-publishing/appstore-assets.md b/source/_guides/appstore-publishing/appstore-assets.md
@@ -22,7 +22,7 @@ order: 3
 ---
 
 A number of graphical assets are required when publishing an app on the
-[Developer Portal]({{ site.links.devportal }}), such as a marketing
+[Developer Dashboard]({{ site.links.devportal }}), such as a marketing
 banners. The resources on this page serve to help developers give these assets a
 more authentic feel.
 
diff --git a/source/_guides/appstore-publishing/index.md b/source/_guides/appstore-publishing/index.md
@@ -25,7 +25,7 @@ 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
+[Developer Dashboard]({{ 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:
diff --git a/source/_guides/appstore-publishing/preparing-a-submission.md b/source/_guides/appstore-publishing/preparing-a-submission.md
@@ -21,7 +21,7 @@ order: 0
 ---
 
 Once a new Pebble watchface or watchapp has been created, the
-[Pebble Developer Portal]({{ site.links.devportal }}) allows the
+[Pebble Developer Dashboard]({{ 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
diff --git a/source/_guides/appstore-publishing/publishing-an-app.md b/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
+Pebble [Developer Dashboard]({{ 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.
diff --git a/source/_guides/best-practices/conserving-battery-life.md b/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]({{ site.links.devportal }})
+Any app published in the [Developer Dashboard]({{ 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
diff --git a/source/_guides/events-and-services/health.md b/source/_guides/events-and-services/health.md
@@ -47,7 +47,7 @@ apps, and API calls will return values to reflect this.
 
 In addition, any app using the ``HealthService`` API must declare the 'health'
 capability in order to be accepted by the
-[developer portal]({{ site.links.devportal }}). This can be done in `package.json`
+[developer dashboard]({{ site.links.devportal }}). This can be done in `package.json`
 in the SDK:
 
 ```js
diff --git a/source/_guides/pebble-timeline/index.md b/source/_guides/pebble-timeline/index.md
@@ -51,13 +51,13 @@ and notifications from any web-based external service.
 ## Enabling a New App
 
 To push pins via the Pebble timeline API, a first version of a new app must be
-uploaded to the [Developer Portal]({{ site.links.devportal }}). This is
+uploaded to the [Developer Dashboard]({{ site.links.devportal }}). This is
 required so that the appstore can identify the app's UUID, and so generate
 sandbox and production API keys for the developer to push pins to. It is then
 possible to use the timeline web API in sandbox mode for development or in
 production mode for published apps.
 
-1. In the Developer Portal, go to the watchapp's details page in the 'Dashboard'
+1. In the Developer Dashboard, go to the watchapp's details page in the 'Dashboard'
    view and click the 'Enable timeline' button.
 
 2. To obtain API keys, click the 'Manage Timeline Settings' button at the
@@ -74,7 +74,7 @@ The production mode is used when a user installs the app from the Pebble
 appstore. Use the two respective API key types for these purposes. If
 whitelisting is enabled in sandbox mode, the developer's account is
 automatically included, and they can add more Pebble users by adding the users'
-email addresses in the [Developer Portal]({{ site.links.devportal }}).
+email addresses in the [Developer Dashboard]({{ site.links.devportal }}).
 
 If preferred, it is possible to enable whitelisting to limit this access to only
 users involved in development and testing of the app. Enter the email addresses
diff --git a/source/_guides/pebble-timeline/timeline-public.md b/source/_guides/pebble-timeline/timeline-public.md
@@ -178,7 +178,7 @@ OK
 It is possible to send a pin (and updates) to multiple users at once by
 modifying the `PUT` header to include `X-Pin-Topics` (the topics a user must be
 subscribed to in order to receive this pin) and `X-API-Key` (issued by the
-[Developer Portal]({{ site.links.devportal }})). In this case, the URL is
+[Developer Dashboard]({{ site.links.devportal }})). In this case, the URL is
 also modified:
 
 ```text
diff --git a/source/_posts/2013-12-18-All-Aboard-the-Pebble-app-store.md b/source/_posts/2013-12-18-All-Aboard-the-Pebble-app-store.md
@@ -24,16 +24,16 @@ If your Pebble app requires a companion iOS or Android app, you can also include
 Submitting an application on the Pebble appstore is free and open to everyone. To get started:
 
  1. Read the [*Appstore Publishing*](/guides/appstore-publishing) guides.
- 1. Join the [developer portal](http://dev-portal.getpebble.com/).
+ 1. Join the [developer dashboard](http://dev-portal.getpebble.com/).
 
-![An application on the Pebble Developer Portal](/images/blog/pebble_appstore_webportal.png)
+![An application on the Pebble Developer Dashboard](/images/blog/pebble_appstore_webportal.png)
 
 More information and answers to common questions after the break!
 
 
-### What is the developer portal?
+### What is the developer dashboard?
 
-The developer portal is the web application that developers use to publish an iOS or an Android application to the Pebble appstore. The URL for the developer portal is [https://dev-portal.getpebble.com](https://dev-portal.getpebble.com). Access to the developer portal is free.
+The developer dashboard is the web application that developers use to publish an iOS or an Android application to the Pebble appstore. The URL for the developer dashboard is [https://dev-portal.getpebble.com](https://dev-portal.getpebble.com). Access to the developer dashboard is free.
 
 ### Will you validate / approve applications?
 
diff --git a/source/_posts/2014-01-06-Pebble-appstore.md b/source/_posts/2014-01-06-Pebble-appstore.md
@@ -20,7 +20,7 @@ Appstore launches do not happen often and we all know this is a big opportunity;
 
 ## Submitting an application to the Pebble appstore
 
-Submitting an application is a free and very easy process that only takes a few minutes. Just head to our [developer portal](https://dev-portal.getpebble.com) and upload your application and a few images.
+Submitting an application is a free and very easy process that only takes a few minutes. Just head to our [developer dashboard](https://dev-portal.getpebble.com) and upload your application and a few images.
 
 We have prepared some resources to help you:
 
diff --git a/source/_posts/2014-01-17-Pebble-SDK-BETA6.md b/source/_posts/2014-01-17-Pebble-SDK-BETA6.md
@@ -57,13 +57,13 @@ Have you already submitted your app? Or are you about to submit? Here is a quick
 
  * Is your application in the 'Published' state? Publishing a release is not enough. You need to click the 'Publish' button in the top right corner to make sure your app is visible. Please double-check this!
 
- * If you had a 1.x version of your app, did you provide the name and UUID of your 1.x app in the developer portal? This will allow us to automatically migrate your users to the 2.0 version.
+ * If you had a 1.x version of your app, did you provide the name and UUID of your 1.x app in the developer dashboard? This will allow us to automatically migrate your users to the 2.0 version.
 
  * Did you upload a header image for your app (not required for watchfaces)? If not, we provide the [Pebble appstore marketing materials](/guides/appstore-publishing/appstore-assets/) to help you.
 
 ## Deep links to Pebble applications
 
-You can link directly to a Pebble app or watchface in the Pebble appstore. Simply grab your Pebble application identifier in the URL of the developer portal and append it to: `pebble://appstore/`.
+You can link directly to a Pebble app or watchface in the Pebble appstore. Simply grab your Pebble application identifier in the URL of the developer dashboard and append it to: `pebble://appstore/`.
 
 For example, if your application in the portal has the URL `https://dev-portal.getpebble.com/applications/52d396683e2e256b6c00001e`, then a deep-link for your app is `pebble://appstore/52d396683e2e256b6c00001e`.
 
diff --git a/source/_posts/2014-01-23-Pebble-SDK-BETA7.md b/source/_posts/2014-01-23-Pebble-SDK-BETA7.md
@@ -31,7 +31,7 @@ Have you already submitted your app? Or are you about to submit? Here is a quick
 
  * Is your application in the 'Published' state? Publishing a release is not enough. You need to click the 'Publish' button in the top right corner to make sure your app is visible. Please double-check this!
 
- * If you had a 1.x version of your app, and did you provide the name and UUID of your 1.x app in the developer portal? This will allow us to automatically migrate your users to the 2.0 version of your app.
+ * If you had a 1.x version of your app, and did you provide the name and UUID of your 1.x app in the developer dashboard? This will allow us to automatically migrate your users to the 2.0 version of your app.
 
  * Did you upload a header image for your app (not required for watchfaces)? If not, we provide the [Pebble appstore marketing materials](/guides/appstore-publishing/appstore-assets/) to help you.
 
diff --git a/source/_posts/2014-01-31-Appstore-Tips.md b/source/_posts/2014-01-31-Appstore-Tips.md
@@ -9,7 +9,7 @@ If you have already published an app, or are planning on publishing an app,
 here are some tips for a successful appstore launch.
 
 
- * If your Pebble app requires an iOS or Android companion app, make sure that you have entered the Apple App Store/Google Play URL correctly for your app. Double-check that your links work by clicking on the companion app name in the developer portal or clicking the link in the mobile appstore.
+ * If your Pebble app requires an iOS or Android companion app, make sure that you have entered the Apple App Store/Google Play URL correctly for your app. Double-check that your links work by clicking on the companion app name in the developer dashboard or clicking the link in the mobile appstore.
 	 ![](/images/blog/iOS_companion.png)
 	 ![](/images/blog/android_companion.png)
 
@@ -21,7 +21,7 @@ here are some tips for a successful appstore launch.
   * If your Pebble app existed on the 1.x SDK, we recommend that you verify that your app is upgraded properly during the 1.x -> 2.0 onboarding procedure. To test, install your 1.x mobile app and place your Pebble in recovery mode so that you are running a 1.x firmware. Once you've paired your Pebble with your phone (accepting the update to 1.14.1 firmware is ok), make sure your 1.x Pebble app is installed on your Pebble. Update your mobile app to BETA7 and pair it with your Pebble. You will be prompted to complete onboarding for 2.0, and then you can verify that your app was automatically upgraded to its 2.0 version.
 	
 	
-  * Screenshots uploaded to the developer portal should be restricted to screenshots taken from your watchface/watchapp. Color photos and drawings are not permitted. We will attempt to contact you this weekend to fix your screenshot images if they have been flagged, but we reserve the right to unpublish your app if it is found to be in violation on Monday. Creating a screenshot is easy!
+  * Screenshots uploaded to the developer dashboard should be restricted to screenshots taken from your watchface/watchapp. Color photos and drawings are not permitted. We will attempt to contact you this weekend to fix your screenshot images if they have been flagged, but we reserve the right to unpublish your app if it is found to be in violation on Monday. Creating a screenshot is easy!
 
 	* In CloudPebble, on the compilation screen, select "Run Build", enter your Phone IP into the text field and click "Screenshot". 
 		![](/images/blog/cloudpebble_screentool.png)
diff --git a/source/_posts/2014-02-03-Pebble-appstore-is-live.md b/source/_posts/2014-02-03-Pebble-appstore-is-live.md
@@ -23,7 +23,7 @@ Here are some answers to the most pressing questions:
 
  * Can I see how many people have downloaded my application?
 
-   Not yet, but we are collecting analytics and we'll make them available in the [developer portal](http://dev-portal.getpebble.com) very soon.
+   Not yet, but we are collecting analytics and we'll make them available in the [developer dashboard](http://dev-portal.getpebble.com) very soon.
 
  * When is the next update of JavaScript apps coming?
 
diff --git a/source/_posts/2014-04-22-JS-Bundling.md b/source/_posts/2014-04-22-JS-Bundling.md
@@ -15,7 +15,7 @@ tags:
 
 We get a lot of questions about apps that use JavaScript and their availability
 in the store. We are improving the Pebble appstore documentation and the
-Developer Portal to address these questions, but until those changes are live,
+Developer Dashboard to address these questions, but until those changes are live,
 we thought we would summarize the key points in a blog post.
 
 
@@ -84,7 +84,7 @@ developers publishing JavaScript applications:
 to announce when we are going to grab JavaScript from the appstore to submit a 
 new build to Apple, and then when this version is available to iOS users;
 * We are updating the appstore documentation to explain how the process works;
-* We will be showing you in the developer portal what the current status of your
+* We will be showing you in the developer dashboard what the current status of your
   app is and in what version of the iOS application it is or will be in.
 
 We are continuously looking to improve the tools and services we provide to the
diff --git a/source/_posts/2014-07-02-Watch-analytics-with-strap.md b/source/_posts/2014-07-02-Watch-analytics-with-strap.md
@@ -40,7 +40,7 @@ with the REST service provided by What3Words.
 Note: If you have a companion app for iOS or Android, we've got you covered! We
 have 
 [quick start guides](https://github.com/strap/strap_sdk_pebble/tree/master/companion) 
-for those platforms on our developer portal.
+for those platforms on our developer dashboard.
 
 Before you get started, signup for an account at
 https://www.straphq.com/register - it's free without limits during our public
diff --git a/source/_posts/2015-03-20-Getting-Started-With-Timeline.md b/source/_posts/2015-03-20-Getting-Started-With-Timeline.md
@@ -37,7 +37,7 @@ to get information about our packages. We'll go over the specifics of how to:
 - Use the [PebbleKit JS timeline APIs](/guides/pebble-timeline/timeline-js/)
 - Setup a server that utilizes the [pebble-api](https://www.npmjs.com/package/pebble-api)
 npm module
-- Enable timeline for the app through the [Developer Portal]({{ site.links.devportal }})
+- Enable timeline for the app through the [Developer Dashboard]({{ site.links.devportal }})
 
 ## Setup
 
@@ -262,16 +262,16 @@ be delivered, we arbitrarily set the time of the pin to noon.
 > Note in this current implementation users are stored in memory. A better
 implementation would store packages in a database.
 
-## Enable Timeline in the Developer Portal
+## Enable Timeline in the Developer Dashboard
 
 We have almost everything setup, but our app won't work correctly with the
-timeline web APIs until we upload the app's pbw to the Pebble Developer Portal
+timeline web APIs until we upload the app's pbw to the Pebble Developer Dashboard
 and enable timeline.
 
 In order to enable timeline, perform the following steps:
 
 0. Make sure you have a new and unique uuid. If you used the example from GitHub you will have to change it in your `appinfo.json`. To generate a new UUID, [you can use this tool](https://www.uuidgenerator.net/version4)
-1. Login to the [Developer Portal]({{ site.links.devportal }})
+1. Login to the [Developer Dashboard]({{ site.links.devportal }})
 2. Click the Add Watchapp button on the portal (you don't need to upload any image assets)
 3. Upload your pbw by adding a release (located in the build folder of your project)
 4. Click the Enable Timeline button
diff --git a/source/_posts/2015-03-27-Pebble-at-PearlHacks.md b/source/_posts/2015-03-27-Pebble-at-PearlHacks.md
@@ -34,6 +34,6 @@ From the high school students who used our SDK to learn C and wrote an app in un
 
 Pebblers in Los Angeles or the College Park, Maryland area - we’re coming to you very soon! We’ll be at LA Hacks from April 3rd-5th and Bitcamp from April 10th-12th, and we’d love to see you. Stop by our table and come hang out! Check out our [events page](/community/events/) for more information about where we’ll be in the upcoming months.
 
- **Have you created an app at a hackathon but haven't submitted it to the appstore yet? We would love for you to show your app to the world! Head over to the [Developer Portal](https://dev-portal.getpebble.com/developer) to get started.**
+ **Have you created an app at a hackathon but haven't submitted it to the appstore yet? We would love for you to show your app to the world! Head over to the [Developer Dashboard](https://dev-portal.getpebble.com/developer) to get started.**
 
 Much love from our team and we'll see you at the [next event](/community/events/)!
diff --git a/source/_posts/2015-04-16-Deploying-A-Server-For-Your-Timeline-Enabled-App-With-Heroku.md b/source/_posts/2015-04-16-Deploying-A-Server-For-Your-Timeline-Enabled-App-With-Heroku.md
@@ -72,7 +72,7 @@ $ npm install express pebble-api --save
 ```
 
 In order to talk to the timeline web API, you need to obtain an API key from the
-[Developer Portal](https://dev-portal.getpebble.com/). Once you've obtained the
+[Developer Dashboard](https://dev-portal.getpebble.com/). Once you've obtained the
 API key you need to set it as an environment variable, so the `pebble-api` npm
 module can use it.
 
diff --git a/source/_posts/2015-10-29-ios-migration.md b/source/_posts/2015-10-29-ios-migration.md
@@ -89,8 +89,8 @@ text to the dialog with `NSBluetoothPeripheralUsageDescription` to your
 }
 ```
 
-### Specify that your app is built with PebbleKit 3.0 in the Developer Portal
-Go to edit the companion app listing in your [developer portal]({{ site.links.devportal }}) page and check the box for "Was this iOS app compiled with PebbleKit iOS 3.0 or newer?" This way, users on Pebble Time Round will be able to see your app in the appstore.
+### Specify that your app is built with PebbleKit 3.0 in the Developer Dashboard
+Go to edit the companion app listing in your [developer dashboard]({{ site.links.devportal }}) page and check the box for "Was this iOS app compiled with PebbleKit iOS 3.0 or newer?" This way, users on Pebble Time Round will be able to see your app in the appstore.
 
 ![](/images/blog/checkbox.png)
 
diff --git a/source/community/events/developer-retreat-2015/detailed-schedule.md b/source/community/events/developer-retreat-2015/detailed-schedule.md
@@ -172,7 +172,7 @@ A group discussion about the Pebble community. Forums, feedback, surveys, code s
 
 #### 17:30 - Data Analytics and Pebble 
 
-Jack Chai (Data Scientist) takes us through the new Developer Portal analytics and delves into battery performance. He also reveals some interesting insights into levels of user interaction and how your projects could benefit from integration with timeline.
+Jack Chai (Data Scientist) takes us through the new Developer Dashboard analytics and delves into battery performance. He also reveals some interesting insights into levels of user interaction and how your projects could benefit from integration with timeline.
 
 #### 18:00 - Dinner
 
diff --git a/source/community/events/developer-retreat-2015/index.md b/source/community/events/developer-retreat-2015/index.md
@@ -211,7 +211,7 @@ community. Forums, Slack, surveys, code samples, our newsletter, and community p
 
 #### Data Analytics and Pebble 
 
-Jack Chai (Data Scientist) takes us through the new Developer Portal analytics
+Jack Chai (Data Scientist) takes us through the new Developer Dashboard analytics
 and delves into battery performance. He also reveals some interesting
 insights into levels of user interaction and how your projects could benefit
 from integration with timeline.
diff --git a/source/more/index.html b/source/more/index.html
@@ -38,7 +38,7 @@ <h3><a href="/contact/">Contact Form</a></h3>
       <h3><a href="/legal/">Legal Agreements</a></h3>
       <p>
         Some of the developer-related Pebble legal agreements that cover your
-        usage of this site, the Developer Portal, and the Pebble SDK.
+        usage of this site, the Developer Dashboard, and the Pebble SDK.
       <h3><a href="/faqs/">Frequently Asked Questions</a></h3>
       <p>
         A collection of some of the questions that are most frequently asked by developers.
