Skip to content

Commit 51ceed7

Browse files
lucasssvazf-hollow
andauthored
Apply suggestions from code review
Co-authored-by: ESP-Kirill <[email protected]>
1 parent cb5b091 commit 51ceed7

File tree

1 file changed

+12
-14
lines changed
  • content/blog/2025/12/arduino-library-creation

1 file changed

+12
-14
lines changed

content/blog/2025/12/arduino-library-creation/index.md

Lines changed: 12 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ tags: ["Arduino", "ESP32", "Library", "Tutorial"]
55
showAuthor: false
66
authors:
77
- "lucas-vaz"
8-
summary: "Learn how to create, structure, and publish Arduino libraries for ESP32. This step-by-step guide covers everything from basic library structure to submitting your library to the Arduino Library Manager."
8+
summary: "Learn how to create, structure, and publish Arduino libraries for ESP32. This step-by-step guide covers everything from understanding a library structure to submitting your library to the Arduino Library Manager."
99
---
1010

1111
Creating custom Arduino libraries is an excellent way to organize reusable code, share functionality with others, and make your projects more modular. This article covers the process of creating an Arduino library from scratch, using a simple "Hello World" library as a working example.
@@ -53,10 +53,10 @@ flowchart LR
5353

5454
To create an Arduino library for ESP32, you will need:
5555

56-
- Arduino IDE installed on your computer;
57-
- Arduino Core for ESP32 installed;
58-
- A text editor or IDE for writing code;
59-
- Basic understanding of C++ programming.
56+
- Arduino IDE installed on your computer
57+
- Arduino Core for ESP32 installed
58+
- A text editor or IDE for writing code
59+
- Basic understanding of C++ programming
6060

6161
If you haven't installed the Arduino Core for ESP32 yet, follow the steps in the article [Getting Started with ESP32 Arduino](https://developer.espressif.com/blog/2025/10/arduino-get-started/).
6262

@@ -413,18 +413,16 @@ Before releasing a new version, update the version number in your `library.prope
413413

414414
2. **Update the version** in `library.properties` based on the semantic versioning rules:
415415

416-
```properties
417-
version=1.1.0
418-
```
416+
```properties
417+
version=1.1.0
419418

420419
3. **Commit and tag** the new version:
421420

422-
```bash
423-
git add library.properties
424-
git commit -m "Release version 1.1.0"
425-
git tag 1.1.0
426-
git push origin main --tags
427-
```
421+
```bash
422+
git add library.properties
423+
git commit -m "Release version 1.1.0"
424+
git tag 1.1.0
425+
git push origin main --tags
428426

429427
4. **Create a release** on GitHub from the tag (optional but recommended).
430428

0 commit comments

Comments
 (0)