Documentation Videos Modules Stats back to home

Web Pages

Web pages is at the heart of managing content in the system. It's available in the main nav bar at the top of the web console.

It's on the site at: site/pages

A detail page is at: /pages/detail/id

The preview, only available when logged in, is available at: /pages/preview/id 

A video walkthrough

Check out this video walkthrough

How it works

The site map

On the left side is your site map.  The pages are hierarchical.  Want to add a new page?  Simply click the page that will be the direct part and then on the right side, press "add child."

The meaning of the icons in the sitemap

• page - If it's a page, it just means it's a normal page
• page with an x on it - means that it is an inactive page
• a home - means that it is the root of a "subsite." Subsites can be articulated in the setup area of the system

The meaning of the buttons

• Want to move a page? Click the "move" button and you can pick a page on the left under which you would like to move it.
• Delink - will delink a page from its parent and orphan it.
• Preview - will show you the page in the "preview" mode

The meaning of the fields

• Title - pretty obviously the title of the page
• Invisible - clicking will make it unseen everywhere in the site but you'll still be able to preview it.
• URL - will redirect the page.  For example, if you enter http://www.google.com into the URL upon clicking to the page the user will be redirected.  Another example is if you want the page to be for a special module/controller like let's say, for example, "classifieds," you would need to put "/classifieds" into the URL field
• Template - these are master pages that are custom to your site/install. They give you an ability to have different layouts with multiple content areas in them.  Master pages must be added as records in the Console and they must be actual pages that live in the site.
• Start and end dates - controls when a page will start or stop being shown.
• Sequence - allows you to override the default alphabetical sort order.  For example if you wanted the "Zither" page to show before the "Aardvark" page, you'd give it a lower sequence number. 
• Run .NET code - means that the page will process code that you can put into the "source" of the rich text editor.  You would need to do this if you are using any of the customer BRT controls in the page.  For example, maybe you're calling a console form or a querylist?  If so, you'd need to check this box for the system to process the code.
• New window - clicking will pop a new window when the user clicks to the page from the site map
• Page Access - This controls who can see these pages and nodes on the front end.  Meaning, let's say you wanted to restrict access to a node of your website?  Maybe you have an area called "members."  You can create a user group called "members" and then say that only people that are logged in (via the front-end) and are part of this group will be able to access this page/tree.  The front-end has a login available function at /site/login.  This will enable someone to log in to the front-end of the site against the console users object.  Then, as they are browsing the site, we always know who they are and you can create custom protected areas.  Also in "page access" is where you can assign what master pages this page and its children will have access to.  So, for example, let's say you created a subsite and that subsite has different master pages - different templates - different layouts.  You'd want that subsite's node to only have access to its templates/master pages.

Who can manage web pages?

Administrators, by default, can see the link to pages but you can choose who can see the web pages link under USER GROUPS by going to the groups' detail page and choosing the "user group action" "can edit web pages."