Forum .LRN Q&A: Re: Renaming static portlets

Collapse
Posted by Caroline Meeks on
As I recall static portlets has some serious design flaws.  Top of my gripes with it are not using the content repository and having a limit of 4000 characters.

If I had time I'd like to rewrite/replace static portlets with a portletized view of an "edit-this-page" like CMS that provided richtext data entry, versioning and symlinks.

Then I'd write a UI to to allow group administrators to designate specific portlets' content publically visible and serve this content on separate non-portalized pages, perhaps outside of the dotlrn heirachy on the site-map. The goal is to give each class/club thier own public (or registered users only) pages viewable by non-group members. This is an important feature missing in dotLRN.

I actually think this would be pretty easy to do with BCMS.

Simple Use Case: Allow students to browse classes without joining. If the content of the "Class Info" was public we could link that page from the "Join a Group" page and allow students to browse course before they joined.