ResultsADXSTUDIO CMS supports the separation of content from style and behavior. Content entry is completely separate from presentation style. Presentation styles are defined based on location, document type, and any influencing application behaviors. All content is stored in XML and is rendered to output (HTML,WML, …) via application objects and XSLT stylesheets. ADXSTUDIO CMS does not place any limits on the templates that can be made to render content.
ADXSTUDIO CMS uses Active Directory® users and groups and all authentication is performed natively in Active Directory. Since the content hierarchy is also stored in Active Directory, all access control is specified by placing ACLs on active directory objects. All access control is enforced by the operating system.
ADXSTUDIO CMS also has the ability to use 'impersonation' which allows a web application to switch into the user context of the logged on ADXSTUDIO CMS user (an active directory account), and perform network operations with the user's credentials. For example, if you have a secure SQL application, simply create an integrated SQL account for the user and give them permission; there is no need to grant a generic IUSR account access to the application. To access the application within an application using ADXSTUDIO CMS APIs, simply call ADX.Impersonate() to switch to the user's context, then call ADX.RevertToSelf() to switch back to a generic IUSR user context. This is a powerful feature for building secure web applications.
All pages are delivered to clients on the fly. Although we do have the capability of exporting the content to a flat site, we highly recommend against this practice because it restricts future dynamic content or applications. If performance is a concern, rest assued that if you build your website with ASP.NET, ADXSTUDIO CMS's advanced caching capabilities will deliver a very high performance website. If you do choose to export your site to flat HTML pages, we do have this capability and could provide you with some code fragments to make your job easier.
Another capability that is not apparent in the existing demonstration website is the ability to export web content into Microsoft® HTML help format in a compiled .chm file. Internally we use this capability to compile our ADXSTUDIO CMS help files from CMS content.
Our default ADXSTUDIO CMS documents support four dates (Release, Expiry, Creation, and Last Updated). The default XSLT stylesheets respect release and expiration dates on all objects. Additional date fields can be added to the document model with ease.
Content contribution: ADXSTUDIO CMS has a very powerful API that deals with both the rendering of a website and the management of the data. It would be fairly straight-forward to develop an ASP page that could retrieve syndicated content from RSS, XML, HTML, or any other web source and insert it into the CMS.
Becoming a feed: It is even easier to develop an application that could serve out your content in many of the standard formats for content syndication. Since the content is stored in XML and not in HTML, you can have full control of the output format with simple XSLT stylesheets and minimal coding.
The source code for the class libraries is not provided. The class libraries implement all of our server controls. Developers have the capabilities of fully customizing the HTML templates that are output by the CMS. This can be achieved by providing parameters in the server controls, parameters to the XSLT libraries, providing a custom XSLT file, or even deriving custom classes from the existing web controls included with the CMS. Customers are provided with the source code for the XSLT libraries to assist in making these customizations. It is NOT necessary for customers to obtain the source code for the CMS class libraries as full customization is possible using these other techniques.
