We Provide progressive business solutions

Researchg

Web Content Management Systems
A universal interface to connect to and manage any content management system.

solutions

Consolidating Control Panel Interfaces
Designing one interface to connect through the APIs of disparate content management systems

Results

Extending Core Applications
Every CMS has it's own way of doing things. A place to organize the different ways to do things in different types of content management systems.

Login

Evolution

Many content management frameworks exist and are being created every day. Few are as versatile in developing robust web applications, and the community at MODx has been showing steady growth.

Rich Internet Applications accommodate for older browsers and mobile devices by degrading gracefully. Javascript frameworks have breathed new life into the web by providing enhanced user experiences. User interface experts work closely with software engineers and designers to create intuitive interfaces. Now is a better time than ever to be building web applications, and MODx Evolution makes this incredibly easy. You will be up and running with a custom site within just a few recipes, let’s get started!

Most people tend to learn better with first-hand experience. Evolution comes ready with a demonstration site you can enable upon installation. In doing so you will be able to quickly see how the disparate pieces of information are organized and how the components are merged into an application.

Anatomy of a snippet. You will need to clearly understand how to create and invoke snippets, modules, chunks, and plugins, to follow along with the examples in this book.

We will add properties to our snippet call by passing the property and value in the snippet call. When passing a lot of properties you may choose to separate your properties with a line break. We will still refer to this as one ‘line of code’ or one ‘snippet call’. The properties may be referred to as arguments or parameters.

For improved readability we will separate the properties of our snippet calls. This will work just the same if this is combined into one line.

The space preceding the ampersand is optional. We could also write our call like this:

The tags that are used in Evolution and Revolution are a little different. A chart of the tagging syntax is provided for your reference.

Content Elements

Evolution (Old)

Revolution (New)

Templates

no tag representation

no tag representation

Template Variables

[*templatevar*]

Chunks

{{chunk }}

Snippets

Plugins

no tag representation

no tag representation

Modules

no tag representation

does not exist in Revolution

Content Tags

Placeholders

[+placeholder+]

Links

[~link~]

System Settings

[(system_setting)]

Language

no tag representation

language_string_key