Theme and layouts

In Layouts, open Code and enter this in Regions (JSON):

[{"key":"main","label":"Main"}]

Save draft, then publish the layout. With no allowedBlockTypes, the area accepts every current part. Keel saves that list with the layout, so publication uses the same choices. To restrict an area, use Visual and choose the parts it accepts, or give allowedBlockTypes an explicit list such as ["heading","richText"] in Code. An invalid list is refused with the region and allowedBlockTypes field named. Maps can be allowed separately.

Edit expandable answers

Text parts keep expandable answers when you paste or edit them. For example, paste <details><summary>Q</summary>A</details> into a Text part. Open Q to edit its answer. Save, publish and check Preview and the site. The question and answer stay together. The saved open or closed state is kept.

For a group with only one answer open at a time, use an HTML part with the same name on each disclosure:

<details name="faq"><summary>First question</summary>First answer</details>
<details name="faq"><summary>Second question</summary>Second answer</details>

Publish the page to show the change on the site. Text parts containing other formatting the editor cannot hold, such as tables, still open read-only to protect that content.

Collect a web address

In Forms, open the form, choose Add a field, then choose Web address under Kind of field. Give it a label such as Current site address. Tick Visitors must fill this in only when an answer is required. Add field, then Save.

A Web address question uses the browser’s web-address keyboard and checks the answer. Use a complete address such as https://example.com. An optional question accepts a blank answer. Invalid answers show a message beside the question and a link to it in the error summary, in Preview and on the site. Preview forms do not send.

For an AI helper, the same question is {"name":"website","type":"url","label":"Current site address","required":true} in a form’s fields. An invalid submission returns 400 naming fields.website. To delete the question, choose Remove beside Current site address, confirm Remove question when asked, then Save. Helpers remove it from the complete fields list in a versioned form update.

Editing pages: embeds

In the page editor, add an Embed part and choose Pasted link or embed code. Paste a service link or the embed code into Link or embed code. Keel accepts YouTube, Vimeo and Voomly videos, Google Maps, Calendly booking pages, Facebook pages and Typeform forms.

For Typeform, paste a share address such as https://form.typeform.com/to/AbCd1234 or https://account.typeform.com/to/AbCd1234. You can also paste <div data-tf-widget="AbCd1234"></div> including the script if Typeform gave you one. Live embed code (data-tf-live) is refused; paste the share address or widget code instead. Keel keeps only the form’s frame address; it doesn’t run the pasted script. Other Typeform addresses show which share addresses work beside Link or embed code.

For Maps, paste https://www.google.com/maps/embed/v1/place?key=YOUR_KEY&q=Toronto. Keel rebuilds the map without the API key. Search (v1/search?q=Toronto) and a view (v1/view?center=43.65,-79.38&zoom=15) work too. If the place can’t be read, correct the address in the named field. You can also choose Map and type the place instead.

For Voomly, paste the whole video’s embed code or its share address. If its video id is short or malformed (for example, https://share.voomly.com/v/abc123), the Link or embed code field says “This doesn’t look like a Voomly video id. Paste the video’s share link or embed code.” Collection links still explain that Keel embeds single videos, not collections or other Voomly pages. The embed-build.js script alone has no video in it; the message asks you to paste Voomly’s embed code instead.

Wait for the draft to save, use Preview, then publish the page. Preview and the live page show the same frame. To remove it, select the part and choose Remove. AI helpers remove the part from the region’s parts array and save the page.

Typeform live embed code (data-tf-live) uses a configuration ID, not a form ID, and is refused without a lookup. For example, <div data-tf-live="01J5X1H8WM5CSXVDN89WXNX5EB"></div> returns 400 on the part’s data.url: “We couldn’t read this Typeform live embed. Paste its share address, https://form.typeform.com/to/<id> or https://<account>.typeform.com/to/<id>, or its data-tf-widget embed code instead.”

Throw away changes

Open the page, item, Theme, layout, shared design part, site menu or Site-wide details. Choose Discard changes. Keel asks: “Put {name} back to what’s on your site? Your changes since it was last published are thrown away.” Confirm Discard changes to return the whole draft to the published version. This throws away unsaved edits in this browser too. Visitors keep seeing the same published version.

For example, if About is published at /about and you change its words and address to /our-team, Discard changes brings back its published words and /about. Its layout and search settings go back too. Version history records Discard.

An item that has never been published offers Delete page or Delete {kind} instead. Pages and collection items go to their deleted list and can be brought back. A kind without a deleted list is deleted for good; read the confirmation before continuing.

A never-published theme or set of site-wide details has Delete theme or Delete site-wide details instead. The confirmation says it is deleted for good and cannot be brought back. The API accepts DELETE /api/sites/{siteId}/theme/{id} and DELETE /api/sites/{siteId}/globals/{id} with the current If-Match, for a Site administrator (including an approved token). For example, read the theme, then send DELETE /api/sites/{siteId}/theme/{id} with If-Match: "AAAAAAAAB9E=". A published item is refused with 400 naming id; use Discard changes for it. A missing If-Match returns 428; a stale one returns 409 with current.

Earlier saves alone never block deleting a layout. The Delete layout dialog names their pages: “Earlier saves of Home used this layout. Restoring one of them keeps its content and uses the page’s current layout.” For example, GET /api/sites/{siteId}/layouts/{layoutId} returns "earlierSavePages": [{"id":"6d0c7a43-3e7c-4bb1-9a6e-0a8b1b2f6c11","title":"Home","deleted":false}]. DELETE with the layout’s If-Match returns 204 when no current draft, live page, deleted page or collection uses it. Restoring an earlier save then keeps its content and the page’s current layout. Publish the restored draft when ready.

Deleted pages

A deleted page leaves the site and waits under Deleted pages, below the page list in Pages. Each row shows when it was deleted and by whom.

To bring one back, choose Bring back on its row, check the address, then confirm Bring back. It comes back as a draft, where it was in the page tree. Publish it again to put it on the site.

If another page took its address while it was gone, the row says so and the button reads Bring back at a new address. Keel suggests a free address, for example: “Another page uses /about now. Try /about-restored, a free address you can change.” Keep it or type your own.

A page whose parent is deleted too says: “The page it was under is deleted too. Bring that one back first.” Choose Bring back “{parent}” first, then bring back the page itself.

Site administrators can remove deleted pages for good. Delete permanently on a row removes that page and the deleted pages under it, with their drafts and earlier saves; the confirmation lists every name. Delete all permanently empties the list in one step and handles the parent and child order for you; confirm Empty deleted pages. Neither can be undone.

For an AI helper, the same tasks are GET /api/sites/{siteId}/pages/deleted, POST /api/sites/{siteId}/pages/{pageId}/bring-back with the deleted page’s version as If-Match and an optional {"slug":"about-restored"}, and, with site administrator access, POST /api/sites/{siteId}/pages/deleted/permanent with {"pages":[{"id":"…","version":"…"}],"cascade":true}. cascade includes the deleted pages under each one; a page under it that is still on the site refuses the whole request.

Site language and form words

In Web address and launch, choose Edit site details, choose Language, then Save. Cancel discards your unsaved name and language choices. For example, German (Germany) gives built-in form messages German words and shows a collection-list date as “21. Oktober 2026”. French (Canada) shows “21 octobre 2026” and French form messages. Languages without a translation table use English form messages. A form’s own message wording stays in use.

Show and sort saved dates in a collection list

Open the page’s Collection list part. Date to show chooses the saved Date field to display; Date to sort by chooses the field used by Newest first or Oldest first. Both start at Publish date, so existing lists stay as they are. For example, show Event date and sort by Closing date to show each event’s day with the latest closing date first. Choose Publish date again to undo either choice. Show the date can hide it. Missing dates sort last and are not shown; Chosen order keeps your item choices.

A saved Date field may already appear in a collection list while the item’s own page still needs an item design. The item editor’s note names Date to show so you can find the list setting. Dates use the site’s language. For an AI helper, the same example is:

{"type":"collectionList","data":{"collection":"<collection-id>","dateField":"event-date","sortDateField":"closing-date","order":"newest","limit":10}}

Use a Date field from this collection. An unknown field or a field of another type is refused with 400 beside data.dateField or data.sortDateField: “Choose a Date field from this collection, or use Publish date.” Save and publish check the same choices.

Page and collection addresses

Use lowercase letters, numbers, hyphens and underscores, with single hyphens between words. For example, a page can keep /about_us, a collection /photo_galleries, and an item /news/my_post from an imported site. Set Address when creating or renaming a page, in collection settings or in the item editor. Keel keeps the address exactly as you type it: capitals and spaces are refused with a message beside Address, not changed for you. For example, About_Us and about us are refused, and about_us is accepted. The API refuses them the same way, with a 400 naming slug. Other invalid input also shows a message beside the named field; correct it before saving. about_us and about-us are different addresses. Old address links can send visitors from one to the other. Preview and Live keep the address you saved.

Back to the Help centre