Plugin vs module

Easy Docman List ships as a content plugin and an optional site module. Both render the same DOCman output through the same layout engine.

Content plugin (required for shortcodes)

• Name: Content - Easy Docman List (plg_content_docmanlist)
• Use when: documents belong inside an article body, landing page copy, or blog post
• How: type {docmanlist} shortcodes with category IDs and optional keywords
• Defaults: plugin parameter tabs apply to every shortcode unless overridden

Site module (optional)

• Name: Easy Docman List (mod_easy_docman_list)
• Use when: lists belong in sidebars, footers, home page positions, or demo pages
• How: create a module instance, pick categories, assign to menu items
• Inheritance: empty module fields mean use plugin default for that setting
• Wrapper layouts: Default, Card, and Bare module chrome (Joomla module layout, not DOCman layout)

Important naming note

The module stores DOCman layout in docman_layout so it does not clash with Joomla module layout (layout for Default/Card/Bare wrappers).

Both on one page

Version 5.0.0 supports a shortcode block and one or more modules on the same page. Each instance gets its own .edl-root wrapper. CSS and JS load once per page.

Which should you use?

• Articles only: install and enable the plugin
• Sidebars and global download boxes: add the module
• Large sites: use both; set sensible plugin defaults, then override per module or shortcode