1. Getting Started
      1. Basic Installation
      2. What is MODx
    2. Content Editing
      1. Editing Documents
      2. MODx Tags
        1. Document Variables
      3. Terminology
      4. The Manager
      5. Who Should Read This
    3. Designing
      1. Adding Chunks
      2. Adding MODx Tags
        1. Resource Fields
      3. Adding Snippets
      4. Document Caching
      5. Template Basics
    4. Administration
      1. Friendly URL Solutions
      2. Manager Users
        1. Manager Roles And Groups
        2. Reset your Password - Unblock your User
        3. Why Manager Users, Roles and Groups
      3. Moving Site
      4. Taking sites down for maintenance
      5. Upgrading
      6. Web Users
        1. Creating a Web User
        2. Web User Groups and Document Groups
        3. Why Web Users and Groups
    5. Developer's Guide
      1. API Reference
        1. DBAPI
          1. delete
          2. escape
          3. getInsertId
          4. query
          5. select
          6. update
        2. Document Object
        3. DocumentParser Object
          1. addEventListener
          2. changeWebUserPassword
          3. documentContent
          4. documentGenerated
          5. documentIdentifier
          6. documentListing
          7. documentMethod
          8. documentObject
          9. getAllChildren
          10. getCachePath
          11. getChildIds
          12. getDocumentChildren
          13. getDocumentChildrenTVarOutput
          14. getDocumentChildrenTVars
          15. getLoginUserID
          16. getLoginUserName
          17. getLoginUserType
          18. getManagerPath
          19. getParent
          20. getParentIds
          21. getUserData
          22. hasPermission
          23. isBackend
          24. isFrontend
          25. logEvent
          26. maxParserPasses
          27. minParserPasses
          28. regClientCSS
          29. runSnippet
          30. table_prefix
          31. tstart
          32. webAlert
      2. Chunks
      3. Modules
        1. How to create and run a module from within the Content Manager
        2. Managing module dependencies
        3. Setting up configuration parameters
        4. Writing the module code
      4. Plugins
      5. Snippets
      6. Template Variables
        1. (at) Binding
          1. (at)CHUNK
          2. (at)DIRECTORY
          3. (at)DOCUMENT
          4. (at)EVAL
          5. (at)FILE
          6. (at)INHERIT
          7. (at)SELECT
          8. What are (at) Bindings
        2. Creating a Template Variable
        3. What are Template Variables
        4. Widgets
          1. Misc. Widget
          2. DataGrid Widget
          3. Floater Widget
          4. Hyperlink Widget
          5. Marquee Widget
          6. RichTextBox Widget
          7. Ticker Widget
          8. Viewport Widget
          9. What are Widgets

Adding MODx Tags

Last edited by Dmytro Lukianenko on Aug 26, 2013.

[MODx Tags] are the unique elements that will add content and functionality to your web pages. You can insert [MODx Tags] anywhere in your template or document's content where you want the tag's content or functionality to appear.

In the template basics article, we saw a very basic template that didn't do much. Let's add a few [MODx Tags] to it and see it come alive.

Internal MODx Tags

This document will focus on using internal [MODx Tags]. For more specific information on these tags, see the section "MODx Tags".

To begin with, we can personalize the page's title with our site's name and the name of the page:

<title>[(site_name)] - [*pagetitle*]</title>

These tags in the head of your template will display something like "MODx Content Management System - Adding MODx Tags" in the title bar of the browser.

The "site_name" is taken from the name that was configured for your site in the System Configuration menu. The "pagetitle" is the Title you gave the document when you created it.

The next thing we want to do is have the document's content appear in the main part of our page. Add the

[*content*]

tag where the content should appear:

<div id="content">
  <h1>[*longtitle*]</h1>
  [*content*]
</div>

You will also see that the "longtitle" was added before the "content", so every page will have a customized subheading. The "longtitle" is taken from the Long Title field when you created the document. The "content" is the text you entered in the Document content editor when you created the document.

And finally, in the footer, you may want to have your site's name and email address:

<div id="footer">Copyright © <a href="mailto:[(emailsender)]">[(site_name)]</a> 2005</div>

Both of these values are taken from the database and were set in the System Configuration menu.

Suggest an edit to this page on GitHub (Requires GitHub account. Opens a new window/tab).