DNN ShortCut allows you to create keywords that link directly to another tab within your DotNetNuke portal or to an explicit URL. This is similar to "AOL Keywords" where marketing friendly keywords are used to link to specific pages within your website, even hidden pages that do not appear within your menu navigation. A simple Administration screen allows you to define your ShortCut keywords and where they link to. Once defined, shortcut can be integrated into your website in any of three ways (see below).

 

 

Three ways to integrate ShortCut within your DotNetNuke Portal

• Skin Object - Place the ShortCut skin object on your skin, allowing you to place the Shortcut interface on every page of your website.
• Module - Place the ShortCut module on any page within your website, this is a module that is exactly like the ShortCut skin object, to be used when the administrator only wants to place the Shortcut interface on certain pages.
• HTTP Module - Install the HTTP module that handles "www.domain.com/shortcut" directly referencing your shortcut without an interface.

Defining ShortCuts

 

Defining your ShortCuts is easy.  Once you have placed the ShortCut module, you can access the "Define ShortCuts" interface.  The following example shows 3 ShortCuts defined.  From here, you can create a New ShortCut, or click on the ShortCut name of an existing ShortCut to edit it.

 

 

Here is an example of an individual ShortCut that links to another page within this website:

 

 

 

Using ShortCut as a Skin Object

 

Use the provided skin object [SHORTCUT] to place the ShortCut interface on any page using that skin.

             

You have control over the "ShortCut" caption, "Go" button text, and all 3 CSS styles (caption, textbox, and button) using the ShortCut Configuration interface.

 

Using ShortCut as a Module

 

If you only want the ShortCut interface to only show on one, or certain pages within your portal, use the provided ShortCut Module that you can place just like any other DotNetNuke module.  This interface is exactly like the ShortCut skin object, and behaves the exact same way.

 

* You must place this module on a page within your portal to get to the "Define ShortCuts" and "ShortCut Configuration" administrative interfaces.

 

Using the ShortCut HTTP Module

 

By installing the provided HTTP Module, you can enable direct URL to your ShortCuts. Create dedicated URLs for specific areas of your website making it easier for customers to go straight to a particular page. Examples:

 

www.domain.com/support

www.domain.com/sales

 

www.domain.com/customer_name The ShortCut HTTP Module works by creating a directory for each defined ShortCut much like Child Portals work.  The ShortCut interfaces completly manage these directories (creating,editing, and deleting), and nothing has do be done manually.   If you plan on having allot of ShortCuts and don't want to create so many directories in the root of DotNetNuke, there is a ShortCut Intermediate Directory feature that confines your ShortCut directories beneath a single directory.  If you are using this Intermediate Directory feature, then the URL must match the directory structure.

 

ShortCut Configuration

 

ShortCut can be configured by placing the ShortCut Module on a page, then clicking on the "ShortCut Configuration" link. This interface allows you to control almost every aspect of ShortCut.