Native Content

Since version 2.3.2 every public post type (Pages, Posts, Casinos, Slots, News, Payment Methods, Software Providers, Authors) has the standard WordPress editor available alongside the theme's block layout. The two work together: use only blocks, only the editor, or mix both on the same page.

Because the editor content is stored as normal WordPress post_content, everything that expects standard WordPress behaviour works with it out of the box - core search, SEO and internal-linking plugins, RSS, migrations, and REST API publishing.

If a post has no editor content, nothing changes - the block layout renders exactly as it always has.

Editing

The editor appears on the post edit screen below the Blocks Section, using the classic WordPress editor. Content written there is styled with the same typography as a Content block (headings, paragraphs, lists, tables, images), and headings use the same sizes as block titles - so an H2 in the editor matches an H2 block title and the page reads as one consistent hierarchy.

Native Content Position

Theme Settings → Layout → Blocks → Native Content Position controls where the editor content renders relative to the block layout:

• Before blocks (default) - editor content first, block layout below it.
• After blocks - block layout first, editor content below it.

The setting has no effect on posts without editor content.

Placing blocks inside the content

Any block added to the page can also be placed inside the editor content using the block shortcode:

[block key="b8e71dac5"]

• Every block has an auto-generated Block Key, shown read-only under Block Settings → Block Data on the block itself.
• The Insert block button next to Add Media opens a picker listing the page's saved blocks (title, type, key) - clicking one inserts its shortcode at the cursor.
• A block placed via shortcode is automatically removed from the block area, so it renders once, exactly where you put it. Remove the shortcode and it returns to the block area.
• Blocks placed inline keep their normal design - they are not affected by the surrounding text styling.

Newly added blocks appear in the picker after the post is saved. See also the Shortcodes page.

Table of Contents

When the Table of Contents is enabled, H2 headings written in the editor are included alongside block titles, in the order they appear on the page - including blocks placed inline via shortcode. Editor headings automatically receive anchor IDs so TOC links scroll to them. Block-level TOC options (custom label, exclude) remain available on blocks; editor headings are always listed.

Publishing via the REST API

The public post types are exposed through the standard WordPress REST API, so external systems can create and update content the same way they would for regular posts:

POST /wp-json/wp/v2/slot
{
    "title":   "Book of Ra",
    "content": "<h2>Overview</h2><p>…</p>",
    "status":  "publish"
}

• Endpoints follow the post type key: /wp/v2/casino, /wp/v2/slot, /wp/v2/news, etc. (/wp/v2/posts and /wp/v2/pages for built-ins).
• Writing requires authentication - use an Application Password on a user with permission to edit the post type, sent as HTTP Basic auth over HTTPS. Reading published content needs no authentication.
• The content field maps to the editor content and renders through the Native Content system described above.