How MODx works

MODx works for you, not the other way around. You build your mark-up (varying from a html table filled layout or standards compliant HTML5, to XML to use in your Flash application and everything in between) and tell MODx where to put user edited content using specific tags. MODx does not output anything (absolutely nothing!) unless you tell it to, so you have complete control over your website.

Let's go through the basics of MODx, and the terms used.

The first thing to mention are Resources. Resources represent pages (in the broadest sense of the word) within your site. Resources can be split into four different categories, in MODX terms the category is called the class key. They are:

• 
  Documents best described as "pages".
  Documents contain actual content which you will modify from the backend.
• Weblinks asd: will redirect the viewer to the specified resource (for example a Document), or to a specified URL
• Static resource, takes the content of a file on the fileserver.
• Symlinks as: acts as a copy of another resource;

MODx works for you, not the other way around. You build your mark-up (varying from a html table filled layout or standards compliant HTML5, to XML to use in your Flash application and everything in between) and tell MODx where to put user edited content using specific tags. MODx does not output anything (absolutely nothing!) unless you tell it to, so you have complete control over your website.

Let's go through the basics of MODx, and the terms used.

You can also use [[$chunkname]] chunk tags, [[!snippetname? &property=`value`]] snippets and [[+placeholders:ellipsis=`20`]] placeholders.