ReadMe for the swob Blog

README.md

@@ -1,4 +1,85 @@
-## Smswithoutborders Blog
+# Smswithoutborders Blog
 
-SMSWithoutBorders(Relay sms) Official Blog Feed.
-[smswithoutborders](https://smswithoutborders.com)
+Welcome to the SMSWithoutBorders Blog repository! This blog serves as a platform to share updates, new features, and ongoing projects related to SMSWithoutBorders. We encourage contributions from anyone interested in our project and its mission.
+
+## About SMSWithoutBorders
+
+SMSWithoutBorders is an open-source project aimed at providing relay SMS services. Our mission is to [insert mission statement here]. To learn more about SMSWithoutBorders, visit our website.[https://smswithoutborders.com/](https://smswithoutborders.com/)
+
+### Want to Contribute??
+
+Here's how you can contribute:
+
+- Cloning the Repository
+
+Clone the repository to your local machine:
+
+```bash
+git clone https://github.com/smswithoutborders/blog/tree/main
+```
+
+- Navigate to the project directory:
+
+```bash
+
+    cd blog
+```
+
+- Setting Up Locally
+
+Ensure you have Node.js installed on your machine.
+
+- Install dependencies using PNPM:
+
+```bash
+    pnpm install
+```
+
+- Making Changes
+
+- Create a new branch for your changes:
+
+```bash
+git checkout -b feature/your-feature-name
+```
+
+After making changes, add and commit them:
+
+```bash
+    git add .
+    git commit -m "Add your commit message here"
+```
+
+- Testing Locally
+
+  Once you've made your changes, run the blog locally to test them:
+
+```bash
+    pnpm run dev
+```
+
+This will start a development server, and you can view the blog at [http://localhost:3000](http://localhost:3000). Verify that your changes look and function as expected.
+
+### Submitting a Pull Request
+
+    Push your changes to your forked repository:
+
+```bash
+    git push origin feature/your-feature-name
+```
+
+    Go to the repository on GitHub and create a pull request from your branch to the main branch.
+
+    Provide a clear description of your changes in the pull request, and wait for the review and feedback from the maintainers.
+
+#### Deployment
+
+Our blog is automatically deployed when changes are merged into the main branch. Once your pull request is approved and merged, your changes will be live on our blog!
+
+### Get in Touch
+
+If you have any questions or need assistance with contributing, or think we can change something on the blog layout or anything, feel free to open an issue in this repository.
+
+# Notes
+
+`smswithoutborders blog` uses [Tailwind CSS](https://tailwindcss.com) [(v3.0)](https://tailwindcss.com/blog/tailwindcss-v3).

_posts/resilience-of-gateway-clients-in-smswithoutborders.md

@@ -12,14 +12,16 @@ ogImage:
 
 ![resilience-flow](/posts/resilience-flow.png)
 
-By default, these clients have relied solely on HTTPS for routing SMS messages to online platforms. This update introduces support for additional protocols, including AMQP, FTP, and SMTP, providing greater flexibility and resilience in message delivery.
+SMSWithoutBorders is pleased to announce a significant advancement in message-forwarding functionalities for its gateway clients. By default, these clients have relied solely on HTTPS for routing SMS messages to online platforms. This update introduces support for additional protocols, including AMQP, FTP, and SMTP, providing greater flexibility and resilience in message delivery.
 
 ### Breaking Down the Update: Multi-Protocol Support using the Round-Robin algorithm
 
-The decision to diversify protocol support stems from the need to address potential disruptions that may occur with the messaging protocols. By incorporating multiple protocols such as AMQPS (Advanced Message Queuing Protocol), FTP (File Transfer Protocol), and SMTP (Simple Mail Transfer Protocol) into the gateway client framework, SMSWithoutBorders is proactively mitigating the risk of message delivery interruptions. Gateway clients can now automatically switch between protocols in case of failures. The Gateway clients publish the data for which protocols are available for use in specific regions.
+The decision to diversify protocol support stems from the need to address potential disruptions that may occur with the messaging protocols. By incorporating multiple protocols such as AMQPS (Advanced Message Queuing Protocol), FTP (File Transfer Protocol), and SMTP (Simple Mail Transfer Protocol) into the gateway client framework, SMSWithoutBorders is proactively mitigating the risk of message delivery interruptions. Gateway clients can now automatically switch between protocols in case of failures. The Gateway clients publish the data for which protocols are available for use in specific regions. The data is publicly available on the [ SMSWithoutBorders resilience dashboard](https://telemetry.smswithoutborders.com/)
 
 ### The Role of Gateway Clients in the Context of Resilience
 
-Gateway clients serve as the key component in facilitating the seamless transfer of messages from SMS to online platforms. Their ability to adapt to varying network conditions and protocol blockages is crucial for ensuring uninterrupted communication flow. With the introduction of multi-protocol support, gateway clients are poised to become even more resilient and reliable in their message-forwarding capabilities
+Gateway clients serve as the key component in facilitating the seamless transfer of messages from SMS to online platforms. Their ability to adapt to varying network conditions and protocol blockages is crucial for ensuring uninterrupted communication flow. With the introduction of multi-protocol support, gateway clients are poised to become even more resilient and reliable in their message-forwarding capabilities.
+
 Any disruption in message forwarding could have significant implications for users relying on SMSWithoutBorders for their message routing needs. By enhancing resilience through multi-protocol support, SMSWithoutBorders is not only safeguarding against potential disruptions but also instilling confidence in its user base.
+
 By enabling multiple protocols, SMSWithoutBorders is proactively addressing potential challenges and ensuring uninterrupted message forwarding for its users. As we move forward, these advancements will continue to shape the landscape of SMS-based communication, empowering users to stay connected in an ever-changing digital environment.