Skip to content

Commit 6daef67

Browse files
SEO Updates
1 parent d32fef5 commit 6daef67

13 files changed

Lines changed: 283 additions & 72 deletions

File tree

.DS_Store

2 KB
Binary file not shown.

archetypes/post.md

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
title: "{{ replace .Name "-" " " | title }}"
3+
date: {{ .Date }}
4+
description: "Write a compelling 150-160 character description here - this appears in Google search results"
5+
categories: ["Category1"]
6+
tags: ["tag1", "tag2", "tag3"]
7+
image: "featured-image.jpg"
8+
draft: true
9+
---
10+
11+
## Introduction
12+
13+
Start with a clear introduction that includes your main keyword naturally.
14+
15+
## Main Content
16+
17+
Break content into clear sections with H2 and H3 headings.
18+
19+
### Subsection
20+
21+
Use descriptive headings that include relevant keywords.
22+
23+
## Conclusion
24+
25+
Summarize key points and include a call to action.
26+
27+
---
28+
29+
<!-- SEO Tips:
30+
- Use your main keyword in the title, first paragraph, and at least one H2
31+
- Keep title under 60 characters
32+
- Write description between 150-160 characters
33+
- Use 3-5 relevant tags
34+
- Add alt text to images
35+
- Include internal links to other posts
36+
- Aim for 1000+ words for better ranking
37+
- Use bullet points and lists for readability
38+
-->

config/_default/config.toml

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,9 @@
11
# Change baseurl before deploy
2-
baseurl = "vitorribeiro.com"
2+
baseurl = "https://vitorribeiro.com"
33
languageCode = "en-us"
44
title = "Vitor Ribeiro"
5+
enableRobotsTXT = true
6+
canonifyURLs = true
57

68
# Theme i18n support
79
# Available values: en, fr, id, ja, ko, pt-br, zh-cn, zh-tw, es, de, nl, it, th, el, uk, ar
@@ -15,4 +17,9 @@ hasCJKLanguage = false
1517
disqusShortname = ""
1618

1719
[pagination]
18-
pagerSize = 5
20+
pagerSize = 5
21+
22+
[sitemap]
23+
changefreq = "weekly"
24+
priority = 0.5
25+
filename = "sitemap.xml"

content/post/KORE-SUPER-SIM-Heat-map-using-Event-Streams/index.md

Lines changed: 13 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
2-
title: "KORE SUPER SIM Heatmap using Event Streams"
2+
title: "Build a Real-Time IoT Heatmap with KORE SUPER SIM Event Streams"
33
date: 2025-11-26
4-
description: "A Github repository for a real-time geospatial dashboard using KORE SUPER SIM Event Streams, FastAPI, and Leaflet."
5-
categories: ["KORE", "KORE ONE", "SUPER SIM", "Event Streams", "Github code", "API"]
6-
tags: ["KORE", "KORE ONE", "Super SIM", "Event Streams", "Connectivity", "FastAPI", "Leaflet", "Heatmap", "IoT"]
4+
description: "Build a real-time geospatial dashboard for KORE SUPER SIM using Event Streams, FastAPI, and Leaflet. Complete GitHub code and tutorial for IoT visualization."
5+
categories: ["KORE", "API", "Event Streams", "GitHub Code"]
6+
tags: ["SUPER SIM", "KORE ONE", "Cellular Connectivity", "Python"]
77
image: "heatmap-cover.png"
88
---
99

10-
![](KORE-LOGO-SUPERSIM.png)
10+
![KORE SUPER SIM logo](KORE-LOGO-SUPERSIM.png)
1111

1212
# Visualizing KORE SUPER SIM Event Streams in Real Time
1313

@@ -17,6 +17,8 @@ In this article, I’ll show you how I built a full real-time geospatial visuali
1717

1818
You can download the code from my [**GitHub repository here**](https://github.com/naturalfunction/KORE-SUPERSIM-heatmap)
1919

20+
New to Event Streams? Start with my [**Getting Started with KORE SUPER SIM Event Streams**](/p/getting-started-with-kore-super-sim-event-streams/) guide first.
21+
2022
---
2123

2224
## ⭐ What the App Does
@@ -133,7 +135,7 @@ uvicorn app.main:app --reload
133135

134136
---
135137

136-
![](run-project.png)
138+
![Terminal showing FastAPI server running with uvicorn reload command](run-project.png)
137139

138140
## 🛠 Seed sample data
139141

@@ -156,16 +158,16 @@ done
156158
## 🛠 Map Examples
157159

158160
Map after seeding data
159-
![](heatmap.png)
161+
![Interactive heatmap showing SUPER SIM device locations with online and offline status indicators](heatmap.png)
160162

161163
Map after filtering data using the Timeline
162-
![](heatmap-filtering-timeline.png)
164+
![Heatmap filtered by timeline showing device activity at specific time period](heatmap-filtering-timeline.png)
163165

164166
Map after filtering data using the Timeline Online Only.
165-
![](heatmap-filtering-timeline-online.png)
167+
![Heatmap displaying only online devices filtered by timeline with green indicators](heatmap-filtering-timeline-online.png)
166168

167169
Map after filtering data using the Timeline Offline Only.
168-
![](heatmap-filtering-timeline-offline.png)
170+
![Heatmap showing only offline devices filtered by timeline with red indicators](heatmap-filtering-timeline-offline.png)
169171

170172
Map after clicking SHOW ALL
171-
![](heatmap-filtering-timeline-showall-max-zoom.png)
173+
![Zoomed heatmap view showing all device locations and connection towers at maximum zoom level](heatmap-filtering-timeline-showall-max-zoom.png)

content/post/getting-started-with-KORE-ConnectivityPRO-SMS-API/index.md

Lines changed: 26 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
2-
title: "Getting started with KORE ConnectivityPRO™ SMS API"
2+
title: "Getting Started with KORE ConnectivityPRO™ SMS API"
33
date: 2025-11-18
4-
description: "This article covers the basics to start using the Kore Wireless SMS API, I hope this guide helps you onboard the API faster!"
5-
categories: ["KORE", "ConnectivityPRO™", "API"]
6-
tags: ["KORE", "ConnectivityPRO™", "API", "Connectivity", "How to", "Getting Started","SMS"]
7-
image: "KORE-LOGO-CONNECTIVITYPRO.jpeg"
4+
description: "Learn how to send and receive SMS messages using KORE Wireless SMS API. Complete tutorial with authentication, webhooks, and mobile-terminated SMS examples."
5+
categories: ["KORE", "API", "Getting Started"]
6+
tags: ["ConnectivityPRO™", "Cellular Connectivity", "SMS", "REST API", "messaging"]
7+
image: "KORE-LOGO-CONNECTIVITYPRO.jpeg"
88
---
99

10-
![](KORE-LOGO-CONNECTIVITYPRO.png)
10+
![KORE ConnectivityPRO™ logo](KORE-LOGO-CONNECTIVITYPRO.png)
1111

1212
## Introduction
1313

@@ -49,6 +49,8 @@ It enables KORE Wireless to manage all APIs from a single point — referred to
4949

5050
This article focuses on the [**SMS API**](https://developer-app.korewireless.com/api?product=SMS#overview), which allows you to send & receive SMS to your SIMs via API.
5151

52+
If you're new to KORE APIs, check out my [**Getting Started with KORE ConnectivityPRO™ API**](/p/getting-started-with-kore-connectivitypro-api/) guide first.
53+
5254
---
5355
## Introduction
5456

@@ -59,7 +61,7 @@ Once you have access to the Developer Portal:
5961
1. Follow the [**Getting Started**](https://developer-app.korewireless.com/getting-started?id=2.1.1.5) guide to create your first [**client**](https://developer-app.korewireless.com/getting-started?id=2.1.1.1).
6062
2. Selecting the client will let you view your **Production** keys.
6163

62-
![](devportal-api-client.png)
64+
![KORE Developer Portal showing API client configuration with production keys](devportal-api-client.png)
6365

6466
---
6567
### Getting an Authentication Token
@@ -76,7 +78,7 @@ When you create a client, you receive:
7678

7779
See below for a high-level overview.
7880

79-
![](KORE-OAuth-Diagram.png)
81+
![OAuth 2.0 Client Credentials workflow diagram showing authentication flow between client, API, and token endpoint](KORE-OAuth-Diagram.png)
8082

8183
Using Postman, set up a POST request to https://api.korewireless.com/Api/api/token for Production.
8284

@@ -86,7 +88,7 @@ The body of your request must include:
8688
- The key **“client_id”** key with a value from the Developer Portal.
8789
- The key **“client_secret”** key with a value from the Developer Portal.
8890

89-
![](postman-get-token.jpg)
91+
![Postman interface showing POST request to get authentication token with client credentials](postman-get-token.jpg)
9092

9193
You can also use **cURL** to get an authentication token, use the example below to perform a request.
9294

@@ -102,7 +104,7 @@ curl -L -X POST "https://api.korewireless.com/Api/api/token" \
102104

103105
Here’s what the **cURL** returns:
104106

105-
![](curl-response.jpg)
107+
![Terminal showing cURL response with authentication token and expiration time](curl-response.jpg)
106108

107109
The authentication Token is valid for 10 hours, after 10 hours, you will need to call the authentication endpoint again for a new token.
108110

@@ -205,9 +207,9 @@ After sending the GET request, you should receive a JSON response containing all
205207
</code>
206208
</pre>
207209

208-
You can also obtain the MSISDN value using our ConnectivityPro web app using the Subscription details page https://connect-app.korewireless.com/subscriptions/8910390000075864728
210+
You can also obtain the MSISDN value using our ConnectivityPro web app using the Subscription details page https://connect-app.korewireless.com/subscriptions/8910390000075864728
209211

210-
![](cpro-sim-details.png)
212+
![ConnectivityPRO web app showing SIM subscription details page with MSISDN information](cpro-sim-details.png)
211213

212214

213215
## SMS API
@@ -299,7 +301,7 @@ After a successful request is sent, you should get a response like this:
299301
Here’s a screenshot of the received SMS message on a [**NEXA Rhino C6 handheld**](https://rhinomobility.com/c6/features).
300302

301303

302-
![](c6-sms.jpg)
304+
![NEXA Rhino C6 handheld device displaying received SMS message](c6-sms.jpg)
303305

304306
### Receiving a Mobile Originated SMS
305307

@@ -317,7 +319,7 @@ To configure your SMS-MO Alert, please navigate to Manage Rules,
317319

318320
3. Then click the Add Rule button.
319321

320-
![](manage-rules.png)
322+
![Developer Portal Manage Rules page showing SMS alerting configuration options](manage-rules.png)
321323

322324
For your Rule:
323325

@@ -329,7 +331,7 @@ For your Rule:
329331

330332
4. Select your the **account-id** under Account Id
331333

332-
![](add-rule.png)
334+
![Add Rule form showing SMS alerting configuration with account ID selection](add-rule.png)
333335

334336
For your Events:
335337

@@ -339,7 +341,7 @@ For your Events:
339341

340342
3. Click **Next**
341343

342-
![](events.jpg)
344+
![Event configuration showing SMS-MO message event type selection](events.jpg)
343345

344346
For your Conditions:
345347

@@ -351,7 +353,7 @@ For your Conditions:
351353

352354
4. Click **Next**
353355

354-
![](conditions.jpg)
356+
![Conditions configuration showing direction attribute set to from_sim for mobile originated SMS](conditions.jpg)
355357

356358
For your Webhook
357359

@@ -361,7 +363,7 @@ For your Webhook
361363

362364
In my example I will be using Pipedream
363365

364-
![](actions.jpg)
366+
![Webhook action configuration with Pipedream URL for receiving SMS alerts](actions.jpg)
365367

366368
For your Alert Strategy the default value of **Immediate** is selected, please click Save.
367369

@@ -394,7 +396,7 @@ Now you are ready to receive MO SMS, give it a try and validate you have an entr
394396
</code>
395397
</pre>
396398

397-
![](pipedream.png)
399+
![Pipedream interface showing received mobile originated SMS webhook payload with message data](pipedream.png)
398400

399401
### Creating a Mobile Terminated SMS monitoring queue
400402

@@ -412,7 +414,7 @@ To configure your SMS-MT Alert, please navigate to Manage Rules,
412414

413415
4. Select your the **account-id** under Account Id
414416

415-
![](add-rule-mt.png)
417+
![Add Rule form for SMS-MT status monitoring with account ID configuration](add-rule-mt.png)
416418

417419
For your Events:
418420

@@ -422,7 +424,7 @@ For your Events:
422424

423425
3. Click **Next**
424426

425-
![](events-mt.png)
427+
![Event configuration showing SMS-MT Status event type for mobile terminated messages](events-mt.png)
426428

427429
For your Conditions:
428430

@@ -434,7 +436,7 @@ For your Conditions:
434436

435437
4. Click **Next**
436438

437-
![](conditions-mt.jpg)
439+
![Conditions configuration showing direction attribute set to to_sim for mobile terminated SMS](conditions-mt.jpg)
438440

439441
For your Webhook
440442

@@ -591,13 +593,13 @@ If you have any questions, don’t hesitate to reach out to me [here](mailto:vri
591593

592594
KORE offers a Postman collection that enables you to validate the APIs without writing any code, alternatively, the Developer Portal documentation also includes the ability to call the endpoints, you must be logged into the Developer Portal to view this [Auth Section](https://developer-app.korewireless.com/api?product=Connectivity#auth).
593595

594-
![](devportal-postman.png)
596+
![KORE Developer Portal showing Postman collection download option for API testing](devportal-postman.png)
595597

596598
---
597599
### Github
598600

599601
KORE Wireless has a [GitHub repository](https://github.com/korewireless) containing code samples. You can view code samples related to the Connectivity API [here](https://github.com/korewireless/Developer-API).
600602

601-
![](kore-github.png)
603+
![KORE Wireless GitHub repository page showing Developer API code samples](kore-github.png)
602604

603605
You can also read this article on Substack [here](https://vitorr.substack.com/p/getting-started-with-the-kore-wireless)

content/post/getting-started-with-KORE-SUPER-SIM-Event-Streams/index.md

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
22
title: "Getting Started with KORE SUPER SIM Event Streams"
33
date: 2025-11-27
4-
description: "A practical guide on how to set up Destinations, create Streaming Rules, and receive real-time events using KORE SUPER SIM Event Streams."
5-
categories: ["KORE", "KORE ONE", "SUPER", "API"]
6-
tags: ["KORE", "KORE ONE", "Event Streams", "Super SIM", "Streaming", "Connectivity", "How to", "Getting Started"]
4+
description: "Step-by-step guide to configure KORE SUPER SIM Event Streams. Learn to set up destinations, create streaming rules, and receive real-time IoT connectivity events."
5+
categories: ["KORE", "API", "Event Streams", "Getting Started"]
6+
tags: ["SUPER SIM", "KORE ONE", "Cellular Connectivity", "Python"]
77
image: "KORE-ONE.png"
88
---
99

10-
![](KORE-Connect-the-dots.jpg)
10+
![KORE Connect the dots illustration showing IoT connectivity](KORE-Connect-the-dots.jpg)
1111

1212
## Introduction
1313

@@ -18,8 +18,10 @@ This article will show you how to configure **Destinations**, create **Streaming
1818

1919
It’s inspired by the [**official documentation**](https://docs.korewireless.com/en-us/supersim/supersim-first-steps/get-started-with-super-sim-connection-events) but written with a more practical, step-by-step approach.
2020

21+
Want to see Event Streams in action? Check out my [**SUPER SIM Heatmap tutorial**](/p/kore-super-sim-heat-map-using-event-streams/) that builds a real-time visualization dashboard.
22+
2123
---
22-
![](KORE-LOGO-SUPERSIM.png)
24+
![KORE SUPER SIM logo](KORE-LOGO-SUPERSIM.png)
2325

2426
## Prerequisites
2527

@@ -40,7 +42,7 @@ You don’t need advanced programming knowledge, but you should be familiar with
4042
- [REST APIs](https://aws.amazon.com/what-is/restful-api/)
4143

4244
---
43-
![](KORE-LOGO-CONSOLE.png)
45+
![KORE Console logo](KORE-LOGO-CONSOLE.png)
4446
## Overview
4547

4648
**Event Streams** allow you to receive real-time events from KORE products delivered to a destination you configure.
@@ -66,7 +68,7 @@ You can choose:
6668
- A **Webhook** (recommended for simple setups and testing)
6769
- An **AWS Kinesis Stream** (recommended for production)
6870

69-
![](KORE-Developer-Console-Destination-Options.png)
71+
![KORE Developer Console showing destination options for Webhook and AWS Kinesis](KORE-Developer-Console-Destination-Options.png)
7072

7173
---
7274

@@ -99,7 +101,7 @@ A Streaming Rule defines **which** event types you want and **where** they shoul
99101
1. Go to **Event Streams → Streaming Rules**.
100102
2. Select **“+ Create”**.
101103

102-
![](KORE-Developer-Console-Create-Streaming-Rules.png)
104+
![KORE Developer Console interface for creating streaming rules with event type selection](KORE-Developer-Console-Create-Streaming-Rules.png)
103105

104106
3. Configure:
105107

@@ -210,7 +212,7 @@ KORE offers a GitHub repository with code samples:
210212

211213
- https://github.com/korewireless
212214

213-
![](kore-github.png) 4
215+
![KORE Wireless GitHub repository page showing Developer API code samples](kore-github.png)
214216

215217
More Event Streams examples will be added over time.
216218

0 commit comments

Comments
 (0)