Skip to content

Pages, Tabs, Modules, Widgets, and Managed Content

timothyf edited this page Nov 16, 2010 · 1 revision

If you are building your own site with EngineY, it is important for you to understand the structure of how content is displayed in an EngineY site. There are several important objects which go into building a page that a user sees. These objects are pages, tabs, modules, widgets, widget layouts, and html contents.

Pages – Pages can be dynamically added and removed from your site. Any page that is created should have a method for navigating to it, which can be through a Tab or through functionality contained within a widget.

Tabs – Tabs are the navigational elements listed across the top of your pages that provide each access to key areas of your site.

Modules – Modules are large chunks of functionality of your site that can be activated and deactivated. Popular modules include blogs, groups, events, etc. Each module may contain one or more widgets which also need to be configured. However deactivating a module will also deactivate all of its associated widgets.

Widgets – Widgets are the sections of content that appear on pages. For example the home page of your site will usually be composed of a number of widgets which might include a members widget, a groups widget, and an activity feed widget. Widgets are the manner in which new features and functionality can be added into your site.

Widget Layouts – Widget layouts bind widgets to a specific page and column for display. So this table is what is defining what gets put on a page and where it is displayed. You could have lots of widgets available in the widgets table, but if there is not any Widget Layouts created, you will not see any widgets on your page. This allows you to reuse widgets on the same page or on different pages. You can also bind the HTML Contents widget with a piece of Managed Content stored in the html_contents table. This provides you with CMS capability.

HTML ContentsHTML Contents are chunks of managed content that can be displayed using the HTML Content widget.

Something went wrong with that request. Please try again.