fix formatting

Author: mguludag

README.md

@@ -27,6 +27,7 @@ blog/2000-10-30-my-blog-example/
 3. Add your full Markdown blog post content inside the `index.md` file.
 
 Example
+
 ```shell
 $ cat blog/2000-10-30-my-blog-example/index.md
 ---
@@ -66,33 +67,32 @@ socials:        # [optional] Include your socials (like your Github, X, Linkedin
 
 > Note: The Discourse comments plugin only works for production website (a.k.a. https://bemanproject.org/). You cannot test it locally or on preview deployments. Check [Integrate Discourse comment feature for blog posts](https://github.com/bemanproject/website/issues/25) for more details.
 
-
 4. Open a `DRAFT PR` and `wait` up to one minute for a preview deployment of your blog post.
 
-* Draft PR example: [Add blog post: My Blog Example #54](https://github.com/bemanproject/website/pull/54/).
+- Draft PR example: [Add blog post: My Blog Example #54](https://github.com/bemanproject/website/pull/54/).
 
-* Click on the `Deploy Preview` URL (format `https://deploy-preview-${PR NUMBER}--bemanproject.netlify.app/`).
+- Click on the `Deploy Preview` URL (format `https://deploy-preview-${PR NUMBER}--bemanproject.netlify.app/`).
 
-* Successful CI preview deployment example:
+- Successful CI preview deployment example:
 
 ![CI preview deployment success message](./images/tutorial/add-a-blog/ci-preview-deployment-success-message.gif)
 
-* Test your deployment.
+- Test your deployment.
 
 <details>
 <summary> [DEBUG] Inspect CI preview deployment error logs. </summary>
 
 The CI preview deployment logs should be public. Please ping a codeowner otherwise.
 
-* `DRAFT` PR example with CI preview deployment error  - [#49](https://github.com/bemanproject/website/pull/49).
+- `DRAFT` PR example with CI preview deployment error - [#49](https://github.com/bemanproject/website/pull/49).
 
-* Click on the `Latest deploy log` URL - e.g., https://app.netlify.com/sites/bemanproject/deploys/6809108974fd910008633aa9.
+- Click on the `Latest deploy log` URL - e.g., https://app.netlify.com/sites/bemanproject/deploys/6809108974fd910008633aa9.
 
-* Logs inspect example:
+- Logs inspect example:
 
 ![](./images/tutorial/add-a-blog/ci-preview-deployment-failure-message.gif)
 
-* Fix the error, commit and push the changes. Wait for new deployment.
+- Fix the error, commit and push the changes. Wait for new deployment.
 
 > If you need to browse through more recent CI preview deployments logs use https://app.netlify.com/sites/bemanproject/deploys/. Note: netlify provides a single a single CI preview deployment for each PR - latest commit, but stores logs for multiple ones.
 
@@ -101,7 +101,7 @@ The CI preview deployment logs should be public. Please ping a codeowner otherwi
 <details>
 <summary> [DEBUG] Inspect local deployment error logs. </summary>
 
-* On local setup, run `make` (see [Local development](#local-development)) and check if there is any error in the console - example:
+- On local setup, run `make` (see [Local development](#local-development)) and check if there is any error in the console - example:
 
 ```shell
 $ make
@@ -120,9 +120,9 @@ $ make
   - DavidSankel
 ```
 
-* Fix the error, re-deploy the local website.
+- Fix the error, re-deploy the local website.
 
-* Commit and push the changes. Wait for a new CI preview deployment.
+- Commit and push the changes. Wait for a new CI preview deployment.
 
 </details>
 
@@ -131,6 +131,7 @@ $ make
 6. Apply the review feedback. Get approval. Merge the PR.
 
 <!-- TODO: Replace with https://www.bemanproject.org/ after the website deployment switch. -->
+
 7. The updates are automatically deployed to the production website after a few minutes - check https://bemanproject.github.io/website/.
 
 ## Local development
@@ -204,11 +205,10 @@ To start a local development server, run:
 $ make start
 ```
 
-If everything is properly installed, the command  should open a browser window on http://localhost:3000/.
+If everything is properly installed, the command should open a browser window on http://localhost:3000/.
 
 Most changes are reflected live without having to restart the server.
 
-
 ### Generate static content for GitHub Pages deployment
 
 To generate static from the project that can be served using any static contents hosting service (like `gh-pages`).

blog/2025-01-13-beman-intro/index.md

@@ -7,8 +7,8 @@ comments: true
 
 # Beman Project Introduction Online
 
-David Sankel’s talk on Beman at 2024 CppCon is now online! 
-The presentation answers many questions about the project purpose and policies. 
+David Sankel’s talk on Beman at 2024 CppCon is now online!
+The presentation answers many questions about the project purpose and policies.
 
 https://youtu.be/f4JinCpcQOg
 

blog/2025-01-29-nyc-hackathon/index.md

@@ -11,7 +11,8 @@ comments: true
 
 Adobe hosted an exciting and intense half-day Beman hackathon where we worked on
 adding new Beman libraries, addressed infrastructure issues, and brainstormed
-designs for the Beman website. 
+designs for the Beman website.
+
 <!-- truncate -->
 
 It was awesome to collaborate in person. Here's

blog/2025-07-06-sofia-hackathon/images/beman-tidy-board.png

@@ -9,16 +9,15 @@ comments: true
 
 ![intro](./images/intro-v2.png)
 
-
 During the ISO WG21 C++ Meeting in [Sofia, June 2025](https://wg21.link/N5004), we hosted an in-person Beman - Evening Session — a mix of short presentations, a hands-on hackathon, and plenty of big ideas for the future of C++. What started as a relaxed gathering quickly turned into a productive (and caffeinated) brainstorming hub, where we explored potential C++29 library proposals, shared early-stage experiments, and even wrote code live. It was part workshop, part jam session, and fully in the spirit of what makes the C++ community so unique: collaboration, creativity, and a shared passion for pushing the language forward.
 
 <!-- truncate -->
 
-Since November 2024, we have been organizing Beman presentations at ISO WG21 C++ meetings (Warsaw 2024 - Poland, Hagenberg 2025 - Austria). Since we have been receiving positive feedback, we decided to organize another one in Sofia, June 2025 - Bulgaria.  (Note that our next session will be at CppCon in September in Colorado - stay tuned for more details!)
+Since November 2024, we have been organizing Beman presentations at ISO WG21 C++ meetings (Warsaw 2024 - Poland, Hagenberg 2025 - Austria). Since we have been receiving positive feedback, we decided to organize another one in Sofia, June 2025 - Bulgaria. (Note that our next session will be at CppCon in September in Colorado - stay tuned for more details!)
 
 ![intro](./images/intro-v1.png)
 
-We had a great turnout, with 25 participants. The evening started with a great discussion about The Beman Project and where it is going, especially considering the C++26 is closed and the design cycle  for C++29 is starting.
+We had a great turnout, with 25 participants. The evening started with a great discussion about The Beman Project and where it is going, especially considering the C++26 is closed and the design cycle for C++29 is starting.
 
 We presented our first [Production ready. API may undergo changes.](https://github.com/bemanproject/beman/blob/main/docs/beman_library_maturity_model.md#production-ready-api-may-undergo-changes) library, which is the [beman.optional](https://github.com/bemanproject/optional) library, hoping to get it into the C++26 standard and become [Production ready. Stable API.](https://github.com/bemanproject/beman/blob/main/docs/beman_library_maturity_model.md#production-ready-stable-api). We counted a total of 10 [Under development and not yet ready for production use.](https://github.com/bemanproject/beman/blob/main/docs/beman_library_maturity_model.md#production-ready-stable-api) Beman libraries.
 
@@ -34,7 +33,7 @@ The implication during the hackathon was substantial, with 10 participants worki
 
 We were very happy with the impact of that evening (Wednesday evening, in the middle of the ISO WG21 C++ Meeting), but surprises continued ...
 
-After Friday's LEWG session,  [P3655R1: std::zstring_view](https://wg21.link/P3655R1) was presented and got feedback to continue the proposed direction. As an immediate consequence of this event, a new author created the [beman.cstring_view](https://github.com/bemanproject/cstring_view) library, to pursue the C++29 proposal.
+After Friday's LEWG session, [P3655R1: std::zstring_view](https://wg21.link/P3655R1) was presented and got feedback to continue the proposed direction. As an immediate consequence of this event, a new author created the [beman.cstring_view](https://github.com/bemanproject/cstring_view) library, to pursue the C++29 proposal.
 
 The cherry on the cake was the Saturday's plenary! Lots and lots of great news for Beman folks!
 

blog/2025-07-06-sofia-hackathon/index.md

@@ -44,38 +44,49 @@ The simplest way to understand how the infra-containers are used is to look at a
 ```json
 {
   "clang": [
-    { "versions": ["20"],
+    {
+      "versions": ["20"],
       "tests": [
-        {"cxxversions": ["c++26"],
+        {
+          "cxxversions": ["c++26"],
           "tests": [
-            { "stdlibs": ["libstdc++", "libc++"],
+            {
+              "stdlibs": ["libstdc++", "libc++"],
               "tests": [
-                "Debug.Default", "Release.Default", "Release.MaxSan",
-                "Debug.Werror", "Debug.Dynamic"
+                "Debug.Default",
+                "Release.Default",
+                "Release.MaxSan",
+                "Debug.Werror",
+                "Debug.Dynamic"
               ]
             }
           ]
         },
-        { "cxxversions": ["c++23", "c++20"],
+        {
+          "cxxversions": ["c++23", "c++20"],
           "tests": [
-            {"stdlibs": ["libstdc++", "libc++"], "tests": ["Release.Default"]}
+            { "stdlibs": ["libstdc++", "libc++"], "tests": ["Release.Default"] }
           ]
         }
       ]
     },
-    { "versions": ["19", "18"],
+    {
+      "versions": ["19", "18"],
       "tests": [
-        { "cxxversions": ["c++26", "c++23", "c++20"],
+        {
+          "cxxversions": ["c++26", "c++23", "c++20"],
           "tests": [
-            {"stdlibs": ["libstdc++", "libc++"], "tests": ["Release.Default"]}
+            { "stdlibs": ["libstdc++", "libc++"], "tests": ["Release.Default"] }
           ]
         }
       ]
     },
-    { "versions": ["17"],
+    {
+      "versions": ["17"],
       "tests": [
-        { "cxxversions": ["c++26", "c++23", "c++20"],
-          "tests": [{"stdlibs": ["libc++"], "tests": ["Release.Default"]}]
+        {
+          "cxxversions": ["c++26", "c++23", "c++20"],
+          "tests": [{ "stdlibs": ["libc++"], "tests": ["Release.Default"] }]
         }
       ]
     }

blog/2025-09-15-beman-infra-containers/index.md

@@ -26,7 +26,7 @@ dabrahams:
     github: dabrahams
 
 dietmarkuehl:
-  name: Dietmar Kühl 
+  name: Dietmar Kühl
   title: Software Developer
   url: http://www.dietmar-kuehl.de/
   image_url: https://avatars.githubusercontent.com/u/1319703?v=4
@@ -37,7 +37,7 @@ dietmarkuehl:
     linkedin: dietmar-kühl
 
 ednolan:
-  name: Eddie Nolan 
+  name: Eddie Nolan
   title: C++ Developer
   url: https://www.ednolan.com/
   image_url: https://avatars.githubusercontent.com/u/907967?v=4
@@ -64,7 +64,7 @@ JeffGarland:
     github: JeffGarland
 
 mguludag:
-  name: Muhammed Galib Uludağ 
+  name: Muhammed Galib Uludağ
   title: SW Engineer (C++ CMake Linux Automotive)
   url: https://github.com/mguludag
   image_url: https://avatars.githubusercontent.com/u/12413639?v=4

blog/authors.yml

@@ -26,7 +26,7 @@ These Beman-compliant libraries are production-ready, fully implementing the tar
 
 ### Production ready. Stable API.
 
-These production-ready libraries offer stable, standardized APIs.  They are part of the C++ Standard and can be used as a polyfill for compilers lacking native support. Note that these libraries will be retired after two standardization cycles (6 years).
+These production-ready libraries offer stable, standardized APIs. They are part of the C++ Standard and can be used as a polyfill for compilers lacking native support. Note that these libraries will be retired after two standardization cycles (6 years).
 
 > These libraries are recommended for production usage.
 
@@ -37,11 +37,10 @@ These libraries were archived and no longer maintained. These libraries are not
 > These libraries are not recommended for production use!
 > These libraries were removed from the Beman main distribution, but the initial authors could still support them outside the Beman Project.
 
-
 Transition examples:
 
-* They were [Production ready. Stable API.](./beman_library_maturity_model.md#production-ready-stable-api) at some point, but are no longer developed or maintained, being superseded by native compiler implementations - `Mature retirement`.
+- They were [Production ready. Stable API.](./beman_library_maturity_model.md#production-ready-stable-api) at some point, but are no longer developed or maintained, being superseded by native compiler implementations - `Mature retirement`.
 
-* They were [Production ready. API may undergo changes.](./beman_library_maturity_model.md#production-ready-api-may-undergo-changes) at some point, but are no longer developed or maintained, being rejected from the ISO C+ Standardization - `Early retirement`.
+- They were [Production ready. API may undergo changes.](./beman_library_maturity_model.md#production-ready-api-may-undergo-changes) at some point, but are no longer developed or maintained, being rejected from the ISO C+ Standardization - `Early retirement`.
 
-* They were [Under development and not yet ready for production use.](./beman_library_maturity_model.md#under-development-and-not-yet-ready-for-production-use) at some point and were abandoned - `Early retirement`.
+- They were [Under development and not yet ready for production use.](./beman_library_maturity_model.md#under-development-and-not-yet-ready-for-production-use) at some point and were abandoned - `Early retirement`.