Configure Webpage


Webaptive lets you create templates out of any existing ASP.Net without having to embed third-party controls or make any other changes to the page itself. Content and properties of most ASP.Net web (Literal, Panel, etc.) and HTML controls (DIV, P, SPAN, etc. with "runat" attribute set to "server") can be managed through Webaptive CMS. To configure a web page for the first time follow the steps below.

Browse to the page on the web site that is configured to be in Edit mode and log in using the administrator account created during creation of the CMS DB. Then click on the "Enable CMS" button, which will launch a wizard that will step you through configuring the page.

Page Properties


The first screen lets you enter some basic information about the page, like Page Name (used to identify the page in various locations including analytic reports in Perfigure), ID (used with extended properties ), Default Menu Text (default text displayed in navigation menus , can be customized for various locales as explained in the manage content tutorial ) and a search engine-friendly URL for this page. The check box below lets you hide this page from navigation and/or exclude it from search results - this is typically checked for pages that are configured to be templates for creating other postings but do not contain any displayable content.

Pick Editable Fields


The box on the left lists the various elements on the page that can be managed using Webaptive. Most ASP.Net web and HTML controls are supported. To configure an element as editable, select it and give it a Friendly Name, then select the type of content allowed. The options for the type of content are Text Only, HTML, WebParts (Navigation controls) or Properties Only (visibility, style, image source, etc.). Depending on the type of element, not all options would be valid (e.g., an image tag would only support properties). Click on the ">" button to mark the element as editable. Repeat the process until all the elements you wish to manage through Webaptive are added the the "Editable Fields" list, then click the "Next >>" button to proceed to the next step. 

Configure Custom Widgets

 
Optional Step: Custom widgets are ASP.Net user controls whose property can be managed through Webaptive. For a user control
 to be configurable it needs to expose (public access modifier) a property of type string, contain a void method and have an empty ASP.Net placeholder somewhere in the body of the user control. The manage custom widgets option is not available when the "Enable CMS" wizard is run for the first time for a given page. Complete the wizard, then check out the page and click on the CMS Properties button under the Manage tab. Once configured, a content editor can specify a value of the property. Webaptive will set the property with the provided value and call the specified method before the page gets rendered. An example for a custom widget would be a "product of the day widget" where displayed product can be configured via Webaptive by setting a "product id" property of the user control. Once a user control is marked as a widget all instances of that user control on that page become editable.

Configure Extended Properties


Optional Step: Extended properties is a mechanism to allow for dynamic display of content via code. For example, in an e-commerce site every product could have an attribute like a "short description" that gets displayed in other postings like the shopping cart when that product is added to cart. Extended properties allows the content editor to manage dynamically displayed content from the product posting itself. Add extended properties option is not available when the "Enable CMS" wizard is run for the first time for a given page; complete the wizard then check out the page and click on CMS Properties under the Manage tab. Extended properties can only be used for web pages that are either configured to be not a template or as a dynamic template, not an internal template. To add an extended property start with giving it a name, select the type of content and click on the ">" button. The "Is Required" check box is reserved for future use. To consume the value of an extended property, set the value of the control (e.g., an ASP.Net literal) from code to the URL representing the location of the extended property (e.g., cms://ProductView?ID={0}/shortdesc where ProductView is the ID of the page and ID={0} is the dynamic posting parameter and shortdesc is the extended property containing a short description for the product).

Site Map/Taxonomy


The next step is to add the page to the site map. Site maps play a key role in navigation, content and security inheritance. Navigation menus can be created based on the site map such that it automatically updates itself based on changes to the site map. Content, security and work flow also can be set to inherit down from the site master posting and down each node in the site map. After selecting the position of the new web page in the site map, click "Next >" to continue to the next step.

Security and Workflow


The option to inherit security and workflow would be disabled if there are no postings above it in the site map, which would be the case for the first web page being configured. Click the "Next >" button to select workflow and configure security.
 
If there are no workflows a new one will have to be created before proceeding. After selecting the workflow, click "Next >" to configure security for the selected workflow.


Each step in the workflow is owned by a group. Only users belonging to that group and administrators would have the rights to perform the action required to complete that step in the workflow. If you haven't created the groups yet, click on the "CMS Console" button under the Administration section of "Main Console" to create users and groups, and then click on the "< Previous" button and then "Next >" to refresh the list of groups. After selecting a group for each step in the workflow, click "Next >" to proceed to the next step.

Template Settings


In Webaptive a web page can be configured as one of three types. A page can be configured as not being a template (first radio option) - this will still allow content within this page to be edited, but you will not be able to create another posting/page using this page as a template. Log in or shopping cart would be a good example where you might not want to create multiple postings based on the original web page.

A page can also be configured to be an "Internal posting" (the first option under the second radio button). Any number of new postings can be created and added to the site map that are based off this web page. Most content-only pages on a web site (e.g., contact us, about us, news) can be created based on one or two templates. For example, all of these tutorials are based off a single web page configured as an internal posting.

The last option (second option under second radio button), configures a page to be a "Dynamic Posting." This is one of the unique and very powerful features of Webaptive. Dynamic postings are postings that are automatically created based on a URL parameter - in most cases a parameter that the code behind the page already recognizes as the key differentiator. For example, consider an e-commerce web site where the products are created within a separate inventory system. The products created within the inventory system are queried by the e-commerce site and listed by category; the product postings are not created directly within the CMS system. Webaptive can be configured to automatically create new postings as a certain parameter (say productid={0}) changes in the URL. Webaptive will allow content editors to add varying content for each product page as the product id parameter in the URL changes, without the need for any custom coding or API calls and with zero impact on development.

Tip: Choose carefully - this is the only setting that cannot be changed after the page is configured. Only pick the "not a template" option if you are certain that the web page will never be used for creating additional postings. Picking the "Internal Posting" option will still allow you to directly edit the web page content and allow you to create additional postings based off it.
   
Valid XHTML 1.0 Transitional Valid CSS!
 
 © Copyright 2011 Striquent LLC. All rights reserved.