Skip to content

Editing content ​

Content is written in the dashboard. Each blueprint appears in the sidebar under Content. Open it to see its resources, then create or edit one in the editor.

Every project member can create, edit, publish and delete resources.

The resource list ​

The list shows one column per blueprint field, then:

ColumnShown whenContent
SEOSEO scoring is enabled on the blueprintThe saved score, as a coloured badge
PublishedAlwaysThe publication date, or a Draft badge

Rich text is shown as plain text, references by the label of the resource they point to.

ActionHow
SearchType in Search.... It matches Text, Rich text, Email, Slug and Link fields.
SortClick the SEO or Published header. By default, the most recently updated resources come first.
Choose columnsClick Toggle columns (the columns icon) and tick the ones to show.
Page size10, 25 or 50 rows per page.
Open a resourceClick its row.
Delete severalTick their rows, then Delete in the bar that appears. Deletion is permanent.

Click New {blueprint name} in the top bar to create a resource.

Saved views ​

A saved view remembers which columns are visible and how the list is sorted. Views are personal: other members do not see yours.

  • All shows every column with the default sort.
  • Click + (Save current view), name the view and click Save.
  • On the active view, the pencil renames it and the × deletes it.
  • When you change the columns or sort of the active view, an amber dot appears. Click the save icon (Save changes) to update the view.

The search term is not saved with a view.

Creating and editing a resource ​

The editor shows the blueprint's fields in order. The buttons in the top bar depend on the state of the resource:

StateButtons
Draft (or new)Save as Draft, Publish, Schedule
ScheduledSave Changes, Cancel schedule
PublishedSave Changes, Unpublish

The status (Draft, Scheduled or Published) is shown next to these buttons. The trash icon deletes the resource after confirmation.

Press Ctrl+S (⌘+S on macOS) to save without publishing.

Required fields are checked when you click Save as Draft, Publish or Save Changes.

WARNING

On a published resource, Save Changes puts your edits live right away. There is no autosave on published or scheduled resources: changes you have not saved are lost when you leave the page.

Singular and read-only blueprints ​

  • A singular blueprint has a single resource, created automatically. Open it from the list and use Save Changes. The API always serves it, so it has no publishing controls, and it cannot be deleted.
  • A read-only blueprint (form submissions, for example) opens its resources in a view-only page. Records are created through the API only.

Publishing ​

ActionWhat it does
PublishSaves your pending edits and publishes them in a single step.
ScheduleOpens Schedule publication. Pick a date and time in Publish at (it must be in the future) and click Schedule. The resource goes live automatically at that time.
Cancel scheduleThe resource stays a draft and is not published at the scheduled date.
UnpublishTurns the resource back into a draft. It is no longer publicly available.

Publishing and scheduling are only available on standard (multi-record) blueprints. See Publishing for how the API treats each state.

Autosave ​

Drafts save themselves. Two seconds after you stop typing, the draft is saved in the background. It is also saved when you leave the page or close the tab.

The indicator next to the save buttons shows where things stand:

IndicatorMeaning
Unsaved changesAn edit is waiting to be saved.
Saving…The save is in progress.
Draft saved 14:32Saved at that time.
Not saved — …The save failed. The reason follows (an invalid value, for example).
Autosave off — no longer a draftSomeone published or scheduled the resource meanwhile. Use Save Changes.

Good to know:

  • On a new resource, the first autosave creates the draft. A resource you started and left therefore stays in the list as a draft.
  • Autosave skips required-field checks, so an incomplete draft is still saved.
  • Autosave never publishes, and only applies to drafts.
  • Background saves do not trigger workflows. Save as Draft, Publish and Save Changes do.

Variants ​

When the blueprint has variants, the editor shows one tab per variant. The default variant carries a Default badge and opens first. Each tab holds its own copy of every field.

Autosave, publishing and scheduling apply to the whole resource, all variants together.

Rich-text editor ​

Rich text fields use a block editor.

FeatureHow it works
ToolbarUndo and redo, block type, bold and italic, more formatting, lists, alignment, tables, and inserting images, videos and separators. On narrow screens it collapses into menus.
Slash menuType / at the start of a line to insert a paragraph, heading (H2 to H4), bulleted or numbered list, quote, code block, table, image, video or separator. Keep typing to filter.
Text bubble menuSelect text for bold, italic, underline, strikethrough, inline code, text colour, highlight and link.
Link bubble menuClick a link to edit it, open it or remove it. Links can open in a new tab. Pasting a URL on selected text turns it into a link.
Image bubble menuClick an image to set its alt text, align it (left, centre, right or full width), resize it (S 320 px, M 640 px, L 960 px), replace it or remove it. Images can have a caption.
ReorderingHover a block and drag the grip in the left margin to move it.
Full screenThe button in the footer. Press Esc to exit.

The footer also shows the word count, character count and an estimated reading time.

Videos ​

Insert a video from the toolbar or the slash menu and paste its address, or paste a YouTube or Vimeo link on an empty line. YouTube videos are embedded through youtube-nocookie.com. Other providers are not supported.

What gets stored ​

The HTML is cleaned before it is saved, whatever the source (editor, API or MCP). Only the elements the editor can produce are kept: paragraphs, H2 to H4, lists, quotes, code blocks, tables, links, images with captions, and YouTube or Vimeo embeds. Scripts, event handlers, javascript: links and other providers' iframes are removed. Empty captions are dropped.

Media library ​

Add images to rich text from the toolbar, the slash menu, or by dragging and dropping or pasting them into the editor. The image dialog has three tabs:

TabWhat it does
UploadSend a file from your computer.
Media libraryReuse an image already uploaded to this project.
From a URLCopy an image from another site into the project.

Limits: JPEG, PNG, GIF, WebP or AVIF, up to 10 MB and 30 megapixels.

Uploaded images are optimised before they are stored: scaled down to 2,000 px wide at most and converted to WebP. GIFs are kept as they are, so animations survive. Images are served from Diggama's storage by their public URL, so your front end can use the HTML as-is.

The media library lists every rich-text image in the project, newest first, and can be searched by file name. Hover an image to delete it. If a resource still uses the image, you are asked to confirm a second time.

TIP

SVG files are not accepted in the rich-text editor. SVGs imported with a page builder zip are cleaned before they are stored: scripts, event handlers, embedded HTML and external links are removed.

Image and File fields (outside rich text) have their own upload button. Image fields take the same types as above, up to 10 MB. File fields take images, PDF, Office documents, text, CSV, ZIP, MP3/OGG/WAV and MP4/WebM, up to 20 MB.

SEO panel ​

When SEO scoring is enabled on a blueprint, the editor shows an SEO score panel beside the form. The score (0 to 100) updates as you type, and each check shows a green, amber or red status with advice.

To enable it, open the blueprint, go to Settings and turn on SEO scoring. Then map your fields:

SettingUsed for
Content field (required)Length, readability, subheadings, links, image alt text
Focus keyword fieldThe keyword the other checks look for
Title fieldTitle length, keyword in title
Description fieldMeta description length, keyword in description
Slug fieldKeyword in slug
CheckGood when
Focus keywordA keyword is set
Content length300 words or more
Readability20 words or fewer per sentence on average
Keyword densityThe keyword makes up 0.5% to 3% of the words
Keyword in introductionThe keyword appears in the first 120 words
Keyword in title / slug / meta descriptionThe keyword appears there
Title length40 to 60 characters
Meta description length120 to 160 characters
SubheadingsThe content uses H2 to H4 headings
Outbound / internal linksThe content contains links
Image alt textEvery image has alt text

Checks only run for the fields you mapped. The score is a weighted average: a passing check counts in full, a warning counts half. With variants, the default variant is scored.

The score is saved with the resource and shown in the SEO column of the list.

Diggama Documentation