sakaiproject.org workgroup portal
- Former user (Deleted)
Below are screenshots of three experimental views of sakaiproject.org as an implementation of the Sakai workgroup portal. The workgroup portal approach permits one to expose multiple sites to anonymous users by adding to sakai.properties the gatewaySiteList setting which takes a comma-delimited string of siteIds . In this simple example, I have exposed two project sites called "home" and "downloads" in place of the usual !gateway page. In each site I added both the .anon and .auth roles and gave each the site.visit permissions I then added both the wiki, resources and site info tools (each of which is not exposed to anonymous users). I then added several pages of content to the wiki and exposed each page individually using the web content tool (sakai.iframe). I stored the board member images in resources and added content.read permission to the .anon role. Other tools with *.read permissions such as announcements, calendar, messagecenter can also be exposed to anonymous users on these pages. Finally, each site utilitizes the default-horiz skin to run the menu horizontally under the blue bar. Additional project sites representing logical divisions of the information we wish to make available to the general public can be added using the same approach.
Obviously, the key here is identifying consumers and providing an information architecture that meets their needs. But I am convinced we can deliver public-facing information using Sakai by implementing the workgroup portal approach. The bumps we experience along the way will spur further innovation resulting in a more powerful and useful application.
