The integrated portal model
CPG-Nuke packaged capabilities expected by early community portals: content publishing, user accounts, navigational blocks, modules, themes and media features. Exact availability varied by release and configuration, so this map describes capability areas rather than claiming a universal version-specific checklist.
Historical feature areas
Publishing
News and page-like content presented through a portal homepage and navigational blocks.
Accounts
Registration and user profiles supported participation across community features.
Discussion
Forum-style interaction was a central part of many portal deployments.
Photo galleries
Coppermine integration distinguished the project for media-oriented communities.
Modules and blocks
Site owners extended navigation and functionality through modular areas.
Themes
A theme layer changed the visual presentation of the portal.
Translate old features into modern requirements
| Legacy capability | Modern question |
|---|---|
| Portal blocks | Can editors compose reusable page sections with governance? |
| User accounts | Does the project need membership, SSO or only editorial users? |
| Forums | Should discussion be native, integrated or hosted separately? |
| Gallery | How are media metadata, transformations, rights and delivery managed? |
| Modules | Who maintains extensions and verifies compatibility? |
Frequently asked questions
Why was the old CPG_features.htm URL restored?
Historical backlinks point to that subject. The old URL now redirects in one hop to this relevant, safe reference instead of an unrelated homepage.