Merge branch 'main' into pedromsousalima/modulinos/revamp-get-started

Author: pedromsousalima

.github/workflows/preview.yml

@@ -12,9 +12,27 @@ concurrency:
   cancel-in-progress: true
 
 jobs:
-  run:
+
+   # This job is used to render datasheets, but only if they have changed.
+  # It's a separate job so we don't have to cleanup the machine afterwards.
+  render-datasheets:
+    name: Render Datasheets
     if: ${{ contains(github.event.pull_request.labels.*.name, 'preview') || github.ref_name == 'main' }}
     runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 1
+
+      - uses: ./.github/actions/generate-datasheets
+        with:
+          artifact-name: datasheets
+          datasheets-path: static/resources/datasheets
+
+  preview-build:
+    if: ${{ contains(github.event.pull_request.labels.*.name, 'preview') || github.ref_name == 'main' }}
+    runs-on: ubuntu-latest
+    needs: render-datasheets
     concurrency:
       group: netlify
       cancel-in-progress: false
@@ -45,15 +63,22 @@ jobs:
             Waiting for deployment to complete...
 
       - uses: actions/checkout@v4
+        with:
+          fetch-depth: 1
 
+      - name: Cleanup runner disk
+        uses: ./.github/actions/cleanup-disk 
       - uses: actions/setup-node@v4
         with:
           node-version: 18
           cache: "npm"
           cache-dependency-path: "**/package-lock.json"
 
-      - name: Render Datasheets
-        run: cd ${GITHUB_WORKSPACE}/scripts/datasheet-rendering;./render-datasheets.sh
+      - name: Retrieve Datasheets
+        uses: actions/download-artifact@v4
+        with:
+          name: datasheets
+          path: static/resources/datasheets
 
       - name: Copy Static Files
         run: |
@@ -83,7 +108,7 @@ jobs:
             ${{ runner.os }}-public-gatsby-main
 
       - run: npm install
-      - run: npm run build
+      - run: GATSBY_HF_CDN_URL="" npm run build
 
       - name: Install Netlify
         run: npm install netlify-cli@17.23.2 -g

content/arduino-cloud/01.guides/00.overview/overview.md

@@ -92,10 +92,12 @@ The configurations varies between boards, but everything is covered in the insta
 
 ### 3. Create a Thing
 
-After configuring a device, we can create a Thing, which is the **virtual twin** of your board. Here we configure network details, select device we want to associate and create the variables that we want to synchronize.
+After configuring a device, we can create a Thing, which is the **virtual twin** of your board. Here we can select the device to associate and create the variables that we want to synchronize with.
 
 ![Things in the Arduino Cloud.](assets/thing.png)
 
+To configure network details go to the [devices page](https://app.arduino.cc/devices), select your device and set the network credentials.
+
 Variables we create will be used in the sketch, and will keep synchronizing as long as the board is connected to the Cloud. 
 
 When working with your IoT projects, consider this the "main space" for configurations, as you can access your sketches from here as well. 

content/arduino-cloud/01.guides/02.arduino-c/arduino-c.md

@@ -12,7 +12,7 @@ The default option for programming your board to connect to the Arduino Cloud is
 Whenever you create a [Thing](/arduino-cloud/cloud-interface/things) in the Arduino Cloud, you automatically start generating a set of files that will handle the configurations, credentials & connection:
 - `<sketchname>.ino` - your main sketch file,
 - `thingProperties.h` - your main configuration file,
-- `arduino_secrets.h` - your credentials file (for API key, Wi-Fi network etc.)
+- `arduino_secrets.h` - your credentials file (for API key, Wi-Fi network etc.), if the board is using provisioning version 1.0. If the board is using version 2.0 the credentials are stored on the board. To find out more about this read [here](https://docs.arduino.cc/arduino-cloud/hardware/device-provisioning/).
 
 ***If you want to find out more about what the Arduino Cloud service can do, go to the [overview](/arduino-cloud/guides/overview) section.*** 
 
@@ -47,8 +47,10 @@ Next, navigate to the **Things** tab. Here you will see a list of your Things, a
 A "Thing" is a virtual twin of your hardware, and it is here that we create variables that we want to synchronize between the Cloud and board. Any changes we make here will be reflected in an [automatically generated sketch](/arduino-cloud/cloud-interface/sketches#iot-sketches).
 
 1. First, let's attach the device we want to use, by clicking the **"Select Device"** button in the **"Associated Devices"** section to the right. 
-2. let's create a new variable, call it `test`, and select it to be a `boolean` type and with a **read/write** permission.
-3. finally, configure your network in the **Network** section. Here you will enter your Wi-Fi® credentials, and if you are using an ESP32 based board, you need to enter the secret key here.
+2. Let's create a new variable, call it `test`, and select it to be a `boolean` type and with a **read/write** permission.
+
+3. Finally, configure your network in the **Network** section on the device page. Here you will enter your Wi-Fi® credentials, and if you are using an ESP32 based board, you need to enter the secret key here.
+
 
 ![Enter network credentials.](assets/esp32-only.png)
 

content/arduino-cloud/01.guides/03.esp32/esp32.md

@@ -47,8 +47,10 @@ Next, navigate to the **Things** tab. Here you will see a list of your Things, a
 A "Thing" is a virtual twin of your hardware, and it is here that we create variables that we want to synchronize between the Cloud and board. Any changes we make here will be reflected in an [automatically generated sketch](/arduino-cloud/cloud-interface/sketches#iot-sketches).
 
 1. First, let's attach the device we want to use, by clicking the **"Select Device"** button in the **"Associated Devices"** section to the right. 
-2. let's create a new variable, call it `test`, and select it to be a `boolean` type and with a **read/write** permission.
-3. finally, configure your network in the **Network** section. Here you will enter your Wi-Fi® credentials, and your **Secret Key**, obtained when configuring your device.
+2. Let's create a new variable, call it `test`, and select it to be a `boolean` type and with a **read/write** permission.
+
+3. Finally, configure your network in the **Network** section on the device page. Here you will enter your Wi-Fi® credentials, and your **Secret Key**, obtained when configuring your device.
+
 
 ![Enter network credentials.](assets/esp32-only.png)
 

content/arduino-cloud/01.guides/07.node-red/nodered-intro.md

@@ -130,7 +130,7 @@ The Thing we will create for this example is quite simple. It is a sketch to rea
 Follow the steps below to set up the Thing:
 
 - Go to the Arduino Cloud -> Thing -> Create a Thing
-- Add your Device and your Network credentials
+- Add your Device and your Network credentials, which can be changed on the device page
 - Add an integer Variable, with the name humidity, and set permissions to Read Only
 - Go to the **"Sketch"** tab and replace the code with the code below:  
 

content/arduino-cloud/02.hardware/01.devices/devices.md

@@ -46,7 +46,7 @@ Wi-Fi® devices connect to the Arduino Cloud via a local network and are suitabl
 
 Most Wi-Fi® supported Arduino boards have a crypto chip that enables secure communication. This chip is configured during setup and enables secure communication for the board without having to enter any API keys in the code.
 
-Wi-Fi devices require you to enter valid credentials for the Wi-Fi network you attempt to connect to. This is done in the Thing configuration. 
+Wi-Fi devices require you to enter valid credentials for the Wi-Fi network you attempt to connect to. This is done in the Device configuration. 
 
 ***Read more and see the list of all compatible Wi-Fi® boards in the [Arduino Cloud Wi-Fi documentation](/arduino-cloud/hardware/wifi).***