Don’t Let This Module’s Name Mislead You!
ExpressionEngine’s “Pages Module” is a special-case solution to some common publishing rule exceptions and should NOT be confused with eeSiteKit’s or EE’s normal content structure, URI structure, or creation of web pages.
ExpressionEngine Pages Module Use In eeSiteKit
Pages Module Recommended Use
A “URI” is everything that comes after your domain-name and TLD (Top Level Domain). Basically: asitedomain.com/URI —> ...
By default, ExpressionEngine’s “Pages Module” allows you to create almost any URI for a “page” you want. This has the potential to create some issues from time to time as EE has some words that have restricted use in your URIs, and there are some words that eeSiteKit may be using to trigger specific things in your URIs. That said, these instances are typically rare and you should be able to use the Pages Module pretty freely within an eeSiteKit site.
Still Experimental: At this point, the use of the Pages Module within eeSiteKit is somewhat experimental. We have included coding within the kit for the correct rendering of web pages using the Pages Module URIs, and have done some preliminary testing with the search results, page-titles, tell-a-friend, category headings, breadcrumbs and print systems and all appears to be working, but its possible we missed something. We ask that when you do use the Pages Module in your site, that you do a little testing with your URIs to make sure they are working for you.
When in doubt, you can always assign a Pages Module entry to a category as a back up, although this could create a duplicate URI for the same content which may or may not be a concern for you.
When To Use The Pages Module: You’ll find we use the Pages Module in our sites for the Privacy Statement, Terms of Use and other odd pages that don’t have an obvious channel or category within the site. We tell our clients that its a great tool when they want a special short “memorable” URL they can tell their friends about; great for special promotions:
http://asitedomain.com/water/
http://asitedomain.com/auction/
http://asitedomain.com/tickets/Other than that though, we encourage our clients to use eeSiteKit’s main channel/category/entry-title based structure.
Pages Module URIs Are Not Multilingual Ready: Sadly, we’ve not yet figured out how to get the Pages Module’s URI system to translate as we have with the rest of eeSiteKit’s URIs. This may be a consideration for you. You could still have multilingual content in a Pages Module entry, and eeSiteKit will display it, but we can’t swap one URI for another (switching between languages) for you at this time.