1 result found

1. Retrieve references/usages of local (inline) blocks

   For shared blocks and other content types, we can already query Optimizely Graph to find every instance of a given type. For example:

   query FindByType {
   _Content(where: { _metadata: { types: { in: ["<ContentTypeName>"] } } }) {
   total
   items {
   _metadata { key displayName types url { default } }
   }
   }
   }

   This works because shared blocks are standalone content items with their own key/ContentLink, so they're indexed and queryable like any other content type.

   Local (inline) blocks don't support this. Since they're stored as embedded property data on the parent content item rather than as standalone content items with their own identity, the same _Content query (or any equivalent Content Management API call) can't return them — there's no way to enumerate all pages/content items that contain a given inline block type or instance.

   Why it matters: Without this, tracking usage of local blocks for impact analysis (e.g., "what breaks if I change this block's schema"), content audits, or migration/cleanup work requires manual searching or custom indexing outside the API — something that's already solved for shared content.

   Ask: Extend Optimizely Graph / the Content Management API so inline block types and instances can be queried the same way shared block types are — e.g., returning the parent content items that contain a given inline block type, with enough metadata (parent key, property name, URL) to locate each usage.

   For shared blocks and other content types, we can already query Optimizely Graph to find every instance of a given type. For example:

   query FindByType {
   _Content(where: { _metadata: { types: { in: ["<ContentTypeName>"] } } }) {
   total
   items {
   _metadata { key displayName types url { default } }
   }
   }
   }

   This works because shared blocks are standalone content items with their own key/ContentLink, so they're indexed and queryable like any other content type.

   Local (inline) blocks don't support this. Since they're stored as embedded property data on the parent content item rather than as standalone content… more

   6 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  Graph  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating