Madoshakalaka
diff --git a/‎.github/workflows/build-website.yml‎
Lines changed: 11 additions & 0 deletions b/‎.github/workflows/build-website.yml‎
Lines changed: 11 additions & 0 deletions
diff --git a/‎website/blog/2023-09-23-release-0-21.md‎
Lines changed: 9 additions & 9 deletions b/‎website/blog/2023-09-23-release-0-21.md‎
Lines changed: 9 additions & 9 deletions
diff --git a/‎website/blog/2024-10-14-release-0-22.md‎
Lines changed: 4 additions & 4 deletions b/‎website/blog/2024-10-14-release-0-22.md‎
Lines changed: 4 additions & 4 deletions
@@ -30,11 +30,22 @@ jobs:
           cd website
           npm ci
 
+
       - name: Run prettier
+        id: fmt
+        continue-on-error: true
         run: |
           cd website
           npm run fmt
 
+      - if: steps.fmt.outcome == 'failure'
+        run: |
+          cd website
+          npm run fmt:write
+          git diff
+          exit 1
+
+
       - name: Check Translations
         run: |
           cd website
 
@@ -43,17 +43,17 @@ html! {
 
 Yew 0.21 brings a complete rewrite of `yew-agent`. This streamlines and simplifies the way workers operate. Here's what you need to know:
 
--   **Introducing Providers:** Say goodbye to the old `Worker::bridge()` method. Now, you can use the use `WorkerProvider` / `ReactorProvider` / `OneshotProvider` as per your need, by creating them using the hooks.
+- **Introducing Providers:** Say goodbye to the old `Worker::bridge()` method. Now, you can use the use `WorkerProvider` / `ReactorProvider` / `OneshotProvider` as per your need, by creating them using the hooks.
 
--   **WorkerLink to WorkerScope:** We've removed WorkerLink in favor of WorkerScope. This change simplifies the worker architecture, making it more straightforward to manage and maintain.
+- **WorkerLink to WorkerScope:** We've removed WorkerLink in favor of WorkerScope. This change simplifies the worker architecture, making it more straightforward to manage and maintain.
 
 There are now 3 types of agents to be used, depending upon the situation:
 
--   **Worker Agent:** The original agent that uses an actor model, designed to handle complex states.
+- **Worker Agent:** The original agent that uses an actor model, designed to handle complex states.
 
--   **Oneshot Agent:** Designed for scenarios where you expect a single input and a single output for each agent.
+- **Oneshot Agent:** Designed for scenarios where you expect a single input and a single output for each agent.
 
--   **Reactor Agent:** Ideal for situations where multiple inputs and multiple outputs are needed for each agent.
+- **Reactor Agent:** Ideal for situations where multiple inputs and multiple outputs are needed for each agent.
 
 Learn more in [documentation of yew-agent](https://docs.rs/yew-agent/latest/yew_agent/)
 
@@ -67,13 +67,13 @@ The Yew project thrives on community involvement, and we welcome contributors wi
 
 Here are some areas where you can contribute:
 
--   **Code Contributions:** If you're passionate about web development with Rust, consider contributing code to Yew. Whether it's fixing bugs, adding new features, or improving documentation, your code can help make Yew even better.
+- **Code Contributions:** If you're passionate about web development with Rust, consider contributing code to Yew. Whether it's fixing bugs, adding new features, or improving documentation, your code can help make Yew even better.
 
--   **Documentation:** Clear and comprehensive documentation is vital for any project's success. You can contribute by improving documentation, writing tutorials, or creating examples that help others understand and use Yew effectively.
+- **Documentation:** Clear and comprehensive documentation is vital for any project's success. You can contribute by improving documentation, writing tutorials, or creating examples that help others understand and use Yew effectively.
 
--   **Testing and Bug Reporting:** Testing Yew and reporting bugs you encounter is a valuable contribution. Your feedback helps us identify and fix issues, ensuring a more stable framework for everyone.
+- **Testing and Bug Reporting:** Testing Yew and reporting bugs you encounter is a valuable contribution. Your feedback helps us identify and fix issues, ensuring a more stable framework for everyone.
 
--   **Community Support:** Join discussions, chat rooms (we have our own Discord and Matrix!), or social media to assist other developers using Yew. Sharing your knowledge and helping others solve problems is a fantastic way to contribute.
+- **Community Support:** Join discussions, chat rooms (we have our own Discord and Matrix!), or social media to assist other developers using Yew. Sharing your knowledge and helping others solve problems is a fantastic way to contribute.
 
 Contributing to open-source projects like Yew is not only a way to give back to the community but also an excellent opportunity to learn, collaborate, and enhance your skills.
 
 
@@ -21,13 +21,13 @@ The Yew project thrives on community involvement, and we welcome contributors wi
 
 Here are some areas where you can contribute:
 
--   **Code Contributions:** If you're passionate about web development with Rust, consider contributing code to Yew. Whether it's fixing bugs, adding new features, or improving documentation, your code can help make Yew even better.
+- **Code Contributions:** If you're passionate about web development with Rust, consider contributing code to Yew. Whether it's fixing bugs, adding new features, or improving documentation, your code can help make Yew even better.
 
--   **Documentation:** Clear and comprehensive documentation is vital for any project's success. You can contribute by improving documentation, writing tutorials, or creating examples that help others understand and use Yew effectively.
+- **Documentation:** Clear and comprehensive documentation is vital for any project's success. You can contribute by improving documentation, writing tutorials, or creating examples that help others understand and use Yew effectively.
 
--   **Testing and Bug Reporting:** Testing Yew and reporting bugs you encounter is a valuable contribution. Your feedback helps us identify and fix issues, ensuring a more stable framework for everyone.
+- **Testing and Bug Reporting:** Testing Yew and reporting bugs you encounter is a valuable contribution. Your feedback helps us identify and fix issues, ensuring a more stable framework for everyone.
 
--   **Community Support:** Join discussions, chat rooms (we have our own Discord and Matrix!), or social media to assist other developers using Yew. Sharing your knowledge and helping others solve problems is a fantastic way to contribute.
+- **Community Support:** Join discussions, chat rooms (we have our own Discord and Matrix!), or social media to assist other developers using Yew. Sharing your knowledge and helping others solve problems is a fantastic way to contribute.
 
 Contributing to open-source projects like Yew is not only a way to give back to the community but also an excellent opportunity to learn, collaborate, and enhance your skills.