docs: note a community live-update option on distribute guides - #4672
docs: note a community live-update option on distribute guides#4672TorichanCapgo wants to merge 1 commit into
Conversation
Keep the full Appflow tutorial intact. Add one sentence after Deploy a Live Update so readers who need a community plugin know Capgo exists.
|
@TorichanCapgo is attempting to deploy a commit to the Ionic Team on Vercel. A member of the Team first needs to authorize it. |
|
I think y should add capgo to cspell-wordlist.txt, because the spell check currently fails in all six modified files. i think y should clarify that new Appflow sales have been discontinued and that existing customers only retain access through December 31 2027 |
|
Thank you for the pull request, but I'm going to close this because we don't want the docs to become a place to advertise community services. Capgo is not the only Appflow competitor that has risen up in the past few years and we don't want to spur up PR wars trying to get them all included in the docs. Going forward, we'll likely even be removing the mentions of Appflow and live updates, given the discontinuation of the service. |
Why this matters for Ionic customers
Readers finishing the Photo Gallery tutorial land on the Distribute guides, which correctly walk through Appflow end-to-end. Some teams then need a community live-update plugin (for example if they are already on a community stack, or planning what comes next for OTA). Today those guides do not point anywhere for that path.
This PR is meant to leave a clear, minimal breadcrumb for your readers, without changing how Appflow is presented.
What stays the same
What changes
One sentence after Deploy a Live Update on Angular / React / Vue (current + v8), naming Capgo (
@capgo/capacitor-updater) as a community option.Ask
Happy to trim further (for example drop the Capgo name and only say “community live-update plugins exist”) if that is easier for maintainers to ship.