fix: fix mentions

riderx · riderx · commit ec638a5ff7ec · 2025-03-24T12:58:42.000Z
diff --git a/src/content/blog/en/capacitor-ota-updates-app-store-approval-guide.md b/src/content/blog/en/capacitor-ota-updates-app-store-approval-guide.md
@@ -105,7 +105,7 @@ Create update interfaces that are easy to use and non-disruptive:
 -   Enable **background downloads** with progress indicators.
 -   Allow users to decide when to install updates, except for critical security patches.
 
-Forced updates should only be used for critical security fixes, and they must clearly communicate the urgency [\[3\]](https://capawesome.io/blog/how-live-updates-for-capacitor-work/). These steps help reduce rejection risks caused by intrusive update prompts.
+Forced updates should only be used for critical security fixes, and they must clearly communicate the urgency [\[3\]](/blog/how-live-updates-for-capacitor-work). These steps help reduce rejection risks caused by intrusive update prompts.
 
 ### Update Security Protocol
 
@@ -210,4 +210,4 @@ Rolling out OTA updates for Capacitor apps involves a mix of technical precision
 
 By following the compliance steps discussed earlier, teams can benefit from automated checks that simplify adherence to app store rules. Features like end-to-end encryption and controlled rollouts help address critical security and compliance needs.
 
-With Apple and Google continuously updating policies (like those in sections 2.1-2.3), expect more focus on update frequency and stricter security standards. Stay ahead by preparing for these changes while keeping JavaScript and asset update capabilities intact. Don't forget to document and test thoroughly to meet both platform guidelines and user expectations.
+With Apple and Google continuously updating policies (like those in sections 2.1-2.3), expect more focus on update frequency and stricter security standards. Stay ahead by preparing for these changes while keeping JavaScript and asset update capabilities intact. Don't forget to document and test thoroughly to meet both platform guidelines and user expectations.
diff --git a/src/content/blog/en/capacitor-ota-updates-best-practices-for-performance.md b/src/content/blog/en/capacitor-ota-updates-best-practices-for-performance.md
@@ -85,7 +85,7 @@ Before rolling out updates, thorough testing is essential:
 
 -   Use testing environments that closely replicate production settings.
 -   Record baseline metrics like startup time, memory usage, bandwidth, and battery consumption.
--   Verify fallback mechanisms to ensure the server path resets if an update fails [\[4\]](https://capawesome.io/blog/how-live-updates-for-capacitor-work/).
+-   Verify fallback mechanisms to ensure the server path resets if an update fails [\[4\]](/blog/how-live-updates-for-capacitor-work).
 
 Once performance is stable, check that the updates meet app store regulations.
 
@@ -95,11 +95,11 @@ To avoid issues with app store approvals, follow these platform-specific rules:
 
 **Apple App Store Requirements:**
 
-> "Interpreted code may be downloaded to an Application but only so long as such code: (a) does not change the primary purpose of the Application by providing features or functionality that are inconsistent with the intended and advertised purpose of the Application as submitted to the App Store, (b) does not create a store or storefront for other code or applications, and (c) does not bypass signing, sandbox, or other security features of the OS." [\[4\]](https://capawesome.io/blog/how-live-updates-for-capacitor-work/)
+> "Interpreted code may be downloaded to an Application but only so long as such code: (a) does not change the primary purpose of the Application by providing features or functionality that are inconsistent with the intended and advertised purpose of the Application as submitted to the App Store, (b) does not create a store or storefront for other code or applications, and (c) does not bypass signing, sandbox, or other security features of the OS." [\[4\]](/blog/how-live-updates-for-capacitor-work)
 
 **Google Play Store Guidelines:**
 
-> "This restriction does not apply to code that runs in a virtual machine or an interpreter where either provides indirect access to Android APIs (such as JavaScript in a webview or browser)." [\[4\]](https://capawesome.io/blog/how-live-updates-for-capacitor-work/)
+> "This restriction does not apply to code that runs in a virtual machine or an interpreter where either provides indirect access to Android APIs (such as JavaScript in a webview or browser)." [\[4\]](/blog/how-live-updates-for-capacitor-work)
 
 ### Using [Capgo](https://capgo.app/) for Updates
 
@@ -185,6 +185,6 @@ This highlights the importance of creating a reliable update system that balance
 
 To maximize the efficiency of OTA updates in your Capacitor app, make sure to:
 
--   **Set up encryption**: Use digital signatures to verify updates [\[4\]](https://capawesome.io/blog/how-live-updates-for-capacitor-work/).
+-   **Set up encryption**: Use digital signatures to verify updates [\[4\]](/blog/how-live-updates-for-capacitor-work).
 -   **Streamline update delivery**: Consider tools like Capgo for smooth, background updates.
--   **Prepare fallback systems**: Ensure the app remains functional even if an update fails [\[9\]](https://dzone.com/articles/why-device-firmware-updates-are-critical-to-produc).
+-   **Prepare fallback systems**: Ensure the app remains functional even if an update fails [\[9\]](https://dzone.com/articles/why-device-firmware-updates-are-critical-to-produc).
diff --git a/src/content/blog/en/capacitor-ota-updates-targeting-ios-vs-android.md b/src/content/blog/en/capacitor-ota-updates-targeting-ios-vs-android.md
@@ -175,8 +175,8 @@ Capgo can adjust any JavaScript code, including app and generated code, but it s
 
 ## Conclusion
 
-OTA updates for [Capacitor apps](https://capgo.app/blog/capacitor-comprehensive-guide/) require different approaches for iOS and Android due to platform-specific rules. For iOS, there are stricter controls, such as the file path restriction that limits server paths to "/Library/NoCloud/ionic\_built\_snapshots" [\[2\]](https://capawesome.io/blog/how-live-updates-for-capacitor-work/). Meanwhile, Android allows more freedom, with fewer limitations on virtual machines and interpreters accessing APIs [\[2\]](https://capawesome.io/blog/how-live-updates-for-capacitor-work/). These differences highlight the importance of creating update strategies that align with each platform's framework.
+OTA updates for [Capacitor apps](https://capgo.app/blog/capacitor-comprehensive-guide/) require different approaches for iOS and Android due to platform-specific rules. For iOS, there are stricter controls, such as the file path restriction that limits server paths to "/Library/NoCloud/ionic\_built\_snapshots" [\[2\]](/blog/how-live-updates-for-capacitor-work). Meanwhile, Android allows more freedom, with fewer limitations on virtual machines and interpreters accessing APIs [\[2\]](/blog/how-live-updates-for-capacitor-work). These differences highlight the importance of creating update strategies that align with each platform's framework.
 
 Data from platforms like Capgo demonstrates how effective these strategies can be. Developers have successfully delivered 947.6 million updates across 1,400 production apps, proving the scalability of well-designed update systems [\[1\]](https://capgo.app/). However, success relies heavily on meeting each platform's requirements while maintaining strong security measures.
 
-For example, Apple mandates that interpreted code must not alter an app's core functionality or compromise its security [\[2\]](https://capawesome.io/blog/how-live-updates-for-capacitor-work/). This rule is a clear reminder of the platform-specific guidelines developers must follow to implement OTA updates effectively.
+For example, Apple mandates that interpreted code must not alter an app's core functionality or compromise its security [\[2\]](/blog/how-live-updates-for-capacitor-work). This rule is a clear reminder of the platform-specific guidelines developers must follow to implement OTA updates effectively.
diff --git a/src/content/blog/en/capacitor-ota-updates-version-targeting-explained.md b/src/content/blog/en/capacitor-ota-updates-version-targeting-explained.md
@@ -43,7 +43,7 @@ Here’s what you’ll learn:
 
 Want to learn how to set it up and avoid common mistakes? Keep reading for a step-by-step guide.
 
-## Explore [Capawesome](https://capawesome.io/plugins/)'s Ionic [Capacitor](https://capacitorjs.com/) Live Update Plugin
+## Explore [Capgo](https://capgo.app/plugins/)'s Capacitor [Capacitor](https://capacitorjs.com/) Plugins
 
 ![Capawesome](https://mars-images.imgix.net/seobot/screenshots/capawesome.io-1374c0b85e4621707603b9b4a57465b0-2025-03-14.jpg?auto=compress)
 
@@ -248,4 +248,4 @@ To make the most of version targeting, a solid plan is key for maintaining app c
 
 -   **Set Version Rules**: Define clear constraints to manage update distribution.
 -   **Track Deployments**: Monitor update success rates across various app versions.
--   **Support Legacy Versions**: Keep critical older versions functional while nudging users toward updates.
+-   **Support Legacy Versions**: Keep critical older versions functional while nudging users toward updates.
diff --git a/src/content/blog/en/capacitor-ota-updates-versioning-best-practices.md b/src/content/blog/en/capacitor-ota-updates-versioning-best-practices.md
@@ -218,7 +218,7 @@ When selecting an OTA update tool, make sure it offers:
 -   **End-to-end encryption** to keep updates secure
 -   **CI/CD integration** to align with your workflow
 -   **User assignment** for controlled rollouts
--   **App store compliance** to avoid distribution issues [\[10\]](https://capawesome.io/blog/how-live-updates-for-capacitor-work/)
+-   **App store compliance** to avoid distribution issues [\[10\]](/blog/how-live-updates-for-capacitor-work)
 
 Your choice of OTA update software can have a big impact on your team's efficiency and deployment success. Take time to assess your needs around security, version control, and collaboration to find the best fit for your project.
 
@@ -249,4 +249,4 @@ To enhance your OTA update process, consider these actions:
     Monitor the performance of your updates and how users respond to them. Use this data to refine your deployment approach over time.
     
 
-Future OTA updates should aim to combine fast deployment with a smooth user experience, ensuring both efficiency and satisfaction.
+Future OTA updates should aim to combine fast deployment with a smooth user experience, ensuring both efficiency and satisfaction.
diff --git a/src/content/blog/en/how-to-schedule-ota-updates-for-capacitor-apps.md b/src/content/blog/en/how-to-schedule-ota-updates-for-capacitor-apps.md
@@ -64,7 +64,7 @@ Here are some performance benchmarks [\[1\]](https://capgo.app/):
 -   **API response time**: 434 ms globally
 -   **Update success rate**: 82% worldwide
 
-## Explore [Capawesome](https://capawesome.io/)'s New Ionic [Capacitor](https://capacitorjs.com/) Live Update ...
+## Explore [Capgo](https://capgo.app/plugins/)'s Capacitor [Capacitor](https://capacitorjs.com/) Plugins
 
 ![Capawesome](https://mars-images.imgix.net/seobot/screenshots/capawesome.io-5dcbb99c7c66e0a1d148a9bb4683db23-2025-03-21.jpg?auto=compress)
 
@@ -204,4 +204,4 @@ OTA updates can boost app performance by delivering updates quickly and securely
 -   **Performance Monitoring**: Keep an eye on update success rates and essential metrics to fine-tune the process [\[1\]](https://capgo.app/).
 -   **Rollback Protection**: Set up automated error tracking to enable quick rollbacks if needed [\[1\]](https://capgo.app/).
 
-Since 2022, the landscape of OTA update solutions has grown significantly. For instance, Capgo has managed over 23.5 million updates across 750 production apps [\[1\]](https://capgo.app/). When combined with CI/CD integration and real-time analytics, these practices provide a solid OTA update strategy for your Capacitor app workflow.
+Since 2022, the landscape of OTA update solutions has grown significantly. For instance, Capgo has managed over 23.5 million updates across 750 production apps [\[1\]](https://capgo.app/). When combined with CI/CD integration and real-time analytics, these practices provide a solid OTA update strategy for your Capacitor app workflow.
diff --git a/src/content/blog/en/mobile-app-update-strategies-a-developers-checklist.md b/src/content/blog/en/mobile-app-update-strategies-a-developers-checklist.md
@@ -72,7 +72,7 @@ With a clear roadmap in place, it’s time to select the right tools to streamli
 
 Picking the right tools for your Continuous Integration/Continuous Deployment (CI/CD) pipeline is essential. Popular options like [GitHub Actions](https://docs.github.com/actions), [Bitrise](https://bitrise.io/), and [CircleCI](https://circleci.com/) each have unique benefits. For example, [GitHub Actions](https://docs.github.com/actions) integrates directly with your GitHub repositories, making it a convenient choice for many developers [\[2\]](https://www.poppinslabs.com/blog/mobile-app-ci-cd-pipeline).
 
-For Over-the-Air (OTA) updates, tools like Capacitor allow you to deliver changes directly to users without waiting for app store approvals [\[3\]](https://capawesome.io/blog/how-live-updates-for-capacitor-work/). When choosing an OTA solution, consider these factors:
+For Over-the-Air (OTA) updates, tools like Capacitor allow you to deliver changes directly to users without waiting for app store approvals [\[3\]](/blog/how-live-updates-for-capacitor-work). When choosing an OTA solution, consider these factors:
 
 -   **Deployment speed** to minimize downtime.
 -   **Version control** to manage updates effectively.
@@ -177,4 +177,4 @@ These steps help developers manage updates smoothly while keeping user experienc
 
 > "A structured approach helps in minimizing downtime by automating the update process and ensuring that updates are thoroughly tested before deployment. This approach also enhances user satisfaction by delivering updates that are based on user feedback and are designed to improve the app's performance and functionality" [\[1\]](https://www.nimbleappgenie.com/blogs/mobile-app-development-checklist/)[\[5\]](https://www.netsolutions.com/hub/mobile-app-development/checklist).
 
-Ultimately, effective app updates come down to balancing technical excellence with what users want. By sticking to these strategies and staying committed, developers can keep their apps secure, competitive, and easy to use in a constantly changing digital world.
+Ultimately, effective app updates come down to balancing technical excellence with what users want. By sticking to these strategies and staying committed, developers can keep their apps secure, competitive, and easy to use in a constantly changing digital world.
diff --git a/src/content/blog/en/open-source-vs-proprietary-app-update-solutions.md b/src/content/blog/en/open-source-vs-proprietary-app-update-solutions.md
@@ -63,9 +63,9 @@ These features work seamlessly with modern CI/CD workflows, making app updates m
 
 ### Common Tools and Plugins
 
-The open-source landscape offers trusted tools for app updates. **[Capgo](https://capgo.app/)** stands out as a top choice for live updates in Capacitor apps, offering end-to-end encryption, smooth CI/CD integration, and compliance with app store guidelines.
+The open-source landscape offers trusted tools for app updates. **[Capgo](https://capgo.app/)** stands out as a top choice for live updates in Capacitor apps, offering end-to-end encryption, smooth CI/CD integration, and compliance with app store guidelines. And completely open source.
 
-Another popular option is the **[Capacitor Live Update](https://www.npmjs.com/package/%40capacitor%2Flive-updates) plugin**, which simplifies the process of adding live update functionality [\[2\]](https://www.npmjs.com/package/@capawesome/capacitor-live-update)[\[4\]](https://capawesome.io/blog/announcing-the-capacitor-live-update-plugin/).
+Another popular option is the **[Capacitor Live Update](https://www.npmjs.com/package/%40capacitor%2Flive-updates) plugin**, which simplifies the process of adding live update functionality [\[2\]](https://www.npmjs.com/package/@capawesome/capacitor-live-update)[\[4\]](https://www.npmjs.com/package/@capawesome/capacitor-live-update), open source plugin but no backend.
 
 ### Strengths and Weaknesses
 
@@ -175,9 +175,9 @@ When deciding between open-source and proprietary tools, consider factors like y
 
 ### When Open Source Makes Sense
 
-Open-source tools are a great fit for projects that need flexibility and customization. They’re especially useful for teams looking for tailored integrations and cost-efficient options. The [Capacitor Live Update plugin](https://capgo.app/confirm_email/) is a good example of this approach. As [Capawesome.io](https://capawesome.io/) explains:
+Open-source tools are a great fit for projects that need flexibility and customization. They’re especially useful for teams looking for tailored integrations and cost-efficient options. The [Capacitor Live Update plugin](https://www.npmjs.com/package/@capgo/capacitor-updater/) is a good example of this approach. As [Capgo.app](https://capgo.app/) explains:
 
-> "One of the biggest advantages of Capacitor over other runtimes is the ability to deliver updates in real-time without having to resubmit your app to the app stores" [\[4\]](https://capawesome.io/blog/announcing-the-capacitor-live-update-plugin/).
+> "One of the biggest advantages of Capacitor over other runtimes is the ability to deliver updates in real-time without having to resubmit your app to the app stores" [\[4\]](/blog/open-source).
 
 This option is well-suited for:
 
@@ -211,4 +211,4 @@ For organizations juggling multiple apps or requiring enterprise-level features,
 
 To successfully implement your chosen solution, start by assessing your app's specific requirements. Then, select the tool that aligns best with those needs and integrate it into your CI/CD pipeline while ensuring it complies with relevant platform standards. A smooth implementation will depend on how well your choice matches your team’s technical skills, budget, and capacity for long-term maintenance.
 
-The success of your update solution will largely depend on its ability to meet both current demands and future growth. Whether you opt for open-source tools for their customization options or proprietary platforms for their structured support, make sure your choice complements your development process and adheres to platform guidelines [\[2\]](https://www.npmjs.com/package/@capawesome/capacitor-live-update).
+The success of your update solution will largely depend on its ability to meet both current demands and future growth. Whether you opt for open-source tools for their customization options or proprietary platforms for their structured support, make sure your choice complements your development process and adheres to platform guidelines [\[2\]](https://www.npmjs.com/package/@capawesome/capacitor-live-update).
