Role Based ACL
This talk sidesteps the 1.5 approach to ACL so we can discover the richer approach and new possibilities of the 2.5 ACL. The ACL and its components will be explained from a fresh perspective that might provide the missing pieces for those who have yet to fully grasp it.
More important is how we apply the ACL. A role-based approach allows us to deliver to our clients a variety of roles for managing site content. Image each staff member seeing a different set of options in the backend based upon what roles have been assigned to him or her. This allows us to deliver a CMS that is tailored to the client’s needs and simpler to use for those managing content.
Issues covered:
• An overview of the new ACL – explained from a 2.5 perspective
• What are role-based groups and what do they approach buy us?
• How to configure roles in the ACL
• Setting up the backend to display differently for each role
• The important role of “user manager”
Randy is the web architect at Careytech Studios. In 2012 he launched the iCue Project (improving the CMS user experience) with the goal of developing best practices and Joomla extensions that will improve the CMS user experience from the client's perspective. With a background in software engineering, Randy appreciates Joomla! for its infrastructure which leverages object-oriented design and the MVC design pattern. Having worked also on the business side of the web equation, he is quite conscious of the importance of business goals and of the perspective of the CMS end users.