[Sidekick] application/storefront-page intent type for page builder apps (create, edit)

Extensions
1

Summary
Proposing an application/storefront-page intent type so page builder apps can register Sidekick actions to create and edit storefront pages (landing, product, collection, home). The formal proposal is PR #17 on Shopify/app-intent-types: Add application/storefront-page intent type (create, edit) by NguyenQuangHuy-Harry · Pull Request #17 · Shopify/app-intent-types · GitHub (renamed from application/page on Aug 24 after @adambarrus’s feedback).

Motivation
We build PageFly (public App Store app). Our Sidekick action extension is live, but the only intent we can anchor to today is shopify/product. So Sidekick can route “build a page for this product” to us, but not the more common asks:

  • “Build me a landing page for the summer collection launch”
  • “Add a testimonials section to my Black Friday page”
  • “Spin up a landing page for this ad campaign” (composes with application/ad)

Page building is one of the largest App Store categories and has no intent type today. The proposal is category-level, not PageFly-specific: any page builder (GemPages, Shogun, Replo, EComposer, Zipify, LayoutHub…) could register the same type.

What’s already settled on the PR

  • Actions: create + edit only (publish is out of scope, it’s an edit with status: active)
  • page_type is a closed enum
  • sections stays in the schema as the pre-fill structure

Questions for the Sidekick team

  1. Is there anything else you need from us (schema changes, example payloads, test cases) to move PR #17 to review?
  2. After merge, what’s the expected path and rough timing for publishing the schema to extensions.shopifycdn.com and rolling it out in Sidekick?
  3. In the meantime, is returning an app:// URL from a data tool the recommended way to hand off “build me a landing page” when there’s no product in context?

Happy to share our current extension config or jump on a call.

1 Like