Content rendering

SEO is becoming more and more important. It's also the main reason for the built in content renderer. It's job is to render text components, checking for in-site linking url's. Let's say you're trying to link to your contact page, and this page does not exist? You could be in some trouble concerning search engines. Search engines, do not like 404's linked in-site. The content renderer detects such links, and converts them to uri components. So you will still see your uri like you've entered it, only the content rendere will have attached it to your default alias.

Page warnings

Whenever you have a false uri, or any other problem with your page, xswcms will detect those problems, and sum them up for you in a nice 'to-do' list. This way you can solve the problems, and tag them as 'handeld'. So when deleting a page, all other pages linking to it will put a new item in your to-do list. Don't be fooled though, xswcms comes with a new feature called 'IpSolver' which stands for Intelligent problem solver. When enabled, it will solve most problems for you, leaving notes in the page log for you. This way, most problems with components (forgetting to enter your preferences), and uri's (non-existing, modified) will be solved. This feature is optional.