1. What problem are you trying to solve?
When organizing Web Content in Liferay using a folder-based structure, content authors expect that creating an article inside a folder should automatically adopt contextual properties that match the purpose of that folder. However, the current behavior requires editors to manually configure several settings every time they create a new article:
-
Categories must be re-selected manually, even if the folder clearly represents that category/topic.
→ This creates repetitive work and increases the risk of selecting the wrong categories. -
The folder for storing attachments (Document Library location) must also be selected manually, even though articles within the same folder typically share the same storage area.
→ This leads to unnecessary repetition and inconsistent file organization.
Overall problem:
Liferay Web Content Folders lack rich configuration options, leading to redundant actions, inconsistent content setup, and reduced editorial efficiency.
2. What is your project about?
The project focuses on enhancing the authoring experience and content governance in Liferay by introducing advanced configuration capabilities for Web Content Folders.
Applicable scenarios include:
-
Corporate Intranet portals
-
Public-facing enterprise websites
-
Government portals
-
News and media content platforms
-
Any content-heavy site requiring structured and consistent editorial workflows
These environments often contain multi-level folder hierarchies where authors expect context-aware defaults during content creation.
3. What solution are you proposing?
Introduce “Advanced Folder Configuration” for Web Content Folders, enabling administrators to define default values for articles created within a specific folder.
A. Default Metadata Configuration
1. Default Categories
Allow each Web Content Folder to specify a predefined list of Asset Categories.
Options may include:
-
Apply automatically
-
Allow overriding (authors can edit)
-
Inherit from parent folder
Benefit:
Eliminates repetitive category selection and ensures consistent classification.
2. Default Tags
Similar to categories, folders may define default tags that are auto-applied to new articles.
3. Default Structure and Template
Allow folders to define:
-
Default Structure (DDM Structure)
-
Default Template (DDM Template)
When authors create an article inside the folder:
-
The editor automatically opens with the folder’s predefined structure/template
-
No manual selection required
Benefit:
Faster content creation and fewer configuration errors.
B. Default Document Storage Mapping
Default Document Library Folder for Attachments
Allow each Web Content Folder to map to a default Document Library (DL) folder.
All images and files uploaded during article creation will automatically be stored in that DL location.
Usage examples:
-
“Corporate News” folder → store images in
/IR/Images/News -
“Financial Reports” folder → store attachments in
/IR/Documents/Reports
Benefits:
-
Eliminates repetitive DL folder selection
-
Keeps file organization clean, consistent, and predictable
-
Avoids misplaced documents and media clutter
C. Optional Additional Enhancements
(Non-essential but potentially valuable)
-
Default Expiration Date / Review Date
— e.g., articles in an event folder expire after 180 days -
Default Permissions Template
— automatically apply predefined permission sets -
Default Metadata Profiles
— helpful for news/media portals requiring standard fields per folder
4. Overall Benefits
40–60% faster content creation
No repetitive selection of categories or file storage locations
Consistent classification and media organization
Reduced editorial mistakes
Improved user experience for content authors
Better governance for large content repositories
5. Example Use Case
A site organizes its news and IR content using folders:
-
/Corporate News
-
/Disclosures
-
/Financial Reports
Today, creating an article inside Disclosures still requires:
-
Selecting category “Disclosure”
-
Selecting a structure/template for disclosures
-
Browsing to the correct DL folder for attachments
With the proposed enhancements:
-
Creating an article inside the folder automatically applies all defaults
-
The author only needs to write content — everything else is pre-configured