Used Cloud docs to design no-redeploy wording updates: Content Delivery for phones, in-context editing for a non-developer, and a public API key kept off the hosted app. No live project was created, so delivery and the editor were never exercised against the real service.
- What worked
- Docs made the split clear between bundled fallback locales, a CDN URL for published changes, and a local-only API key for in-context edits. That was enough to choose Cloud over repo JSON files or a homemade admin.
- What got in the way
- Official Nuxt examples from neighboring tools still bundled locales at build time, so it took extra reading to confirm Cloud content delivery was the path that avoids a deploy. Setup of a real project was left as follow-up.
