Common models (collections)

In this chapter, the most important collections (tables) are described and their associated renders are presented. Text mostly contains links to source code documentation on RubyDoc website. Collection names follow Ruby and Ruby on Rails conventions. When dc_site name is used, the actual database collection name will be dc_sites. Model defines DcSite class and is declared in app/models/dc_site.rb file.

 

Some fields in collections are defined but not yet used or may be used as ideas for further extensions of CMS.

 

dc_site - Web sites managed by Rails instance

 

dc_page - Web pages data

  dc_page_renderer - Example renderer for rendering page data

  dc_part_renderer - Renderer for rendering embedded dc_parts

 

dc_design - Designs (views) for presenting data on web site

 

dc_user - Users collection

 

dc_policy_role - User roles

 

dc_piece - Documents, pieces of content that form web page

  dc_piece_renderer - Examples of how to save and use design from dc_pieces

 

dc_simple_menu - Simple menu system, was my first menu system. Menus can be nested only two levels.

  dc_simple_menu_renderer - Simple menu renderers examples

 

dc_menus - More sophisticated menu system. Menus can be nested n-levels.

  dc_menus_renderer - Menu renderers examples

 

dc_ad - Simple ad system. Ads may be defined as pictures, flash or script code, may be prioritized, may have limited number of displays or clicks.

  dc_ad_renderer - Ads renderer

 

dc_poll - Polls for easy data enter on pages

  dc_poll_renderer - Polls renderer

 

dc_big_table - Can be used to save application predefined data with full i18n support

 

dc_permission - Granular permissions to access database collections

 

dc_folder_permission - Permissions for editors for accessing data in folders

 

dc_journal - Document update and delete journal with ability to undelete particular update.