Merge branch 'main' into mcmchris/opta/user-manual-analog-exp-section

Author: mcmchris

.github/workflows/deploy-prd.yml renamed to .github/workflows/deploy-production.yml

@@ -1,4 +1,4 @@
-name: Deploy to production
+name: Deploy to docs-content.arduino.cc
 
 on:
   workflow_dispatch:
@@ -10,10 +10,15 @@ concurrency:
   group: deploy-production
   cancel-in-progress: true
 
+permissions:
+  id-token: write
+  contents: read
+
 jobs:
   build:
     if: "github.repository == 'arduino/docs-content'"
     runs-on: ubuntu-latest
+    environment: production
     env:
       REPO_ACCESS_TOKEN: ${{ secrets.REPO_ACCESS_TOKEN }}
       APP_ENV: prod
@@ -33,11 +38,12 @@ jobs:
 
       - name: Copy Static Files
         run: |
-          mkdir -p static/resources/datasheets static/resources/schematics static/resources/pinouts
+          mkdir -p static/resources/datasheets static/resources/schematics static/resources/pinouts static/resources/models
           find ./content/hardware -type f -name "*-schematics.pdf" -exec cp {} ./static/resources/schematics/ \;
           find ./content/hardware -type f -name "*-datasheet.pdf" -exec cp {} ./static/resources/datasheets/ \;
           find ./content/hardware -type f -name "*-full-pinout.pdf" -exec cp {} ./static/resources/pinouts/ \;
           find ./content/hardware -type f -name "*-pinout.png" -exec cp {} ./static/resources/pinouts/ \;
+          find ./content/hardware -type f -name "*-step.zip" -exec cp {} ./static/resources/models/ \;
 
       - name: Gatsby main cache
         uses: actions/cache@v4
@@ -60,16 +66,15 @@ jobs:
       - run: npm install
       - run: npm run build
 
-      - name: Configure AWS Credentials
-        uses: aws-actions/configure-aws-credentials@v1
+      - name: Configure AWS credentials from Production account
+        uses: aws-actions/configure-aws-credentials@v4
         with:
-          aws-access-key-id: ${{ secrets.PROD_AWS_ACCESS_KEY_ID }}
-          aws-secret-access-key: ${{ secrets.PROD_AWS_SECRET_ACCESS_KEY }}
-          aws-region: us-west-1
+          role-to-assume: ${{ secrets.PRODUCTION_IAM_ROLE }}
+          aws-region: us-east-1
 
       - name: Sync all cacheable assets
-        run: aws s3 sync --cache-control "public, max-age=31536000, immutable" --include "*.css" --include="*.js" --include="*.gif" --include="*.png" --include="*.svg" --exclude "*.html" --exclude="sw.js" --exclude="*.json" --delete public/ s3://${{ secrets.PROD_AWS_S3_BUCKET_NAME }}/
+        run: aws s3 sync --cache-control "public, max-age=31536000, immutable" --include "*.css" --include="*.js" --include="*.gif" --include="*.png" --include="*.svg" --exclude "*.html" --exclude="sw.js" --exclude="*.json" --delete public/ s3://${{ secrets.PRODUCTION_BUCKET_NAME }}/
 
       - name: Sync all non-cacheable assets
         # Don't cache any HTML or JSON file: they should always be up-to-dates
-        run: aws s3 sync --cache-control "public, max-age=0, must-revalidate" --include "*.html" --include="sw.js" --include="*.json" --include "*.css" --exclude="*.js" --exclude="*.gif" --exclude="*.png" --exclude="*.svg" --delete public/ s3://${{ secrets.PROD_AWS_S3_BUCKET_NAME }}/
+        run: aws s3 sync --cache-control "public, max-age=0, must-revalidate" --include "*.html" --include="sw.js" --include="*.json" --include "*.css" --exclude="*.js" --exclude="*.gif" --exclude="*.png" --exclude="*.svg" --delete public/ s3://${{ secrets.PRODUCTION_BUCKET_NAME }}/

.github/workflows/deploy-stg.yml renamed to .github/workflows/deploy-staging.yml

@@ -1,4 +1,4 @@
-name: Deploy to docs.oniudra.cc
+name: Deploy to docs-content.oniudra.cc
 
 on:
   workflow_dispatch:
@@ -10,9 +10,14 @@ concurrency:
   group: deploy-staging
   cancel-in-progress: true
 
+permissions:
+  id-token: write
+  contents: read
+
 jobs:
   build:
     runs-on: ubuntu-latest
+    environment: staging
     env:
       REPO_ACCESS_TOKEN: ${{ secrets.REPO_ACCESS_TOKEN }}
       APP_ENV: staging
@@ -33,11 +38,12 @@ jobs:
 
       - name: Copy Static Files
         run: |
-          mkdir -p static/resources/datasheets static/resources/schematics static/resources/pinouts
+          mkdir -p static/resources/datasheets static/resources/schematics static/resources/pinouts static/resources/models
           find ./content/hardware -type f -name "*-schematics.pdf" -exec cp {} ./static/resources/schematics/ \;
           find ./content/hardware -type f -name "*-datasheet.pdf" -exec cp {} ./static/resources/datasheets/ \;
           find ./content/hardware -type f -name "*-full-pinout.pdf" -exec cp {} ./static/resources/pinouts/ \;
           find ./content/hardware -type f -name "*-pinout.png" -exec cp {} ./static/resources/pinouts/ \;
+          find ./content/hardware -type f -name "*-step.zip" -exec cp {} ./static/resources/models/ \;
 
       - name: Gatsby main cache
         uses: actions/cache@v4
@@ -60,16 +66,15 @@ jobs:
       - run: npm install
       - run: npm run build
 
-      - name: Configure AWS Credentials
-        uses: aws-actions/configure-aws-credentials@v1
+      - name: Configure AWS credentials from Staging account
+        uses: aws-actions/configure-aws-credentials@v4
         with:
-          aws-access-key-id: ${{ secrets.STAG_AWS_ACCESS_KEY_ID }}
-          aws-secret-access-key: ${{ secrets.STAG_AWS_SECRET_ACCESS_KEY }}
-          aws-region: us-west-1
+          role-to-assume: ${{ secrets.STAGING_IAM_ROLE }}
+          aws-region: us-east-1
 
       - name: Sync all cacheable assets
-        run: aws s3 sync --cache-control "public, max-age=31536000, immutable" --include "*.css" --include="*.js" --include="*.gif" --include="*.png" --include="*.svg" --exclude "*.html" --exclude="sw.js" --exclude="*.json" --delete public/ s3://${{ secrets.STAG_AWS_S3_BUCKET_NAME }}/
+        run: aws s3 sync --cache-control "public, max-age=31536000, immutable" --include "*.css" --include="*.js" --include="*.gif" --include="*.png" --include="*.svg" --exclude "*.html" --exclude="sw.js" --exclude="*.json" --delete public/ s3://${{ secrets.STAGING_BUCKET_NAME }}/
 
       - name: Sync all non-cacheable assets
         # Don't cache any HTML or JSON file: they should always be up-to-dates
-        run: aws s3 sync --cache-control "public, max-age=0, must-revalidate" --include "*.html" --include="sw.js" --include="*.json" --include "*.css" --exclude="*.js" --exclude="*.gif" --exclude="*.png" --exclude="*.svg" --delete public/ s3://${{ secrets.STAG_AWS_S3_BUCKET_NAME }}/
+        run: aws s3 sync --cache-control "public, max-age=0, must-revalidate" --include "*.html" --include="sw.js" --include="*.json" --include "*.css" --exclude="*.js" --exclude="*.gif" --exclude="*.png" --exclude="*.svg" --delete public/ s3://${{ secrets.STAGING_BUCKET_NAME }}/

.github/workflows/preview.yml

@@ -33,7 +33,7 @@ jobs:
           issue-number: ${{ github.event.pull_request.number }}
           comment-author: "github-actions[bot]"
           body-includes: "Preview Deployment"
-          
+
       - name: Update Comment if exists
         if: github.event_name == 'pull_request' && steps.deploy-preview-comment.outputs.comment-id != 0
         uses: peter-evans/[email protected]
@@ -57,11 +57,12 @@ jobs:
 
       - name: Copy Static Files
         run: |
-          mkdir -p static/resources/datasheets static/resources/schematics static/resources/pinouts
+          mkdir -p static/resources/datasheets static/resources/schematics static/resources/pinouts static/resources/models
           find ./content/hardware -type f -name "*-schematics.pdf" -exec cp {} ./static/resources/schematics/ \;
           find ./content/hardware -type f -name "*-datasheet.pdf" -exec cp {} ./static/resources/datasheets/ \;
           find ./content/hardware -type f -name "*-full-pinout.pdf" -exec cp {} ./static/resources/pinouts/ \;
           find ./content/hardware -type f -name "*-pinout.png" -exec cp {} ./static/resources/pinouts/ \;
+          find ./content/hardware -type f -name "*-step.zip" -exec cp {} ./static/resources/models/ \;
 
       - name: Gatsby main cache
         uses: actions/cache@v4
@@ -107,7 +108,7 @@ jobs:
             --auth ${{ secrets.NETLIFY_AUTH_TOKEN }} \
             --json \
             > deploy_output.json
-      
+
       - name: Generate URL Preview
         if: github.event_name == 'pull_request'
         id: url_preview
@@ -124,7 +125,7 @@ jobs:
             ## Preview Deployment
             🚀 Preview this PR: ${{ steps.url_preview.outputs.NETLIFY_PREVIEW_URL }}
             📍 Commit SHA: ${{ github.sha }}
-      
+
       - name: Update PR Preview Comment
         if: github.event_name == 'pull_request' && steps.deploy-preview-comment.outputs.comment-id != 0
         uses: peter-evans/[email protected]

.gitignore

@@ -7,4 +7,7 @@ node_modules
 public
 src
 .DS_Store
-.vscode/settings.json
+.vscode/settings.json
+content/en
+content/de
+content/pt

content/_dev-test/content.md

@@ -0,0 +1,9 @@
+---
+id: ""
+title: ""
+categories: ""
+subCategories: ""
+leaf: false
+mainDescription: ""
+mainTitle: ""
+---

content/arduino-cloud/02.hardware/05.cellular/cellular.md

@@ -17,8 +17,6 @@ A number of Arduino boards are able to connect to the Arduino Cloud using a sim
 
 Connection through cellular networks can be considered in remote areas where there's no Wi-Fi, or in mobile projects (such as cargo tracking).
 
-***For more information, visit the [Arduino SIM page](https://store.arduino.cc/digital/sim).***
-
 ***Note that a secured connection is a memory intense operation, so there's not a lot of memory for the user application (e.g. around 2.6 kB on the MKR GSM 1400). Using a lot of Arduino Cloud variables may cause the sketch to run out of memory on boards which don't offload the SSL stack and make it crash.***
 
 ## Setup
@@ -36,12 +34,3 @@ To configure a cellular board, follow the steps below:
 Your board is now configured and ready to be used in the Arduino Cloud. 
 
 To get started, check out the official [Getting Started (Arduino / C++)](/arduino-cloud/guides/arduino-c) guide. This will guide you to successfully send data between your board and Arduino Cloud.
-
-## Network Configuration
-
-When you attach your board to a Thing, you will need to enter some credentials. With an Arduino SIM, configure it as:
-
-- **APN** - `prepay.pelion`
-- **PIN** - `0000`
-- **Username** - `arduino`
-- **Password** - `arduino`

content/arduino-cloud/03.cloud-interface/00.sketches/assets/sketch.png

@@ -8,23 +8,35 @@ author: Karl Söderby
 A sketch is a file where we write programs to run on our Arduino boards. Sketches have a `.ino` extension, which supports the Arduino programming language (a variant of C++).
 
 The Arduino Cloud has two categories of sketches:
-- **Regular sketch** - a single `.ino` file where you write a program. These sketches can be used for **any** Arduino board. 
-- **IoT Sketch** - a set of files that are automatically generated when creating a [Thing](/arduino-cloud/cloud-interface/things). This includes an `.ino` file and two header (`.h`) files that contain your Thing configuration + credentials. Only available for boards with IoT support.
+- **Sketch** - a single `.ino` file where you write a program. These sketches can be used for **any** Arduino board. 
+- **Sketch with attached Thing** - a set of files that are automatically generated when creating a [Thing](/arduino-cloud/cloud-interface/things). This includes an `.ino` file and two header (`.h`) files that contain your Thing configuration + credentials. Only available for boards with Arduino Cloud support.
 
-In this document we will take a look at how to use sketches in the Arduino Cloud environment.
+In this document, we will take a look at how to use sketches in the Arduino Cloud environment.
 
 ***If you need help getting started with programming your Arduino in the online environment, check out the [Cloud Editor](/arduino-cloud/guides/cloud-editor) tutorial.***
 
 ## Access Your Sketches
 
-You can access all your sketches at [app.arduino.cc/sketches](https://app.arduino.cc/sketches), where you can easily select between your regular sketches and IoT sketches.
+You can access all your sketches at [app.arduino.cc/sketches](https://app.arduino.cc/sketches). Here you can easily see if your sketch has a Thing connected to it by checking if it has a light blue text box next to it.
 
-![Sketches in the Arduino Cloud.](assets/sketch.png)
+![Sketches in the Arduino Cloud](./assets/sketch.png)
 
 Clicking on each sketch will direct you to the [Cloud Editor](https://create.arduino.cc/editor/), which is an online version of the Arduino IDE. Here you can write a program, compile it and upload it to your board. 
 
 ***To get started with the Cloud Editor, check out the [Cloud Editor](/arduino-cloud/guides/cloud-editor) tutorial.***
 
+### How to Create and Organize Folders
+
+You can easily organize your sketches by creating folders. Here’s how you can do it:
+
+**Create a New Folder**: Click on **Create**, then select **New Folder**.
+
+**Move Sketches into a Folder**:
+
+- **Drag and Drop**: Simply drag the sketch you want to move and drop it into the desired folder.
+
+- **Right-Click and Move**: Alternatively, click the three dots on the right, choose the option "Move to folder", and then select the folder you want to move it to.
+
 ## Regular Sketches
 
 A regular sketch in the Arduino Cloud is exactly like a sketch used in the [Arduino IDE](/software/ide-v2), with no difference whatsoever. You can take a sketch from the online IDE and compile it in the offline IDE. 
@@ -45,11 +57,11 @@ If you are new to the Arduino environment, you can check out the [Language Refer
 
 For specific features of a board, make sure to check out the [hardware documentation](/).
 
-## IoT Sketches
+## Sketches with an attached Thing
 
-IoT sketches are more complex and are generated automatically when you create a Thing and variables.
+Sketches with an attached Thing are more complex and are generated automatically when you create a Thing and variables.
 
-***Read more about this in the [Automatic Sketch Generation](/arduino-cloud/cloud-interface/sketches) documentation.***
+***Read more about [Things](/arduino-cloud/cloud-interface/things/).***
 
 ### Sketch File
 
@@ -122,13 +134,13 @@ The Remote Sketchbook feature is great as you can push/pull your sketches from t
 ***A very important note on Remote Sketchbook: when you push/pull a sketch, you will overwrite the existing sketch, similarly to how GitHub works, but without the option of retrieving your previous sketch.***
 
 
-## Recommended Code Practices (IoT Sketches)
+## Recommended Code Practices (Sketches with an attached Thing)
 
 This section highlights some important aspects of writing code with regard to the implementations in the [ArduinoIoTCloud](https://github.com/arduino-libraries/ArduinoIoTCloud).
 
 ### Watchdog Timer (WDT)
 
-All Arduino Cloud sketches use a **Watchdog Timer (WDT)** by default. The WDT can be used to automatically recover from hardware faults or unrecoverable software errors.
+Arduino Cloud sketches use a **Watchdog Timer (WDT)** by default, however, not all boards support this function. The WDT can be used to automatically recover from hardware faults or unrecoverable software errors.
 
 A WDT is essentially a countdown timer, whereas it starts counting from a set value, and upon reaching zero, it resets the board. To prevent it from reaching zero, we continuously call it from the `loop()`, using the `ArduinoCloud.update()` function.
 
@@ -140,7 +152,7 @@ The WDT can however be disabled inside of the `setup()` function, by adding the
 ArduinoCloud.begin(ArduinoIoTPreferredConnection, false).
 ```
 
-***You can view the source code of this implementation [here](https://github.com/arduino-libraries/ArduinoIoTCloud/tree/master/src/utility/watchdog).***
+***You can view the source code of this implementation [here](https://github.com/arduino-libraries/ArduinoIoTCloud/tree/master/src/utility/watchdog) and you can check if your board supports this feature [here](https://github.com/arduino-libraries/ArduinoIoTCloud?tab=readme-ov-file#what).***
 
 ### Alternatives to Delays
 

content/arduino-cloud/03.cloud-interface/00.sketches/sketches.md

@@ -336,6 +336,21 @@ An example of how it is used in a sketch:
 locationVariable = Location(51.5074, 0.1278);
 ```
 
+### Advanced Map
+
+![Advanced Map Widget](assets/widget-advanced-map.png)
+
+The advanced map widget allows you to track the location of your cloud-connected device. Using GPS within your project allows the advanced map widget to track where the linked thing has been. This widget not only shows the live location of your device but also lets you specify a time frame to view its location history and the track it produced.
+
+It can be linked with the **Location** variable. When the location updates the new location will be added to the advanced map widget and a path between the locations will be marked. The path and icon on the map can be customized in the widget settings.
+
+An example of how it is used in a sketch:
+
+```arduino
+//Location(Latitude, Longitude);
+locationVariable = Location(51.5074, 0.1278);
+```
+
 ### Chart
 
 ![Chart Widget](assets/widget-chart.png)