Todo List

Modified 8 January 2009 by Per Cederberg (per)

Note: This list of scheduled work items is currently incomplete. More items will be added soon.

Admin Interface

Improve Text Editor (Version 1.1 or later)

The formatted text editor should probably be converted into a WYSIWYG type of editor and merged with the HTML editor. HTML tag cleanup and such would be required of course.

Multiple Language Support (Version 1.1 or later)

Multiple languages should be supported in the administration site(s). Current target languages for the 1.0 release are English and Swedish.

Predefined Document Properties (Version 1.1 or later)

Many types of content are highly similar across sites, such as articles, products, etc. The document properties for these should be easily available when creating new sections, allowing them to be modified as needed.

Simplify Local Linking (Version 1.1 or later)

When editing documents and adding local links, it would be easier to select the document from a simple tree view than to enter the URL (as now). Also, selecting the document could produce a link to the document ID, making it possible to move it later on.

Internals

Aliases & Redirects (Version 1.1 or later)

Support for web page aliases and redirects should be added. This will facilitate keeping URL:s working on site changes. Also, it could be useful for providing shorter URL:s to selected content.

Add Search Function (Version 1.1 or later)

A capability for quick and efficient free text search in the content should be added.

More User Preferences (Version 1.1 or later)

A batch of user preferences must be added to the database. These include timezone, language, IP authentication, etc. It should also be possible to store and retrieve any set of name-value pairs for users.

Add Calendar Support (Version 1.1 or later)

Calendar events should be easy to add and display in a web page. It is possible that this can be handled by extending the document object type a bit (with a date field), but the exact requirements for calendars must first be established.

Generic Content Relations (Version 1.1 or later)

Content object should be possible to structure in generic relations, not just the current parent-child relation. Generic relations would make it possible to have efficient support for cross-section content categories, related article functions, etc.

ACL Validation on Documents (Version 1.1 or later)

Documents should be able to have individual ACL:s, if required. An efficient implementation should be possible to achieve by storing a relation for each content object to the ancestor object that contains the current ACL. Upon login, the id of all content objects that a user has access to should be calculated and then used in all further content searches.

JavaScript Interface (Version 1.1 or later)

A standard JavaScript interface to LiquidSite should be created, allowing easier inclusion of Admin functionality into a normal web site. Also, some dynamic web applications should be easier to integrate into web sites in the JavaScript form than as FreeMarker templates. Efficiency on the web server site should also increase markedly, as should the experienced speed.

Other

Reference Manual (Version 1.1 or later)

The reference manual must be completed. The manual should cover at least the terminology, site and content views, basic workflows and security concerns.