These are the kinds of data you can embed in your web pages:

A content field from an HTML file (embed_type,content_file,content_field)

A content field from an XML file (embed_type,content_file,tag_type,tag_name)

A RANDOM content field from an HTML file (embed_type,content_file)

A RANDOM content file from an XML file (embed_type,content_file)

A field with a HARD-CODED VALUE (--)

A PASSTHRU VALUE (value1,value2)

A COMBINATION of hard-coded and passthru values (value1)

Display content based on CONDITIONAL TAGS surrounding an embed tag (--)

Show the value of ENVIRONMENT VARIABLES (--)

The value of an HTML FORM element (embed_type,content_file,content_field,form_element)

n-level MENU DATA formatted into arrays (embed_type,content_file,content_field,data_type)

Linear NAVIGATION ELEMENTS driven by a content file (--)

The results from a SEARCH query (embed_type[,search_string])

STRIP ALL MARKUP from embedded content (--)

Use regular expressions to REPLACE pieces of embedded content (--)

Rather than displaying embedded content, put it into a VARIABLE (--)

Rather than merging content into a template, display it directly with NO TEMPLATE (--)

An entire text FILE (embed_type,content_file)


Using the preferences.ini file, you can also do some neat tricks:

RECURSIVELY PARSE embed tags contained in embedded content (embed_type,content_file)

Embed a field from a content file saved in a NON-STANDARD FILE LOCATION (embed_type,content_file,content_field)

Access INDIVIDUAL SEGMENTS of a page name for use in embed tags (--)

REQUIRE AUTHENTICATION before displaying a set of page names (--)

SET HREF TARGETS for external links that don't yet have a target set (--)

PRE-RENDER FILES before merging content into templates (embed_type,content_file)