FTdata

It acts as a neutral container or temporary holding area for parts that don’t have a more specific target (place:).

It’s where parsed information lives before it’s routed or rendered —

a kind of default bucket in $this->CP->parts.

It represents “internal data, not visible output”

When a .txt part doesn’t specify place:print or place:html-body, it still gets stored somewhere —

but not printed, not rendered, not used in session or cookie.

So FTdata holds:

• internal variables,

• reusable templates,

• computed fragments,

• or data passed between parsers/controllers.

In other words: “Functional Transport Data” (engine’s internal wiring).

FTdata = the “shared memory” of the current file/page.

Why it’s a good idea

• Prevents null/undefined array keys ($CP->parts[null] → messy).

• Gives a consistent namespace for internal values.

• Keeps “invisible” data separate from visible HTML or exported states.

• Works even if you parse multiple .txt files into one context.