Sakai 2.9 brings with it a new look in the tool we call the neoportal.
One of the biggest changes was that up to release 2.9.0-b07 the skin (css) files were different and replaced by entirely new skins from various contributors. - SAK-22236Getting issue details... STATUS .
The early 2.9 skins and look (neo-default29)
The current 2.9 skins and look (neo-default)
As you can see side by side, many things were shifted along the top bar, the background was removed, the bottom was detached from the main frame, the left buttons (and all buttons) just look better. However what this means is that any super early adopters will either have to maintain unsupported skins or switch to the new skins which work much better and have gotten much better user feedback overall. The neo-default has been updated to these new skins in reference, while the previous has been moved to neo-default29.
A skin guide can be found at Sakai 2.9 and Sakai 10 skin guide.
Important (new) properties
To enable the "Neo Portal Skins" you set this property "portal.templates" to neoskin. This is the default
The neo portal will add a prefix to the directory name for the skin of "neo-" - so the tool.css URL when the neo portal is in effect will be
This property also switches which render engine is activated in
The previous skin for pre 2.9 is still present in the default skin directory and anything without the neo-prefix is considered an older skin and less supported.
This property for a prefix (if you wanted to change it) is also configurable with the property "portal.neoprefix"
To get back to the non neo-prefixed skins (the old skins) Just set the portal.templates to something else.
Setting this property will prevent appending the neoprefix (neo-) to every skin directory. By default the property skin.default is still equal to "default" so if you have neoskin as the portal.templates the default is "neo-default" if you don't the default is "default" as it was in 2.9. The skins are in the same place as before and still deployed to the library directory (which is also still configurable with the skin.repo property). https://source.sakaiproject.org/svn/reference/branches/sakai-2.9.x/library/src/webapp/skin/
See - SAK-20713Getting issue details... STATUS for additional information. Currently the skin doc hasn't been updated to include new information for 2.9 but there are plenty of example skins (neo-gen-u, neo-example-u). But you should be able to use previous techniques as well as developer tools in modern browsers to update this new skin for your university.
It's expected we will eventually drop all support for the older neoskin as well as the previous default in a future release, this is just left in-case you want to upgrade to 2.9 but be able to hold off with the new skin. Some features will not function with the older skins.
These properties control the top dropdown menu. By default they are set to the appropriate tool id. If you set them to "none" instead, no link will appear. The last property for portal.use.tutorial is true/false and will display or hide the tutorial feature.
These two properties control the neochat widget of the portal. By default in 2.9 this is set to false (chat is turned off) as this is still an experimental feature which we are testing. We recommend leaving neochat disabled in a production environment until performance and usability tests are completed.
The mobile detection in 2.9 has changed. Tablets are considered regular devices as they have larger screens and are generally more capable and given a full screen view.
The property below is the default
Old and new Properties defaults