Way cool! The forum is generally a discussion format, so I guess the answer might depend on whether you intend to have a two way conversation. When I hear "blog", I think of more of a one-way sharing of knowledge, with some limited feedback in the comments section. That said, we do get some more "blog-style" posts in the curated #using-arduino:introductory-tutorials and #community:exhibition-gallery forum categories.
Much more "bloggy" is the Arduino Project Hub.
To circle back to our previous discussion here. Since the time we last talked Arduino has released a useful new thing for library maintainers. As explained here, there is now a dedicated web page for every library in the Library Manager index where the indexer logs are published. The URL of yours is here:
https://downloads.arduino.cc/libraries/logs/github.com/hpssjellis/portenta-pro-community-solutions/
2021/06/12 21:58:38 Scraping https://github.com/hpssjellis/portenta-pro-community-solutions.git
2021/06/12 21:58:38 Checking out tag: 0.1.2
2021/06/12 21:58:38 Release portenta-pro-community-solutions:0.2.0 already loaded, skipping
2021/06/12 21:58:38 Checking out tag: 0.2.0
2021/06/12 21:58:38 Release portenta-pro-community-solutions:0.2.0 already loaded, skipping
2021/06/12 21:58:38 Checking out tag: 0.3.0
2021/06/12 21:58:39 Release portenta-pro-community-solutions:0.2.0 already loaded, skipping
2021/06/12 21:58:39 Checking out tag: 0.4.0
2021/06/12 21:58:39 Release portenta-pro-community-solutions:0.4.0 already loaded, skipping
This can be useful for investigating the sort of problem you reported here, where a library release is not appearing in the Library Manager index. Due to the way the system works, they are currently pretty subtle in communicating the issue in this particular case (the clue is the :0.2.0 version identifier suffix being shown after checking out the repository's 0.3.0 tag). I have some ideas for how to improve on that. The output when the release is rejected for other reasons is much more clear.