Introduction

The Layout is implemented using XML data from the database, variables from the running process, and a set of XSLT define in your layouts and internal extraneous XSLT definitions as offered by the core and different extensions.

XSLT is used to transform the XML data into an actual page that can be display in a website.

This page gives some information about XSLT and different features available in that language.

[Note: I'm writing this before doing the actual implementation of the data and therefore it is likely to change by the time it is fully implemented.]

At the ...

WARNING

I moved this feature under the Editor entry because what I talk about here are the widgets of the inline editor offered as the editor plugin. For this reason I marked this page as Details only.

Some of the content of this page needs to be duplicated somewhere else and then this page removed. There are many important points such as the security entry at the bottom.

Widgets versus HTML Code

We want a way to make it really easy to create the HTML output.

At first I was thinking about forms, however, to make it really easy for the entire output we want to support widgets. ...

More about groups, actions, and permissions is defined here:
Content Object in Cassandra (Content Tree)

When viewing permissions as sets, the decision on whether a user has permission to do something is easily taken: the set of permissions intersected by the set of groups the user is part of must not be empty.

However, there are cases when a certain action may require multiple authorizations and if all those authorizations are not satisfied, then the user cannot take that action. This is represented by multiple sets of permissions (realms or categories of permissions.)

A good example ...