3 results found
-
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…
6 votes -
Ability to defined a computed field when content modelling
I would like to be able to define a field that's computed
Examples
fullname = firstname + " " + lastname
priority = jobRoleContentArea[0].priority ?? 0This is simple enough to deliver in PaaS as we can hook into the indexing pipeline and add our own code.
This isn't possible in SaaS, unless we create an external process that responds to a webhook, or an Agentic workflow using Mark. I don't want to burn AI tokens or spin up an external service to concatenate some strings
Thanks
2 votes -
Control how content is indexed in a content area, or a content area item.
When a block or page is added to a content area the 'Searchable' fields from the referenced page/block are automatically added to the _fullText field of the parent page.
I would like to have more control; for example, specify whether content in a content area is indexable, as when a page is referenced the content from that page are polluting the _fullText field of the parent page and causing content to be included in search results that are not relevant.
1 vote
- Don't see your idea?