The basic concept behind the functionality of a CLE is that users control their own sites; for example, they can choose which tools to include in the sites they create. The application treats users as adults and enables flexibility through choice. The tools include chat, forums, wiki, polls, Google-like search capabilities, and others—with more tool options with every new version of Sakai. Numerous tools enhance group formation, allowing for intuitive interaction (hence the word "collaboration" in Collaboration Learning Environment).
The range of tools is rich indeed, especially if you include all those contributed by the energetic and motivated Sakai community. Many local deployments have specialized tools for which they develop their own enhancements. They then contribute these extra tools, software for connections to external systems, and various other new features back to the community. As Sakai grows in strength, the number of extras is increasing explosively. The Sakai Foundation web site mentions at least 20 extras and the Foundation's source code repository has around 120 contributed directories.
Sakai was designed with a framework that significantly simplifies the creation of tools. Developers do not have to reinvent the wheel for fundamental services like finding a user's name, managing a site's look and feel, or internationalization. There are strong, well-established lines of support for developers, including style guides, best practices, a programmer's café, workshops, and central quality assurance (QA), throughout a development project's full life cycle.
To help organizations decide which tools to deploy in their production environments (for example, a college campus), which tools to start looking at for future use, and which to retire, each tool is assigned a status:
Core—Tools with which the community has a great deal of experience and is confident about their robustness, stability, and scalability.
Provisional—Tools with which the community has less experience or which are becoming obsolete. They are disabled by default.
Contrib—Tools with which the community has little experience and which the QA work group does not recommend for broad usage in a production environment. Contrib tools are available, separately from the release, in the Contrib area of Sakai's source repository.
Watching the codebase over time, you see a convection effect where contrib tools move to provisional, are thoroughly tested, and move to core; and then older core tools move down to either provisional or are pensioned off. As time progresses, there is a quality convergence—the software gets thoroughly debugged first by a team of dedicated testers and then by real-life high-scale deployments. In the end, the user has more choices and sophistication in the toolset. The extra choice of tools costs more server effort. Luckily, due to the trend known as Moore's law, servers double in computational power roughly every eighteen months. The end user thus directly benefits from a scalable framework, an increasingly functional-rich toolset, and ever-improving server specifications.