Typed a title on my markdown macro and nothing changed on the page

What you are seeing

I typed a title on my markdown macro and nothing changed on the page.


#Why it happens

Two separate reasons. First, the title strip only renders when 'Show Border' is on. With the border off there is nowhere to show it. Second, the title you type is saved onto the stored document, and the header shows that document's title rather than a macro setting.


#What to do

Turn on 'Show border' in the macro config. The header will then show the document's title. On a published Capable Site the title appears as a heading regardless of the border.


#Settings involved

Setting

Where

What it does

Global settings → Capabilities → Markdow

-

Hiding Markdown removes it from the Capable nav bar and the content byline menu across the site (app property capable-global-hidden-capabilities). It does NOT stop existing macros from rendering.

Space settings → Space Capability Settin

-

Auto shows the byline entry only when the page already carries markdown; Always pins it in every page's byline in that space; Never hides it there. Stored on the space property <APP_HASH>_capable under capabilities.alway

Global settings → Features → AI integrat

-

'Allow AI-powered features across Capable. Turn off to disable AI for all users.' Turning it off removes the Studio (Generate markdown with AI) section from the markdown catalogue. Studio additionally requires the app's


#Limits that apply here

Limit

Value

What happens

Large-document scroll mode

500,000 characters

Past this the document macro shows '⚠️ Large content detected. Rendering in scrollable mode.' and renders inside a fixed 1200px-high scroll box instead of inline.

Virtualised rendering threshold

500,000 chars ; 1,000,000 chars (large p

Above the threshold the document is chunked (400 lines or 60,000 characters per chunk, fences kept intact) and only visible chunks are rendered.

MCP / Rovo document size cap

512 KB (524,288 characters)

Creating or updating a markdown asset through the Capable tools refuses (rather than truncates) anything larger, with a message telling the caller to split it.


#A few things that catch people out

  • The duplicate-title check only inspects documents directly under the space's Capable storage, and if the check itself fails the save proceeds anyway.



Found it? Good.