I downloaded tersus.web and started working with it.
A few questions regarding the current version of tersus.web:
1. When I run tersus.web with my own content, then the first page that is displayed is empty, even though the "Home" page (i.e. the page listed as "Home" in the horizontal navigation bar), is populated. Why is not that page being displayed?
2. I was disappointed that you did not include the Tersus homepage as a sample. When I downloaded tersus.web it was specifically because I wanted to see how you were doing
a) the autoscrolling newsbox;
b) dividing the page up into several, distinct text areas. (I - similarly - want my home page to contain several table cells, that each contain a teaser for an article with a "more ..." link that is linked to the appropriate webpage, where the article is continued (like you see on portals, news sites, etc.)
3. How do I control the space available for the "registration" link (next to the"login" link)? I want tobe able to replace the "registration" label by something more verbose, such as "register here to get the latest information".
4. How can I use the authorization mechanism to provide only a subset of the administration features to content managers, while preserving the full feature set for Super (i.e. myself)? I.e. content managers can only change the content of existing pages, but cannot add or remove pages from the website, or modify the type of the respective page.
5. I want to add pages that are populated from a database. I.e. tersus.web needs to populate that page using a database table and filling in some repeated pattern consisting of a mixture of text labels and display elements. Also I need a corresponding data entry page to enter the data into the database table. Obviously I know how to use Tersus to create such pages, but how do best integrate that with the existing tersus.web infrastructure?
Even though the current incarnation of tersus.web only has a very small feature set compared to CMS oldtimers, I am certain that a small number of volunteers could rapidly add many of the most urgently needed additional features.
Perhaps the most urgently needed support from tersus would be some documentation material that explains the overall structure of the tersus.web implementation and gives some navigational help especially for the adminstration side of things.
(Also I would use a different name, instead of tersus.web. If you guys want to make sure that the tersus.web CMS promotes the Tersus development environment, then how about tersus.CMS?)
For best results, use the Firefox browser..