Professional DNN7: Open Source .NET CMS Platform
by Shaun Walker, Bruce Chapman, Cathal Connolly, Peter Donker, Israel Martinez, Charles Nurse, Chris Paterra, Clinton Bland, Ashish Prasad, Nathan Rover, Mitchel Sellers, Dennis Shiao, Will Strohl, Erik van Ballegoij, Scott Willhite, Ralph Williams Jr.

Modules
WHAT YOU WILL LEARN IN THIS CHAPTER
- Adding modules to pages
- Sharing modules across multiple pages
- Configuring module permissions
- Scheduling module visibility by date and time
- Installing modules
- Configuring the HTML rich-text editor
DNN can be extended in several ways. The areas where DNN can be extended are known as extension points. DNN has several extension points such as authentication providers, skins/themes, and language packs just to name a few. Probably the most popular extension point, however, is the one known as “modules.” DNN is built on a modular architecture, and as such, developers can leverage the platform architecture to create reusable, modular units of functionality. This chapter provides a high-level overview of modules. If you are looking for more in-depth information and guides for creating your own custom module, check out Chapters 13 through 16.
WHAT IS A MODULE?
A module is a reusable, plug-and-play piece of functionality. We often use the analogy of a module being to DNN what an app is to an iPhone. It's a way to extend the functionality of the framework with whatever functionality you desire. Examples of modules could be photo galleries, blogs, rotators, forms, and so on. There can be multiple modules on a page and even multiple instances of the same module on a page. It's very common to see multiple HTML modules on a single page.
From a developer's ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access