Search
A search interface with faceted filtering. Contains a child listing block for results and typed facets (checkbox, select, date range, toggle) for filtering.

Search with Facets
Filter by
Docs
A design-system-first page-builder toolkit for any CMS. Guides for building a frontend, deploying and securing Inka, editing content, testing, adapters, and rules.
Templates
Layout and block templates
CMS adapter guide
Connect Inka to a content store through one adapter contract — the same experience for editors whatever sits behind it.
How Inka Works
Inka is the page-building and governance layer between your CMS and your front ends. Content stays in the CMS, rules come from your design system, and front ends in any framework render the result. Editing is private; publishing is public.
Rules and checks
The rules your front end sets are applied while people edit, from blocked saves to advice beside a field. Inka Assure, in development, will keep the record of what was checked and signed off.
Deploy and secure Inka
What to run, where to put it on your network, how editors' logins reach the front end, and the settings that keep editing private.
Simple Search
Site Footer
Footer with social links and copyright
Adding and moving blocks
The block chooser, slash menu, and drag handles are part of Inka and look the same everywhere. What you can pick from those choosers — the list of block types — comes from your site's design system. One site might offer "Lead paragraph", "Pull quote", "Stat highlight"; another might just have "Text" and "Image". Mechanic is identical.
Containers
A container block holds other blocks inside it — sliders, columns, accordions, grids, generic sections. The blocks inside are called its children. Containers can be nested (a column inside a row inside a section).
Editing text
Click into any text in the preview that's marked inline-editable and start typing. There are two kinds of text fields: simple text (like a title) and slate (rich text — the body of a paragraph block, descriptions, etc.).
Links and media
The link picker, image picker, and upload dialog are part of Inka's chrome — they look the same on every site. What varies by design system is which links and images are click-to-edit in the preview: a site might wire up every link inline, or only a few "primary" links, with everything else editable from the sidebar. Same applies to images.
Selecting blocks
The editor has two modes when a block is selected: text mode (you're editing inside the block) and block mode (the whole block is selected as a unit).
Developer Reference
Schema
Pass this object inside the blocks option when calling initBridge() to register this block type with the admin UI. See Custom Blocks for the full setup guide.
search: {
id: 'search',
title: 'Search',
group: 'common',
blockSchema: {
properties: {
variation: { title: 'Variation' },
query: { title: 'Query', widget: 'querystring' },
listingBodyTemplate: { title: 'Results template' },
showSearchInput: { title: 'Show search input', type: 'boolean' },
showSortOn: { title: 'Show sort on', type: 'boolean' },
showTotalResults: { title: 'Show total results', type: 'boolean' },
sortOnOptions: { title: 'Sort on options', type: 'array' },
facets: {
// Typed sub-items: each facet's `type` names its own block type,
// so the item is edited with THAT type's schema (the same shape
// slider.slides uses). A site can register another facet type and
// list it here without touching this schema.
title: 'Facets',
widget: 'object_list',
typeField: 'type',
allowedBlocks: ['checkboxFacet', 'selectFacet', 'daterangeFacet', 'toggleFacet'],
defaultBlockType: 'checkboxFacet',
},
headline: { title: 'Headline', type: 'string' },
title: { title: 'Title', type: 'string' },
facetsTitle: { title: 'Facets title', type: 'string' },
// The quick-answer region only renders once a query has been
// asked; the sample question is what data-block-selector-input
// types to reveal it (query-reveal-page + query-reveal.spec).
quickAnswerSample: { title: 'Sample question', type: 'string' },
quickAnswer: {
title: 'Quick answer',
widget: 'blocks_layout',
allowedBlocks: ['quickAnswer'],
},
// The results region (docs/examples/search.md): a child listing
// block under blocks_layout.listing. Undeclared, its children
// render but never enter the pathMap — the exact orphan the
// guardrail now refuses without exemptions. Mirrors the admin's
// search schemaEnhancer (volto-hydra/src/index.js) EXACTLY —
// that enhancer only adds the field when absent, so a diverging
// fixture copy would win and change the sidebar.
listing: {
title: 'Results Listing',
widget: 'blocks_layout',
description: 'Listing block to render search results',
allowedBlocks: ['listing', 'default', 'summary', 'teaser', 'image'],
maxLength: 1,
defaultBlockType: 'listing',
},
},
},
}JSON Block Data
Example block JSON (as stored in the CMS). This is the data structure your component will receive in the block prop.
{
"@type": "search",
"headline": "Search with Facets",
"listingBodyTemplate": "summary",
"facetsTitle": "Filter by",
"facets": [
{
"@id": "facet-type",
"type": "checkboxFacet",
"title": "Content Type",
"field": {
"value": "portal_type",
"label": "Type"
},
"multiple": true,
"hidden": false
},
{
"@id": "facet-subject",
"type": "checkboxFacet",
"title": "Tags",
"field": {
"value": "Subject",
"label": "Tags"
},
"multiple": true,
"hidden": false
}
],
"blocks": {
"listing-1": {
"@type": "listing",
"variation": "summary",
"querystring": {
"query": [
{
"i": "path",
"o": "plone.app.querystring.operation.string.absolutePath",
"v": "/"
}
],
"sort_on": "effective",
"sort_order": "descending"
}
}
},
"blocks_layout": {
"listing": [
"listing-1"
]
},
"query": {
"b_size": "4",
"query": [
{
"i": "path",
"o": "plone.app.querystring.operation.string.absolutePath",
"v": "/"
}
],
"sort_on": "effective",
"sort_order": "descending"
},
"showSearchInput": true,
"showSortOn": true,
"showTotalResults": true
}Rendering
How this block renders in your frontend. Add its handling to your renderer, or — for list-style blocks — register a fetcher and reuse your list rendering.
function SearchBlock({ block, blockId }) {
const [query, setQuery] = useState('');
const facets = (block.facets || []).filter(f => !f.hidden);
const listing = block.blocks_layout?.listing || [];
const listingId = listing[0];
const listingBlock = listingId ? (block.blocks?.[listingId]) : null;
return (
<div data-block-uid={blockId} className="search-block">
{block.headline && <h2 data-edit-text="headline">{block.headline}</h2>}
<input
type="search"
placeholder="Search..."
value={query}
onChange={e => setQuery(e.target.value)}
/>
{facets.length > 0 && (
<div className="facets">
<h4 data-edit-text="facetsTitle">{block.facetsTitle || 'Filter'}</h4>
{facets.map(facet => (
<FacetRenderer key={facet['@id']} facet={facet} />
))}
</div>
)}
{listingBlock && (
<ListingBlock block={listingBlock} blockId={listingId} />
)}
</div>
);
}
function FacetRenderer({ facet }) {
switch (facet.type) {
case 'checkboxFacet':
return <fieldset data-block-uid={facet['@id']}><legend data-edit-text="title">{facet.title}</legend>{/* checkbox options */}</fieldset>;
case 'selectFacet':
return <label data-block-uid={facet['@id']}><span data-edit-text="title">{facet.title}</span><select>{/* options */}</select></label>;
case 'daterangeFacet':
return <label data-block-uid={facet['@id']}><span data-edit-text="title">{facet.title}</span><input type="date" /> – <input type="date" /></label>;
case 'toggleFacet':
return <label data-block-uid={facet['@id']}><input type="checkbox" /> <span data-edit-text="title">{facet.title}</span></label>;
default:
return null;
}
}