The modx backend. A living nightmare?

    <!--Keywords:->
        <!--CV(singular/plural): Content Variable - A variable pulled from table modx_11site_content-->
        <!--TV(singular/plural): Template Variable - A variable pulled from modx_11site_tmplvars and-->
        <!--Item: A collection of variables describing a particular object. For example a document or a weblink.-->
        
    <!--Ideas:-->
        <!--00. Rewrite mutate_content_dynamic.php to create the whole content dynamically. Right now the overall structure is static html with inline php here and there to fill in contents.-->
        <!--    Rewriting it will make it possible to change the layout and its contents depending on role, userid, template and other things -->
        <!--01. Add a display_params table containing information about the overal layout of each variable (CV and TV) when it is display in a form -->
            <!--It might by necessary to store that information context sensitive. Don't know why, its just a feeling... -->
        <!--02. Treat the inclusion of variables context sensitive. A "Document" item will need other variables as for example a "weblink". -->
        <!--03. Allow definition of (content) items. Each item consists of any number of CV and TV -->
            <!--Example: "Image item" - cv_id, tv_image_url, cv_description, cv_title-->
            <!--New table: "content_item_groups": id, name, description, sort_order-->
            <!--Create dialog defining variable groups (fieldsets) for each item.-->            
            <!--New table "content_item_variables": Contains information about the variables used by an item, to which kategegory (fieldset) they belong and in which order they appear within the fieldset-->
            <!--Create dialog to assign CV and TV of a particular item and assign them to different groups (fieldsets). Also set sort order for those variables within any group.-->
            <!--Mission: Identical output to the static content template.-->
            <!--Possible use: Create an image item. Give it among other variables a title, a caption and a url. Now you can grab that information whenever you pull that image from the database -->
    
    <!--Questions:-->
        <!--Though each item has it's own set of variables that describe it, it will be necessary to to hide some variables depending on who is working on a particular item.-->
            <!--Restrictions could be applied to different roles as well as to individual users-->
            <!--Right now this is achieved by tools like managermanager or by hiding items through css-->
            <!--Idea: Restrict user access to -->
        <!--It might also be interesting to provide different standard content depending on the template