feat: migrate blog posts from ipynb/md to qmd format

[Shivampal157]

• Update conda/dev.yaml for quarto support
• Update .makim.yaml to render qmd to md in pipeline
• Add scripts/convert-blog-posts-to-qmd.py
• Update CONTRIBUTING.md with qmd-first workflow

Fixes #255

[Shivampal157]

Hi @xmnlab , all CI checks are now passing. Please review when you get a chance. Happy to make any changes if needed!

[xmnlab]

thanks for working on that @Shivampal157
just add a few comments inline here

could you also remove the previous ipynb files inside the blog sub-folders?

[xmnlab]

probably we don't need this script anymore

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[Shivampal157]

@xmnlab Hi! I’ve migrated the blog posts to .qmd, removed the legacy ipynb files, and updated the CI config, but the Linter job is still failing and I can’t see the full logs as an external contributor.
Could you please share the exact error message (file + hook) from the Linter step so I can fix it properly?

[xmnlab]

hi @Shivampal157 , the logs should be open for everyone
this is the link to the raw log: https://productionresultssa3.blob.core.windows.net/actions-results/88b728fe-f631-4962-9ff0-5839d3bd8ea6/workflow-job-run-3174f0a6-9cab-5669-b8cf-0a9a0db02301/logs/job/job-logs.txt?rsct=text%2Fplain&se=2026-03-11T20%3A43%3A29Z&sig=737V%2Bvojaj7koNuX7n3%2FORVdltuxIi6Xb12hd3mYmSo%3D&ske=2026-03-11T23%3A14%3A27Z&skoid=ca7593d4-ee42-46cd-af88-8b886a2f84eb&sks=b&skt=2026-03-11T19%3A14%3A27Z&sktid=398a6654-997b-47e9-b12b-9515b896b4de&skv=2025-11-05&sp=r&spr=https&sr=b&st=2026-03-11T20%3A33%3A24Z&sv=2025-11-05

[Shivampal157]

@xmnlab, I’ve tried to fix the ci locally on windows, but makim and the quarto step depend on a linux‑style environment (fcntl, /bin/bash, and the blog-post.html template path), so I can’t reproduce the ci build exactly.
The failing hook is mkdocs-build because makim pages.build regenerates some pages/blog/**/index.md files in ci and they don’t match what’s in my commit.
could you please either:

run makim pages.build in your Linux environment and push the updated pages/blog/**/index.md, or
suggest the preferred way for contributors on window to regenerate those files so they match the ci output? once I know the correct workflow or have the updated index.md files, I’ll happily continue and adjust my PR if needed.

[xmnlab]

@Shivampal157 I made some changes.

• the script that check the links shouldn't be changed, so I changed it back to its previous version.
• the makim task should fail if the quarto cli is not found.
• change the default thumbnail

and made a few other minor changes

now I realized that the new version of the md, doesn't have the correct headers .. which means that the quarto md is not properly setting the header for the yaml header for the final version of the md.

diff --git a/pages/blog/google-summer-of-code-week-4th-and-7th-midterm-evaluation/index.md b/pages/blog/google-summer-of-code-week-4th-and-7th-midterm-evaluation/index.md
index 13b073b8..88b840f7 100644
--- a/pages/blog/google-summer-of-code-week-4th-and-7th-midterm-evaluation/index.md
+++ b/pages/blog/google-summer-of-code-week-4th-and-7th-midterm-evaluation/index.md
@@ -1,84 +1,81 @@
----
-title: "Google Summer of Code- Week 4th & 7th Midterm Evaluation"
-slug: google-summer-of-code-week-4th-and-7th-midterm-evaluation
-date: 2023-07-25
-authors: ["Ankit Kumar"]
-tags: [google summer of code, gsoc, open-source open-sciencelab]
-categories: [open-source, gsoc]
-description: |
-  In this article, I will share the progress for Week 4th week to 7th week for my
-  contribution to Open-science labs as a part of Google Summer of Code 2023.
-thumbnail: "/GSoC-Vertical.png"
----
+# Google Summer of Code- Week 4th & 7th Midterm Evaluation
+Ankit Kumar
+2023-07-25
 
 ## Google Summer of Code- Week 4th & 7th Midterm Evaluation
 
-In this article, I will share the progress for Week 4th week to 7th week for my
-contribution to Open-science labs as a part of Google Summer of Code 2023.
+In this article, I will share the progress for Week 4th week to 7th week
+for my contribution to Open-science labs as a part of Google Summer of
+Code 2023.
 
- <img src="GSoC-Vertical.png" width="400">
+<img src="GSoC-Vertical.png" width="400">
 
-As my Google Summer of Code journey continued, I found myself faced with an
-exciting yet daunting task: implementing a whole new build-system as an option
-for templates in the esteemed Open-Science Lab. This endeavor demanded
-meticulous planning, unwavering dedication, and the exploration of various
-build-systems, including Maturin, Hatchling, Scikit-build, and `pybuild11`.
+As my Google Summer of Code journey continued, I found myself faced with
+an exciting yet daunting task: implementing a whole new build-system as
+an option for templates in the esteemed Open-Science Lab. This endeavor
+demanded meticulous planning, unwavering dedication, and the exploration
+of various build-systems, including Maturin, Hatchling, Scikit-build,
+and `pybuild11`.
 
-In this period, I started working on to add support for `Maturin` build-system.
+In this period, I started working on to add support for `Maturin`
+build-system.
 
 ### Maturin
 
-[**Maturin**]() was the first build-system I explored. Its unique approach of
-building Python bindings for Rust libraries intrigued me, and I wondered if it
-could provide a novel solution to the lab's needs. The seamless blending of
-Python and Rust offered the potential for unparalleled performance and memory
-efficiency in research projects. However, I faced a steep learning curve to
-master the intricacies of Rust and its integration with Python. Overcoming these
-challenges was a significant achievement, and I managed to create a functional
-prototype that demonstrated Maturin's potential to revolutionize the
-Open-Science Lab's workflow. My contribution to this issue is
+[**Maturin**]() was the first build-system I explored. Its unique
+approach of building Python bindings for Rust libraries intrigued me,
+and I wondered if it could provide a novel solution to the lab’s needs.
+The seamless blending of Python and Rust offered the potential for
+unparalleled performance and memory efficiency in research projects.
+However, I faced a steep learning curve to master the intricacies of
+Rust and its integration with Python. Overcoming these challenges was a
+significant achievement, and I managed to create a functional prototype
+that demonstrated Maturin’s potential to revolutionize the Open-Science
+Lab’s workflow. My contribution to this issue is
 [here](https://github.com/osl-incubator/scicookie/pull/152)
 
-After merging this pull request, I started to add support for `Hatchling`
-build-system.
+After merging this pull request, I started to add support for
+`Hatchling` build-system.
 
 ### Hatchling
 
-[**Hatchling**]() known for its user-friendly nature, was my next target. It
-promised to simplify the build and deployment processes, which could be
-particularly beneficial for newcomers to the lab and projects with
-straightforward requirements. Integrating Hatchling into the lab's ecosystem
-required thorough documentation and integration tests to ensure its smooth
-adoption. Overcoming initial hurdles, I was elated to see the positive response
-from the lab's community as they began adopting Hatchling for their projects. My
-contribution to this issue is
-[here](https://github.com/osl-incubator/scicookie/pull/144)
+[**Hatchling**]() known for its user-friendly nature, was my next
+target. It promised to simplify the build and deployment processes,
+which could be particularly beneficial for newcomers to the lab and
+projects with straightforward requirements. Integrating Hatchling into
+the lab’s ecosystem required thorough documentation and integration
+tests to ensure its smooth adoption. Overcoming initial hurdles, I was
+elated to see the positive response from the lab’s community as they
+began adopting Hatchling for their projects. My contribution to this
+issue is [here](https://github.com/osl-incubator/scicookie/pull/144)
 
 After completetion of this issue, I jumped to a task to add support for
 `Scikit-Build-Core`.
 
 ### Scikit-build-core
 
-[**Scikit-build-core**]() a cross-platform build-system, offered a robust option
-for integrating CPython extensions. While challenging to implement, I recognized
-its potential to support projects with complex native code dependencies. My
-experience with Scikit-build exposed me to advanced build and packaging
-concepts, and I was thrilled to see it complementing the existing build-systems
-in the lab, catering to a broader range of projects. My contribution to this
-issue is [here](https://github.com/osl-incubator/scicookie/pull/161)
+[**Scikit-build-core**]() a cross-platform build-system, offered a
+robust option for integrating CPython extensions. While challenging to
+implement, I recognized its potential to support projects with complex
+native code dependencies. My experience with Scikit-build exposed me to
+advanced build and packaging concepts, and I was thrilled to see it
+complementing the existing build-systems in the lab, catering to a
+broader range of projects. My contribution to this issue is
+[here](https://github.com/osl-incubator/scicookie/pull/161)
 
 ### Conclusions
 
 In conclusion, my Google Summer of Code experience with implementing new
-build-systems for the Open-Science Lab was a transformative journey. Overcoming
-hurdles with Maturin, embracing user-friendliness with Hatchling, exploring the
-potential of Scikit-build.I realized the importance of innovation and
-adaptability in the world of open-source development. This experience has not
-only enriched my technical skills but also instilled in me a passion for
-contributing to projects that drive positive change in the world of scientific
-research. As I look to the future, I am excited to continue this journey,
-collaborating with the open-source community to create solutions that empower
-researchers and advance the boundaries of knowledge.
+build-systems for the Open-Science Lab was a transformative journey.
+Overcoming hurdles with Maturin, embracing user-friendliness with
+Hatchling, exploring the potential of Scikit-build.I realized the
+importance of innovation and adaptability in the world of open-source
+development. This experience has not only enriched my technical skills
+but also instilled in me a passion for contributing to projects that
+drive positive change in the world of scientific research. As I look to
+the future, I am excited to continue this journey, collaborating with
+the open-source community to create solutions that empower researchers
+and advance the boundaries of knowledge.
 
 You can read my previous blog [here](https://medium.com/@ayeankit)
 
diff --git a/pages/blog/open-science-labs-participating-google-summer-of-code-2025-mentoring-organization/index.md b/pages/blog/open-science-labs-participating-google-summer-of-code-2025-mentoring-organization/index.md
index 3b934fde..fb8eee67 100644
--- a/pages/blog/open-science-labs-participating-google-summer-of-code-2025-mentoring-organization/index.md
+++ b/pages/blog/open-science-labs-participating-google-summer-of-code-2025-mentoring-organization/index.md
@@ -1,40 +1,52 @@
----
-title: "Open Science Labs is participating in the Google Summer of Code 2025 as a Mentoring Organization!"
-slug: open-science-labs-participating-google-summer-of-code-2025-mentoring-organization
-date: 2025-03-01
-authors: ["Open Science Labs Team"]
-tags: [google summer of code, gsoc, open-source, open-science]
-categories: [open-source, gsoc]
-description: |
-  Open Science Labs (OSL) is participating as a mentoring organization in Google Summer of Code (GSoC) 2025 for the first time. Students and newcomers can join open-source projects, connect with mentors, and apply via the GSoC website. Visit the official page of OSL or Discord for details.
-thumbnail: "/gsoc_osl.png"
----
+# Open Science Labs is participating in the Google Summer of Code 2025
+as a Mentoring Organization!
+Open Science Labs Team
+2025-03-01
 
 ## Open Science Labs is participating in the Google Summer of Code 2025 as a Mentoring Organization!
 
 ![Google Summer of Code 2025 with Open Science Labs](gsoc_osl.png)
 
-We are thrilled to announce that Open Science Labs (OSL) has been selected as one of the 185 mentoring organizations for Google Summer of Code (GSoC) 2025. This is an exceptional opportunity for our community, our projects and sub-organizations, and new contributors to engage in open source software development. As an independent organization participating for the first time in GSoC, we are thrilled to welcome students and newcomers to collaborate on meaningful projects under the guidance of experienced mentors.
+We are thrilled to announce that Open Science Labs (OSL) has been
+selected as one of the 185 mentoring organizations for Google Summer of
+Code (GSoC) 2025. This is an exceptional opportunity for our community,
+our projects and sub-organizations, and new contributors to engage in
+open source software development. As an independent organization
+participating for the first time in GSoC, we are thrilled to welcome
+students and newcomers to collaborate on meaningful projects under the
+guidance of experienced mentors.
 
 ### Participating Projects and Sub-Organizations
 
-You can check it in the [Open Science Labs Official page](https://opensciencelabs.org/opportunities/gsoc/project-ideas/), where each organization has its own set of project ideas and mentors. Feel free to reach out to the mentors directly for inquiries or join our [Discord server](https://opensciencelabs.org/discord) for discussions.
+You can check it in the [Open Science Labs Official
+page](https://opensciencelabs.org/opportunities/gsoc/project-ideas/),
+where each organization has its own set of project ideas and mentors.
+Feel free to reach out to the mentors directly for inquiries or join our
+[Discord server](https://opensciencelabs.org/discord) for discussions.
 
 ### How to Participate
 
 #### For Students and Contributors
 
-If you are a student or newcomer eager to contribute to open source projects, here is how you can get involved:
+If you are a student or newcomer eager to contribute to open source
+projects, here is how you can get involved:
 
-1. Explore Project Ideas: Check out the list [here](https://opensciencelabs.org/opportunities/gsoc/project-ideas/).
-2. Introduce Yourself: Reach out to the organization or project mentors you are interested in working with.
-3. Review Guidelines: Read our Contributor Guide and the official GSoC [Student Instructions](https://summerofcode.withgoogle.com/).
-4. Apply: Submit your application through the GSoC website once the application period opens.
+1.  Explore Project Ideas: Check out the list
+    [here](https://opensciencelabs.org/opportunities/gsoc/project-ideas/).
+2.  Introduce Yourself: Reach out to the organization or project mentors
+    you are interested in working with.
+3.  Review Guidelines: Read our Contributor Guide and the official GSoC
+    [Student Instructions](https://summerofcode.withgoogle.com/).
+4.  Apply: Submit your application through the GSoC website once the
+    application period opens.
 
-For the latest project ideas and detailed submission guidelines, check out our official page or other communication channels.
+For the latest project ideas and detailed submission guidelines, check
+out our official page or other communication channels.
 
 ### Get Involved!
 
 - **For inquiries**: Email us at <team@opensciencelabs.org>.
-- **Join the conversation**: Connect with us on [Discord](https://opensciencelabs.org/discord).
-- **Learn more about GSoC**: Visit the official [GSoC website](https://summerofcode.withgoogle.com/).
+- **Join the conversation**: Connect with us on
+  [Discord](https://opensciencelabs.org/discord).
+- **Learn more about GSoC**: Visit the official [GSoC
+  website](https://summerofcode.withgoogle.com/).
diff --git a/pages/blog/osl-2-0/index.md b/pages/blog/osl-2-0/index.md
index 6d39510f..a59832b0 100644
--- a/pages/blog/osl-2-0/index.md
+++ b/pages/blog/osl-2-0/index.md
@@ -1,102 +1,98 @@
----
-title: "OSL 2.0"
-slug: osl-2-0
-date: 2026-01-19
-authors: ["Ivan Ogasawara"]
-tags: [osl]
-categories: [osl]
-description: |
-  OSL 2.0 is a new chapter—and an open invitation. If you believe in Growth, Collaboration, and Impact, there's a place for you here: to learn in public, contribute to real projects, and grow into a leader who helps others do the same. Whether you're a student, a researcher, a maintainer, or simply someone who cares about open source and open science, we'd love to meet you. Read our mission, join the conversation, and take your first step with us—one small contribution can become a life-changing journey.
-thumbnail: "/header.png"
----
+# OSL 2.0
+Ivan Ogasawara
+2026-01-19
 
 ## OSL 2.0
 
-Open Science Labs (OSL) was born in 2015, when I was working at a transportation
-engineering lab. The idea was simple: help researchers bring open science into
-their daily work.
+Open Science Labs (OSL) was born in 2015, when I was working at a
+transportation engineering lab. The idea was simple: help researchers
+bring open science into their daily work.
 
-After a few months, life took me in other directions, and OSL went on pause.
+After a few months, life took me in other directions, and OSL went on
+pause.
 
-In 2018, a few friends were looking for their first jobs in tech. I decided to
-reactivate OSL (back then called _Open Data Science Labs_) to support them with
-mentoring and internships, and to connect them to open source projects in
-research settings.
+In 2018, a few friends were looking for their first jobs in tech. I
+decided to reactivate OSL (back then called *Open Data Science Labs*) to
+support them with mentoring and internships, and to connect them to open
+source projects in research settings.
 
-Through this initiative, my friends **Sandro Loch** and **Elton Santana**
-started contributing to a scientific project I had previously worked on:
-**Alerta Dengue**, led by professor **Flavio Coelho**. A few months later, both
-of them were hired.
+Through this initiative, my friends **Sandro Loch** and **Elton
+Santana** started contributing to a scientific project I had previously
+worked on: **Alerta Dengue**, led by professor **Flavio Coelho**. A few
+months later, both of them were hired.
 
-That was the real beginning of OSL. It matched what moves me most: helping
-people grow while helping open source projects move forward.
+That was the real beginning of OSL. It matched what moves me most:
+helping people grow while helping open source projects move forward.
 
----
+------------------------------------------------------------------------
 
 ### Growing together
 
 From there, OSL started many kinds of activities: mentoring, open source
 incubation, internships, translations, webinars, and more.
 
-We received support from wonderful people and friends like **Francisco Palm**,
-**Mariangela Petrizzo**, **Ever Vino**, **Eunice Rodas**, **Luis Gago**,
-**Agustina Pesce**, **Sandro Loch**, and many others.
+We received support from wonderful people and friends like **Francisco
+Palm**, **Mariangela Petrizzo**, **Ever Vino**, **Eunice Rodas**, **Luis
+Gago**, **Agustina Pesce**, **Sandro Loch**, and many others.
 
-New interns joined too, such as **Luã Bida**, **Anavelyz Perez**, and **Yurely
-Camacho**, who helped keep many internal projects moving. Later, Anavelyz also
-helped coordinate our activities related to **Google Summer of Code (GSoC)**.
+New interns joined too, such as **Luã Bida**, **Anavelyz Perez**, and
+**Yurely Camacho**, who helped keep many internal projects moving.
+Later, Anavelyz also helped coordinate our activities related to
+**Google Summer of Code (GSoC)**.
 
-And speaking of GSoC, we are deeply grateful to **Gagandeep Singh** for his
-guidance and support over the years.
+And speaking of GSoC, we are deeply grateful to **Gagandeep Singh** for
+his guidance and support over the years.
 
----
+------------------------------------------------------------------------
 
 ### Our partners along the way
 
-OSL also received direct and indirect support from several partners, including:
-**Alerta Dengue**, **The GRAPH Network**, **The GRAPH Courses**, **pyOpenSci**,
-**LiteRev**, and **IGDORE**.
+OSL also received direct and indirect support from several partners,
+including: **Alerta Dengue**, **The GRAPH Network**, **The GRAPH
+Courses**, **pyOpenSci**, **LiteRev**, and **IGDORE**.
 
-A big thank you to **Olivia Keiser**, **Sara Botero**, **Flavio Coelho**,
-**Aziza**, **Erol Orel**, and many others for the opportunities and trust.
+A big thank you to **Olivia Keiser**, **Sara Botero**, **Flavio
+Coelho**, **Aziza**, **Erol Orel**, and many others for the
+opportunities and trust.
 
-We are also very grateful to the **Python Software Foundation**, which supported
-us with three grants to help maintain three affiliated projects: **SciCookie**,
-**Makim**, and **ASTx**.
+We are also very grateful to the **Python Software Foundation**, which
+supported us with three grants to help maintain three affiliated
+projects: **SciCookie**, **Makim**, and **ASTx**.
 
-These grants allowed us to hire amazing former interns like **Anavelyz**,
-**Yurely**, **Abhijeet**, and **Ana Paula**.
+These grants allowed us to hire amazing former interns like
+**Anavelyz**, **Yurely**, **Abhijeet**, and **Ana Paula**.
 
----
+------------------------------------------------------------------------
 
 ### The game changer: Google Summer of Code
 
-A big turning point for our community was joining the **Google Summer of Code**
-program.
+A big turning point for our community was joining the **Google Summer of
+Code** program.
 
-In the first two years, we joined GSoC under the umbrella of **NumFOCUS**, who
-opened the doors for us. Later, in 2025, OSL was accepted as an official **GSoC
-Mentoring Organization**.
+In the first two years, we joined GSoC under the umbrella of
+**NumFOCUS**, who opened the doors for us. Later, in 2025, OSL was
+accepted as an official **GSoC Mentoring Organization**.
 
-GSoC put us “on the map” for newcomers, which has always been one of our main
-audiences. Many new people started reaching out to participate in GSoC with OSL.
-This was beautiful—but also challenging.
+GSoC put us “on the map” for newcomers, which has always been one of our
+main audiences. Many new people started reaching out to participate in
+GSoC with OSL. This was beautiful—but also challenging.
 
-We were not fully prepared for such a large number of candidates. It was hard to
-manage, and we learned a lot in the process.
+We were not fully prepared for such a large number of candidates. It was
+hard to manage, and we learned a lot in the process.
 
-GSoC 2026 has not yet been announced, and we are already receiving messages from
-new candidates. This is one of the reasons we felt the need to pause, look at
-ourselves, and clarify our mission, motivation, and purpose.
+GSoC 2026 has not yet been announced, and we are already receiving
+messages from new candidates. This is one of the reasons we felt the
+need to pause, look at ourselves, and clarify our mission, motivation,
+and purpose.
 
-We want to make these clear and public so that people join us because they
-connect with our values, not only because of GSoC. Otherwise, many might feel
-disappointed, since only a few can be selected each year.
+We want to make these clear and public so that people join us because
+they connect with our values, not only because of GSoC. Otherwise, many
+might feel disappointed, since only a few can be selected each year.
 
-You can read more about our mission, motivation, and purpose [here](/about).
-Below is a short summary.
+You can read more about our mission, motivation, and purpose
+[here](./about). Below is a short summary.
 
----
+------------------------------------------------------------------------
 
 ### Our core: Growth, Collaboration, Impact
 
@@ -106,54 +102,56 @@ The three core values that represent our community are:
 - **Collaboration**
 - **Impact**
 
-We are building a community where anyone who shares these values has a space to:
+We are building a community where anyone who shares these values has a
+space to:
 
 - Learn and grow
 - Contribute to real projects
 - Create a positive impact in the world
 
-We truly believe that open source is a powerful way to connect people who want
-experience with maintainers who need contributors.
+We truly believe that open source is a powerful way to connect people
+who want experience with maintainers who need contributors.
 
-Today, only a small fraction of students manage to work in the field they
-studied after finishing university. That's the gap OSL is trying to help fill.
+Today, only a small fraction of students manage to work in the field
+they studied after finishing university. That’s the gap OSL is trying to
+help fill.
 
----
+------------------------------------------------------------------------
 
-### We don't want followers, we want leaders
+### We don’t want followers, we want leaders
 
 The focus of OSL is not to create followers, but to help people become
 **leaders**.
 
-We want people in our community who feel our projects as **their** projects,
-with the same love and passion that we put into them.
+We want people in our community who feel our projects as **their**
+projects, with the same love and passion that we put into them.
 
-Of course, each person grows at their own pace. It can take time to understand
-the architecture, roadmap, and purpose of a project. It can also take time
-before you feel confident to contribute independently or receive an invitation
-to become a maintainer.
+Of course, each person grows at their own pace. It can take time to
+understand the architecture, roadmap, and purpose of a project. It can
+also take time before you feel confident to contribute independently or
+receive an invitation to become a maintainer.
 
-That's normal. Don't give up.
+That’s normal. Don’t give up.
 
 Keep moving forward. Ask for feedback. Use every step to grow.
 
-As **Jim Kwik** says in his _Super Brain_ course:
+As **Jim Kwik** says in his *Super Brain* course:
 
-> “Practice doesn't make perfect. Practice makes progress.”
+> “Practice doesn’t make perfect. Practice makes progress.”
 
----
+------------------------------------------------------------------------
 
 ### Thank you 💚
 
-Before closing, I want to say a special thank you to some amazing collaborators
-who have helped us more actively in different projects and initiatives: **Sandro
-Loch**, **Ever Vino**, **Felipe Paes**, **Satarupa Deb**, **Yuvi Mittal**,
-**Aniket Kumar**, **Abhijeet**, and all our interns, mentors, former steering
-council members, and partners.
+Before closing, I want to say a special thank you to some amazing
+collaborators who have helped us more actively in different projects and
+initiatives: **Sandro Loch**, **Ever Vino**, **Felipe Paes**, **Satarupa
+Deb**, **Yuvi Mittal**, **Aniket Kumar**, **Abhijeet**, and all our
+interns, mentors, former steering council members, and partners.
 
-Thank you all for being part of our lives and our journey. Together, we are
-building a welcoming place where people can grow, contribute, and make a real
-difference.
+Thank you all for being part of our lives and our journey. Together, we
+are building a welcoming place where people can grow, contribute, and
+make a real difference.
 
-OSL 2.0 is not just a new phase of a project. It is a new chapter in a community
-of people who care.
+OSL 2.0 is not just a new phase of a project. It is a new chapter in a
+community of people who care.

[Shivampal157]

@xmnlab, the PR still shows 1 requested change and the main/build check failing. I’ll address the requested change once I see it. for the failing build, could you share the latest build log (or the failing step’s error) so I can fix it?

[xmnlab]

the current issue in the ci is because it builds the content inside the ci and check if the changes are already inside your branch, if it is already there, it means you have pushed the content rendered, which is what is expected. if it check that there are any new changes, it means that you didn't pushed the rendered version. and that is why it is failing.

but in this specific case, your solution is removing the metadata header, which is not correct, so you need to fix that first before pushing the rendered md files

[Shivampal157]

Hi @xmnlab, I’ve added _quarto.yml for GFM YAML preservation, kept the inject script as a fallback, and pushed the synced rendered blog index.md files (commit 866059f). The main / build check is still failing. Could you share the build log or the error from the failing step? I’d also like to address the “1 requested change” - could you point me to that comment so I can fix it?