Sep 21, 2018


    SORTEX un clasificador óptico:   Configuración de un nuevo punto de referencia en la clasific... Leer más...


    El propósito principal del proceso de tostaduría es garantizar el desarrollo de un aroma uniform... Leer más...
  3. SORTEX Z+


    Continua la revolución de clasificación.  - Una precisión sobresaliente - Máxima rentabilid... Leer más...


    Revolución en la clasificación de Verduras. La SORTEX K ha demostrado ser un clasificador muy f... Leer más...


    Clasificadores ópticos. Para los productos más seguros en sus paquetes..... Leer más...
  6. Tren Buhler

    Tren Buhler

    Tren BUHLER Las máquinas de Buhler están diseñadas y construidas para maximizar el rendimiento... Leer más...

Documentation - Module Positions

Module Positions

This template incorporates two methods for placing your modules into its layouts.

Classic Module Positions

Using the traditional module positioning scheme, you can publish your module to any of the following:

  • Header
  • Top
  • Top2
  • Top3
  • Outer-Left
  • Outer-Right
  • Left
  • Right
  • Footer
  • Banner
  • User1
  • User2
  • User3
  • User4
  • User5
  • User6
  • User7
  • User8
  • User9
  • User10
  • User11
  • User12
  • User13
  • User14
  • User15
  • User16
  • User17
  • Bottom-Fixed

Since the module positions are contractible, if you choose not to publish a certain module on a page, then the template's layout will auto-adjust to accommodate that space. This allows you a great deal of flexibility in choosing where to publish your modules, without having to make any changes to the css of the template. Certain module groupings, like User1-User3, will adjust to equally* share the space attributed to the group by width. The same is true for the groupings: User4 & User5, User6-User9, User10-User13 and User14-User17.




*Module Width Distribution

Width DistributionIn the template parameters, you will note a setting called "Module Width Distribution". With this set to "Equal", if only two modules from the group are published on a page, then they will equally share the space for that group. If set to "Offset", then the first module will occupy approx 70% of the group width, and the second module with be allotted 30% of the width.



Self-Columnizing Module Zones

This template also has self-columnizing module "zones", which allow you to achieve an unlimited number of columns across for your modules' layout. This is achieved by using a jQuery-based columnizer plugin to handle the splitting and positioning of any modules published to the same position. The module zones are mapped as follows:

  • TopZone1 (Beneath Group User1-User3)
  • TopZone2 (Above Left, Right and Main Content)
  • TopZone3 (Between Left and Right but Above Main Content)
  • MidZone1 (Beneath Group User4-User5)
  • BotZone1 (Beneath Group User6-User9)
  • BotZone2 (Beneath Group User10-User13)
  • FooterZone1 (Beneath Group User14-User17)

While each of these Zones arranges modules published to them ordered from left to right, you can also stack up to three rows per zone by denoting A, B, or C to the position.

Here's an example: You have four modules, each is published to position TopZone1A. They will equally split that zone space and arrange from left to right according to their ordering as modules.

You also publish 5 modules to TopZone1B. These create a new row beneat the "A" row, and columnize according to their ordering as modules.

Click Here for a screenshot of this scenario.


Load a Module in Your Content

You can place a module inside of your content articles with ease. Here's how:

1) Choose the module you want to display in a content article, and instead of choosing the position from the dropdown, simply type in a unique position name, such as "contentmodule1" and publish that module to all pages.

2) Now open the article in which you want to place the new module, and insert the following - BUT REMOVE THE * (asterisk):

{*loadposition contentmodule1}

No_Component Module Position

Sometimes you will wish to display a module on the page without having the component area showing up. We've found this to be useful in many front-page layouts. To do this, simply create a new module and publish it to the "no_component" position. Any page to which you publish this module will not display the central area of the template, allowing, for example, the display of only a slideshow published to the header on that page.