there used to be a module for that function and it was pretty good by Chris Onyak no longer available.

What exactly do you mean when you say "more advanced front-end development"?

 

John, there are many ways to go about this, but it is highly dependent on how the site has been developed. Everything from theme code base/architecture to the modules being used for content layout and management. From a core DNN perspective, user roles and permissions in general are handled at a page level, module level and file/folder level. With a role-based security model, you can create as many roles as you'd like and name them whatever makes sense for your use case. Then, you can apply permissions by role or user, to a page/module/file/folder. This can control who can "view" or "edit" the object (page/module/file/folder).

That said, some modules add more granular permissions capabilities for various functionality, etc.

Furthermore, if you are using a structured content solution (e.g., 2sxc or OpenContent), you have even more capabilities for those in a role that is beyond simple content management. For instance, in 2sxc you can allow certain roles to be able to edit the templates associated with views. This would provide the ability for developers to be able to do more powerful changes to templates using HTML, Razor, CSS, etc.

For those needing to do theme or custom module development, this should be handled via normal DNN extension installation/upgrade capabilities and would be for super-users only.

I hope this helps. :)

Posted By David Poindexter on 5/9/2024 7:32 AM
John, there are many ways to go about this, but it is highly dependent on how the site has been developed. Everything from theme code base/architecture to the modules being used for content layout and management. From a core DNN perspective, user roles and permissions in general are handled at a page level, module level and file/folder level. With a role-based security model, you can create as many roles as you'd like and name them whatever makes sense for your use case. Then, you can apply permissions by role or user, to a page/module/file/folder. This can control who can "view" or "edit" the object (page/module/file/folder).

That said, some modules add more granular permissions capabilities for various functionality, etc.

Furthermore, if you are using a structured content solution (e.g., 2sxc or OpenContent), you have even more capabilities for those in a role that is beyond simple content management. For instance, in 2sxc you can allow certain roles to be able to edit the templates associated with views. This would provide the ability for developers to be able to do more powerful changes to templates using HTML, Razor, CSS, etc.

For those needing to do theme or custom module development, this should be handled via normal DNN extension installation/upgrade capabilities and would be for super-users only.

I hope this helps. :)

My answer would've been almost identical.  ☝🏽

 

I mean folks who are skilled in HTML and CSS and capable of designing and building their own pages. For example, we have a Young Adult "sub-site" within the portal and some of them would like greater ability to create sub-pages, add modules, and code. Those are functions we previously limited to admins.  

Yeah, the people who are more technical could have more permissions.  In the case of the content, if you're using structured content, giving them editing capabilities can allow them to also edit the HTML content templates. 

Thanks so much, everyone. What a great resource this forum is!

John 

You are welcome John - let us know if you ever need any additional help. This is a great community and there are great companies represented here to work with as well.