The article tells about the changing scenario in the development of web sites. The companies are no longer looking for single solution providers only, but multi solution caterers who would help in the expansion of the business.

Are you using a Xanthia theme? While the basic installation, insertion of pntitle.php (note little "t") in the directory of the modules, insertion of pnTitle.php (note capital "T") in the includes directory, and header modification are the same, calling the title hack function will be done differently.

In a recent review of the progress that Content Management Systems (CMS) are making with regards to Search Engine Optimization (SEO), it seems that dynamic content is beginning to get proper attention. Most CMS platforms still neglect to address the growing concern for search engine (SE) friendly URLs and unique Meta Tags. A few, including PostNuke, now offer webmasters a way to move up in the all-important SE rankings.

In addition to pointing out the benefits of Mod_rewrite and htaccess, Kevin Kantola makes reference to MirageLab's own SEO article for those looking for assistance in making their own PostNuke sites SE friendly.

Read more: Content Management Systems Eyeball SEO's
by Kevin Kantola on WebProNews.com.

The ability to use "search-engine-friendly" URLs is something that many CMS platforms fail to accomodate. The out-of-the-box installation of PostNuke does not offer this feature. There are a few themes available that incorporate ShortURLs, each with it's own handler function. No centralized ShortURLs manager exists to syncronize URL translation across themes, although existing themes may be easily adapted for ShortURL usage.

After a long and arduous search for the reason ShortURLs were not operating on my homepage (labPanels, currently). The URLs were translated into phtml links correctly on other pages, such as Downloads, or the forum (phpBB_14, currently). The URLs were NOT, however, translating in any API compliant modules (later versions of Semantics, OpenRealty, labPanels, and pretty much every client module I've developed in the last two years).

The culprit turns out to reside in the site root index.php file. The code relies on pnHTML to render pages, although it did not do it in the last few core releases. With all the discussion about alternate rendering mechanisms, this is an oddity.

After looking long and hard for a "Contact Management" module, and finding only a long series of components designed to handle publishing your contact information or the contact information for your company or site, you are almost ready to give up and rely on Outlook or whatever contact list manager your webmail offers.

You need a contact manager that manages your contacts. You need it to discriminate between private and business contacts. You need it to provide for not just email addresses, but also phone numbers, websites, and a host of other information that you need to be able to decide on later. It needs to be open ended. It needs help you network.

You need a 6 degrees rolodex, a Friendster that doesn't require the other person to be a member.

You need labDossier.

Homepage: here
Manual: here
Demo: here (uid: demo, pwd: demo)
Module Library Entry: here
Download: here (requires registration and subscription)
FAQ: here

One morning you come to work and you notice that the phone number and other contact information on your company’s website are incorrect. Having incorrect information displayed on your website is hurting your business by the minute. You pick up the phone and call your webmaster. Unfortunately, you get his answering machine telling you he is going to be on vacation for the next two weeks. Welcome to the reality of eBusiness...

The latest release of labPanels has been implemented on both Ivory Tower and MirageLab. The organizational GUI used to manipulate homepages is made full use of throughout both sites. The dynamic use of any available block can be seen on my homepage, the MirageLab Modules page, and the labPanels Homepage.

Featured capabilities:
* Set up unlimited "homepages" comprised of available blocks (active and inactive)
* Organizational GUI displays each block in context with available options.
* Move blocks left/right and up/down through standard sequencing arrows.
* Align blocks in the same row to enhance content width
* Align blocks in the same column to extend content
* Rows line up independent of each other to stack content
* Change individual block displays by switching to a different block position (l, r, c, etc.).
* Set a different theme for each homepage
* Edit block options via a direct link
* Set optional preview text to display in homepage menus
* Set optional boilerplate content to display above blocks
* Organize sets of homepages using labCategories

Manual: here
Download: here (free to premium subscribers, $39.95 to purchase)
Forum: here
FAQ: here

labIPNtrigger is THE answer to integrated Instant Payment Notification (IPN) for PostNuke. IPN is what ecurrency services like PayPal use to confirm online purchases instantly. Standard PayPal transactions, sent from existing modules like PayPalCart, provide a URL for PayPal to return visitors to who cancel their purchase, and a URL to return them to after a completed purchase. Currently unused by PayPalCart (and others) is a third URL, the return_url, is used by PayPal to send secure transaction confirmations to. It can also send specific transaction information, like shopping cart contents, subscription details, order total, taxes, fees, etc.

labIPNtrigger functions as the receiver for this IPN information. By adding the labIPNtrigger URL to PayPalCart as the PayPal return_url (link for details), your customer order information can be collected and used on your website.

Read more or go directly to the labIPNtrigger homepage!

You want search engines to see your pages as unique. If every page of your PostNuke site has the same page title, meta keywords, and meta description, many search engines will consider it all the same page and only include one instance. While content may be king, good search engine optimization will be necessary to keep the king on the throne.

Maybe you've tried the pnTitle hack. If not, you should. I'm going to give you a reason to. This hack changes the site root header.php file so that the page title is dynamically based on individual pntitle.php files located in module directories. If a file is present, it typically returns a title based on the content category or section, although some just display a general module title, and others will build the title based on individual items viewed. Anyone navigating the site will be aided by the feedback they get in the form of the customized site title. Search engines will like it even better.

When Technivore released pnMeta, site owners were given an alternative to the distributed file structure of the pnTitle hack. Now, sites can have not just dynamically generated page titles, but also dynamic meta keywords and description. However, the customization only drills down to the module level, leaving behind some of the power of pnTitle.

Until now, these were the choices. Sites could have one or the other. We know you want it all, because we did to. That's why we wrote a revised header.php file to combine the dynamic nature of both the pnTitle hack and pnMeta. Simply install pnMeta using the standard module installation (regenerate/initialize/activate). Then, upload all of the pnTitle hack files except header.php. Finally, upload our revised header.php file, and start customizing your meta data for each installed module via pnMeta. If the revised header.php file does not retrieve a title from pnTitle, it will use the one returned by pnMeta. As other pntitle files become available for additional modules, simply upload them; the revised header.php file does the rest.

labDocument is a document creation, collaboration, and management tool. Verbiage intended for use as static printed material can be built online by multiple users simultaneously. Each document contains one or more chapters/sections. Each of these contains one or more pieces of block content that can be reordered using the labDocument GUI.

This module is meant to perform as a stripped down version of Content Express, with no innate word processing GUI, no internal image support, and no hyper-dynamic menu generator. labDocument does, however, offer the unique capability to re-order chapter verbiage without having to edit text, thus allowing simultaneous collaboration between users even within the same chapter, if need be.

labDocument was written to facilitate creation of legal forms and contracts based on roughly categorized components of verbiage. Next phase plans include more printable page options that support site specific CSS, and company letterhead creation.

Download: here (registration and subscription req'd)