Thank you to everyone who has visited this blog and now onwards this will be updated regularly with all sort of stuff related to Webcenter sites...
Friday, 9 November 2012
Thursday, 3 June 2010
Static Lists Recommendation (Contributed by Partha)
Recommendations are assets that determine which products or content should be featured or “recommended” on a rendered page.
There are three kinds of recommendations:
• Static Lists – return a static list of recommended items (List Mode and Recommendation Mode).
• Dynamic Lists – return a list of recommended items that is generated by a dynamic list element that you create
• Related Items – return a list of recommended items based on relationships between flex assets, such as products.
In this section I shall elaborate about Static Lists Recommendations in Recommendation Mode.
To create a Static Lists recommendation in Recommendation mode:
1.Click New in the button bar.
2.In the new form, click New Recommendation.
3.Enter Name, Description, Start Date and End Date (date range in which the asset will display online), Mode and click Continue.
There are three kinds of recommendations:
• Static Lists – return a static list of recommended items (List Mode and Recommendation Mode).
• Dynamic Lists – return a list of recommended items that is generated by a dynamic list element that you create
• Related Items – return a list of recommended items based on relationships between flex assets, such as products.
In this section I shall elaborate about Static Lists Recommendations in Recommendation Mode.
To create a Static Lists recommendation in Recommendation mode:
1.Click New in the button bar.
2.In the new form, click New Recommendation.
3.Enter Name, Description, Start Date and End Date (date range in which the asset will display online), Mode and click Continue.
Wednesday, 2 June 2010
Deciding which data model
How you determine which type of data model should be used for a particular content?
The basic asset model is a good choice when your data has the following characteristics:-
1)It is fixed, predictable: there will be no need to add attributes to the asset type.
2)It is homogenous: all assets of the same type have similar attributes.
3)It has a moderate number of attributes. You are limited by your database as to how many columns/attributes you can have in the asset type table for a basic asset.
4)You want to use the static publishing method predominantly.
The flex model is the right choice when your data has the following characteristics:
1)It has lots of attributes.
2)It can be represented in a hierarchy in which assets inherit attribute values from parent assets.
3)You cannot predict what attributes might be necessary in the future.
4)Asset instances of the same type can vary widely. That is, not all assets of that type should have the same attributes.
5)Visitors browse your online site by navigating through “drill-down” searches that are based on the attribute values of your data.
6)You want to use Engage.
The basic asset model is a good choice when your data has the following characteristics:-
1)It is fixed, predictable: there will be no need to add attributes to the asset type.
2)It is homogenous: all assets of the same type have similar attributes.
3)It has a moderate number of attributes. You are limited by your database as to how many columns/attributes you can have in the asset type table for a basic asset.
4)You want to use the static publishing method predominantly.
The flex model is the right choice when your data has the following characteristics:
1)It has lots of attributes.
2)It can be represented in a hierarchy in which assets inherit attribute values from parent assets.
3)You cannot predict what attributes might be necessary in the future.
4)Asset instances of the same type can vary widely. That is, not all assets of that type should have the same attributes.
5)Visitors browse your online site by navigating through “drill-down” searches that are based on the attribute values of your data.
6)You want to use Engage.
Thursday, 20 May 2010
Method of calling Template CSElement and SiteEntry assets
How does your code call template, CSElement, and SiteEntry assets?
- Because a SiteEntry is a pagelet, you use the render:satellitepage tag to call SiteEntry assets from within your element code.
- Because a CSElement is an element, you use the render: callelement tag to call CSElement assets from within your element code.
- Because a template is both an element and a page name, you can use either of the above, although typically the render: calltemplate tag is designed to be used for templates. It encapsulates the functionality of render:satellitepage and render:calleelement as well as other features, such as parameter validation.
FatWire and its advantages.
What is FatWire?
FatWire is a web content management system tool .It generates personalized content in an easier way.
Please visit http://www.fatwire.com/home for more information.
Advantages of FatWire
1) Separation of design, structure and content.
2) The CMS provides a graphical user interface that allows the editor to create content, add images and multimedia files, create content schedules, and much more.
3) Easy generation of navigation items for placed pages.
4) Configurable access restrictions.
5) Dynamic content.
6) Decentralized maintenance.
7) Content scheduling.
8) 2 level caching mechanism.
9) Easy ways to create workflows.
10) Designed with non-technical content authors in mind
11) Options for dynamic as well as static publishing etc….
Introduction
Hi Everyone ...
For last 4.5+ years I am working on FatWire CMS .I have been struggling to find sample codes of FatWire on web but never got much help and thus creating this blog which will contain sample codes for FatWire /Webcenter sites development.
For last 4.5+ years I am working on FatWire CMS .I have been struggling to find sample codes of FatWire on web but never got much help and thus creating this blog which will contain sample codes for FatWire /Webcenter sites development.
Subscribe to:
Posts (Atom)