Contains following features:
1.
Core.Module - main part of modules system. Contains functionality to manage modules, to provide data for them.
2.
Default Content Module - provide functionality to quick and easy edit pages/nodes data. Shortly: for each page could be generated default page, under (site)->(settings)->(Defaults)
Content manager just have to fill data into "default" page, - all pages with same alias will "take-relate" those data. if page have to be with unique data, - content manager just have to edit data of this page.
3.
Module.MultiSiteFields - specific property types, which could work in module context:
-
TreeNode picker - could be single picker, multiple picker, could pick nodes from different Tree Types (content,media,member,filesystem etc.)
Have predefined start point: (from site root folder, from site settings, from site mail templates etc). could be simple extended: extra start point and tree could be added from code.
-
Links picker - needs to manager site-node links: internal or external, images, target etc.
4.
Mailing System Module - provide a way to manage site mails. Have possibility to predefine mail settings for each functionality by generate and fill template nodes under (site)->(settings)->(mail templates).
Then form code could be executed transformation template to mail...
5.
Site Widgets Module - Content managers just have to fill content, they don't know well html formatting etc. that is why template editor isn't good solution to change page structure.
That is why been develop module with 1 macros only, this macros-control need to render "banners-widgets" for page.
how it works:
- developers needs to develop frontend, html specify place holders (containers) for banners
- developers have to predefine banner types: they have to generate document alias for them, and macros, which will be used to render banner
- developers could predefine several banners (site/settings/banners/1,2,3,4...n
- content manager need to chose banners for each of page by nodes picker:
example: for homepage top area: needs to be shown breadcrumb, image carousel, top news, image link text banner...
more...
6.
Module.PageComments - possibility to manage (approve, decline, delete, add,edit ) comments for each of page-node (frontend have to has control which render client side code). Visitors then could have possibility to live their comments, related to page content. then from backoffice content manager could approve -decline them.
7. '''
Module.Commerce''' - provide a way to sell products (nodes, which have property: product price).
etc.