Extend site-settings.json Support for Additional Site Configurations in Site Initializers

Product Ideas
1

What is the problem you are trying to solve?

When using a Site Initializer to provision a site, there is no way to seed site-level configurations (site name translations, descriptions, virtual host URLs, .etc).

Currently, site-settings.json in Site Initializers supports only a limited subset of site configurations.

As a result, after site creation, administrators must manually configure these settings from the Site Settings UI, which creates additional operational overhead and makes environment provisioning less reproducible.

What is your project about? (e. g. Intranet, Partner Portal, Enterprise Website, etc)

Enterprise public-facing websites built on Liferay DXP, using Site Initializers to fully automate site provisioning across multiple environments (DEV, UAT, PRD).

What is your proposed solution? (optional)

Extend site-settings.json support to allow additional site properties to be configured during initialization. For example:

[
  {
    "pid": "com.liferay.portal.kernel.model.Group",
    "properties": {
      "languages": "en_US,ar_SA",
      "defaultLanguageId": "en_US",
      "name_i18n": {
        "en_US": "Corporate Website",
        "ar_SA": "الموقع الرسمي"
      },
      "description_i18n": {
        "en_US": "Corporate public website",
        "ar_SA": "الموقع العام للشركة"
      },
      "friendlyURL": "/corporate",
      "virtualHostname": "www.example.com"
    }
  }
]
1 Like