Usage

Parent Previous Next

Component's structure and main principles


"ARI Smart Content" can retrieve data from different data sources like databases, CSV files, Flickr and Picasa services, Joomla! articles, folder with images and etc. and then use these data by "ARI Smart Content" applications. For example it is possible to create a data source and define what photos should be selected from Flickr and then use this data source in Nivo Slider, Cloud Carousel or other "ARI Smart Content" application which operates with images. The same data source can be used by different applications. Not all applications are required to use data sources. Some of them supports ability to enter data manually (for example items for Accordion or Tabs plugin).


Applications from "ARI Smart Content" contain Joomla! module(s) and/or plugin(s) so you can configure them as standard Joomla! modules/plugins using regular behavior and interface.


For modules all parameters are configured in module settings page using user-friendly interface. Modules can be show in module positions which are supported by site template (standard Joomla! feature) or can be loaded into a content using ARI Smart Content - Load Module plugin or other similar plugin. If you prefer to use an application like a plugin, read the next paragraph.



How to use plugins from "ARI Smart Content"


As other Joomla! plugins, "ARI Smart Content" plugins can be found and configured on "Extensions → Plugin Manager" page on Joomla! backend. Applications plugins work like most of Joomla! content plugins, a plugin code is entered into content (for example in an article) in place where want to show an application (for example a slider, tabs and etc.). Plugin code is similar to HTML code. It contains plugin tag, attributes (optional) and some content between opening and closing plugin tags (optional). Plugin code contains an opening tag which is enclosed in curly braces (for example {myapp}), an closing tag which is placed between {/ and } symbols (for example {/myapp}), additional attributes can be placed in opening tag (for example {myapp param1="val1" param2="val2"}{/myapp}). A sample code looks like:


{myapp param1="val1" param2="val2"}... Some content goes here ...{/myapp}


Most plugins also support the following syntax to define attributes:


{myapp}

 {params}

   {param name="param1"}val1{/param}

   {param name="param2"}val2{/param}

 {/params}

{/myapp}


This syntax is useful if attributes values contain " symbol(s) or HTML code. It is also possible to use mixed syntax. For example:


{myapp param3="val3"}

 {params}

   {param name="param1"}val1{/param}

   {param name="param2"}val2{/param}

 {/params}

{/myapp}


Some plugins support ability to use one plugin code inside the other. The plugins use parameters which are defined on plugins settings by default, use attributes in a plugin tag only if you want to change default values of some parameters.


Note: if you use a WYSIWYG editor, we recommend to switch it to plain text mode before inserting a plugin code because WYSIWYG editors in design mode can add extra HTML code or encodes inserted HTML code.