Remove CloudPebble vs SDK specific blocks in content

Signed-off-by: C-D-Lewis <[email protected]>

Author: C-D-Lewis

docs/markdown.md

@@ -225,27 +225,6 @@ release.
 {% endalert %}
 ```
 
-### SDK Platform Specific Paragraphs
-
-On pages that have the SDK Platform choice system, you can tag paragraphs as
-being only relevant for CloudPebble or local SDK users. Text, code snippets,
-images, and other markdown are all supported.
-
-First, add `platform_choice: true` to the page YAML metadata.
-
-Specify platform-specific sections of markdown using the `platform` Liquid tag:
-
-```
-{% platform local %}
-Add the resource to your project in `package.json`.
-{% endplatform %}
-
-{% platform cloudpebble %}
-Add the resource to your project by clicking 'Add New' next to 'Resources' in
-the project sidebar.
-{% endplatform %}
-```
-
 ### Formatting
 
 The following additional text formatting syntax is supported.

source/_guides/app-resources/animated-images.md

@@ -19,7 +19,6 @@ description: |
   display them in your app.
 guide_group: app-resources
 order: 0
-platform_choice: true
 ---
 
 The Pebble SDK allows animated images to be played inside an app using the
@@ -47,7 +46,6 @@ A `.gif` file can be converted to the APNG `.png` format with
 
 ## Adding an APNG
 
-{% platform local %}
 Include the APNG file in the `resources` array in `package.json` as a `raw`
 resource:
 
@@ -62,12 +60,6 @@ resource:
   ]
 }
 ```
-{% endplatform %}
-
-{% platform cloudpebble %}
-To add the APNG file as a raw resource, click 'Add New' in the Resources section
-of the sidebar, and set the 'Resource Type' as 'raw binary blob'.
-{% endplatform %}
 
 ## Displaying APNG Frames
 

source/_guides/app-resources/fonts.md

@@ -18,7 +18,6 @@ description: |
   How to use built-in system fonts, or add your own font resources to a project.
 guide_group: app-resources
 order: 3
-platform_choice: true
 ---
 
 
@@ -77,7 +76,6 @@ graphics_draw_text(ctx, text, fonts_get_system_font(FONT_KEY_GOTHIC_24), bounds,
 
 ## Adding a Custom Font
 
-{% platform local %}
 After placing the font file in the project's `resources` directory, the custom
 font can be added to a project as `font` `type` item in the `media` array in
 `package.json`. The `name` field's contents will be made available at compile
@@ -95,18 +93,6 @@ For example:
   ]
 }
 ```
-{% endplatform %}
-
-{% platform cloudpebble %}
-To add a custom font file to your project, click 'Add New' in the Resources
-section of the sidebar. Set the 'Resource Type' to 'TrueType font', and upload
-the file using the 'Choose file' button. Choose an 'Identifier', which will be
-made available at compile time with `RESOURCE_ID_` at the front. This must end
-with the desired font size ("EXAMPLE_FONT_20", for example).
-
-Configure the other options as appropriate, then hit 'Save' to save the
-resource.
-{% endplatform %}
 
 {% alert important %}
 The maximum recommended font size is 48.
@@ -180,13 +166,6 @@ font character sets in common watchapp scenarios:
 | `[0-9:A-Za-z° ]` | Time, date, and degree symbol for temperature gauges. |
 | `[0-9°CF ]` | Numbers and degree symbol with 'C' and 'F' for temperature gauges. |
 
-{% platform cloudpebble %}
-Open the font's configuration screen under 'Resources', then enter the desired
-regex in the 'Characters' field. Check the preview of the new set of characters,
-then choose 'Save'.
-{% endplatform %}
-
-{% platform local %}
 Add the `characterRegex` key to any font objects in `package.json`'s
 `media` array.
 
@@ -200,7 +179,6 @@ Add the `characterRegex` key to any font objects in `package.json`'s
   }
 ]
 ```
-{% endplatform %}
 
 Check out
 [regular-expressions.info](http://www.regular-expressions.info/tutorial.html)

source/_guides/app-resources/images.md

@@ -18,7 +18,6 @@ description: |
   How to add image resources to a project and display them in your app.
 guide_group: app-resources
 order: 4
-platform_choice: true
 ---
 
 Images can be displayed in a Pebble app by adding them as a project resource.
@@ -57,13 +56,6 @@ are available below. Use these when creating color image resources:
 
 ## Import the Image
 
-{% platform cloudpebble %}
-Add the `.png` file as a resource using the 'Add New' button next to
-'Resources'. Give the resource a suitable 'Identifier' such as 'EXAMPLE_IMAGE'
-and click 'Save'.
-{% endplatform %}
-
-{% platform local %}
 After placing the image in the project's `resources` directory, add an entry to
 the `resources` item in `package.json`. Specify the `type` as `bitmap`, choose a
 `name` (to be used in code) and supply the path relative to the project's
@@ -80,7 +72,6 @@ the `resources` item in `package.json`. Specify the `type` as `bitmap`, choose a
   ]
 },
 ```
-{% endplatform %}
 
 
 ## Specifying an Image Resource
@@ -96,13 +87,6 @@ Resources of this type can be optimized using additional attributes:
 | `storageFormat` | Optional. Determines the file format used for storage. Using `spaceOptimization` instead is preferred. | `pbi` or `png`. |
 | `spaceOptimization` | Optional. Determines whether the output resource is optimized for low runtime memory or low resource space usage. | `storage` or `memory`. |
 
-{% platform cloudpebble %}
-These attributes can be selected in CloudPebble from the resource's page:
-
-![](/images/guides/app-resources/cp-bitmap-attributes.png)
-{% endplatform %}
-
-{% platform local %}
 An example usage of these attributes in `package.json` is shown below:
 
 ```js
@@ -114,7 +98,6 @@ An example usage of these attributes in `package.json` is shown below:
   "spaceOptimization": "memory"
 }
 ```
-{% endplatform %}
 
 On all platforms `memoryFormat` will default to `Smallest`. On Aplite
 `spaceOptimization` will default to `memory`, and `storage` on all other
@@ -159,15 +142,8 @@ stored in while the app is running:
 static GBitmap *s_bitmap;
 ```
 
-{% platform cloudpebble %}
-Create the ``GBitmap``, specifying the 'Identifier' chosen earlier, prefixed
-with `RESOURCE_ID_`. This will manage the image data:
-{% endplatform %}
-
-{% platform local %}
 Create the ``GBitmap``, specifying the `name` chosen earlier, prefixed with
 `RESOURCE_ID_`. This will manage the image data:
-{% endplatform %}
 
 ```c
 s_bitmap = gbitmap_create_with_resource(RESOURCE_ID_EXAMPLE_IMAGE);

source/_guides/app-resources/index.md

@@ -21,7 +21,6 @@ menu: false
 permalink: /guides/app-resources/
 generate_toc: false
 hide_comments: true
-platform_choice: true
 ---
 
 The Pebble SDK allows apps to include extra files as app resources. These files
@@ -37,18 +36,10 @@ Aplite platform, and **256 kB** on the Basalt and Chalk platforms. These limits
 include resources used by included Pebble Packages.
 {% endalert %}
 
-{% platform local %}
 App resources are included in a project by being listed in the `media` property
 of `package.json`, and are converted into suitable firmware-compatible formats
 at build time. Examples of this are shown in each type of resource's respective
 guide.
-{% endplatform %}
-
-{% platform cloudpebble %}
-App resources are included in a project by clicking the 'Add New' button under
-'Resources' and specifying the 'Resource Type' as appropriate. These are then
-converted into suitable firmware-compatible formats at build time.
-{% endplatform %}
 
 
 ## Contents

source/_guides/app-resources/raw-data-files.md

@@ -18,7 +18,6 @@ description: |
   How to add raw data resources to a project and read them in your app.
 guide_group: app-resources
 order: 7
-platform_choice: true
 ---
 
 Some kinds of apps will require extra data that is not a font or an image. In
@@ -34,7 +33,6 @@ dictionaries, CSV data files, etc.
 
 ## Adding Raw Data Files
 
-{% platform local %}
 To add a file as a raw resource, specify its `type` as `raw` in `package.json`.
 An example is shown below:
 
@@ -49,12 +47,6 @@ An example is shown below:
   ]
 }
 ```
-{% endplatform %}
-
-{% platform cloudpebble %}
-To add a file as a raw resource, click 'Add New' in the Resources section of the
-sidebar, and set the 'Resource Type' as 'raw binary blob'.
-{% endplatform %}
 
 
 ## Reading Bytes and Byte Ranges

source/_guides/communication/advanced-communication.md

@@ -31,7 +31,6 @@ related_examples:
     url: https://github.com/pebble-examples/png-download-example
   - title: Pebble Faces
     url: https://github.com/pebble-examples/pebble-faces
-platform_choice: true
 ---
 
 Many types of connected Pebble watchapps and watchfaces perform common tasks
@@ -52,8 +51,6 @@ code implements the `appmessage` event listsner, it is ready to receive data.
 > for such an event thanks to the `Intent` system. iOS companion apps must wait
 > for `-watchDidConnect:`.
 
-<div class="platform-specific" data-sdk-platform="local">
-{% markdown %}
 A simple method is to define a key in `package.json` that will be interpreted by
 the watchapp to mean that the JS environment is ready for exchange data:
 
@@ -62,17 +59,6 @@ the watchapp to mean that the JS environment is ready for exchange data:
   "JSReady"
 ]
 ```
-{% endmarkdown %}
-</div>
-
-<div class="platform-specific" data-sdk-platform="cloudpebble">
-{% markdown %}
-A simple method is to define a key in Settings that will be interpreted by
-the watchapp to mean that the JS environment is ready for exchange data:
-
-* JSReady
-{% endmarkdown %}
-</div>
 
 The watchapp should implement a variable that describes if the `ready` event has
 occured. An example is shown below:
@@ -258,20 +244,9 @@ static int s_index = 0;
 
 When a message has been sent, this index is used to construct the next message:
 
-<div class="platform-specific" data-sdk-platform="local">
-{% markdown %}
 > Note: A useful key scheme is to use the item's array index as the key. For
 > PebbleKit JS that number of keys will have to be declared in `package.json`,
 > like so: `someArray[6]`
-{% endmarkdown %}
-</div>
-<div class="platform-specific" data-sdk-platform="cloudpebble">
-{% markdown %}
-> Note: A useful key scheme is to use the item's array index as the key. For
-> PebbleKit JS that number of keys will have to be declared in the project's
-> 'Settings' page, like so: `someArray[6]`
-{% endmarkdown %}
-</div>
 
 ```c
 static void outbox_sent_handler(DictionaryIterator *iter, void *context) {

source/_guides/communication/index.md

@@ -21,7 +21,6 @@ menu: false
 permalink: /guides/communication/
 generate_toc: false
 hide_comments: true
-platform_choice: true
 ---
 
 All Pebble watchapps and watchfaces have the ability to communicate with the
@@ -76,18 +75,8 @@ iOS.
 All messages sent from a Pebble watchapp or watchface will be delivered to the
 appropriate phone app depending on the layout of the developer's project:
 
-<div class="platform-specific" data-sdk-platform="local">
-{% markdown %}
 * If at least an `index.js` file is present in `src/pkjs/`, the message will be
   handled by PebbleKit JS.
-{% endmarkdown %}
-</div>
-<div class="platform-specific" data-sdk-platform="cloudpebble">
-{% markdown %}
-* If the project contains at least one JavaScript file, the message will be
-  handled by PebbleKit JS.
-{% endmarkdown %}
-</div>
 
 * If there is no valid JS file present (at least an `index.js`) in the project,
   the message will be delivered to the official Pebble mobile app. If there is a