Site baseUrl

[rymsha]

Site baseUrl stored in siteConfig under "system" application key: com.enonic.xp.site

"data": {
    "siteConfig": [
      {
        "applicationKey": "com.enonic.xp.site",
        "config": { "baseUrl": "https://www.example.com:8443/path" }
        ...

Can be used for various purposes, similar to how html <base> element used for, but on backend. (although domain part is always required)

• generation of sitemap.xml links
• links in emails
• links in rss
• pageUrl generation when not is scope of request (?)

Examples of baseUrl:

https://www.example.com:8443/path

www.example.com (equivalent to //www.example.com)

www.exaple.com/my-site (equivalent to //www.example.com/my-site)

http://www.example.com

http://www.example.com:8080

https://www.example.com:8443

https://enonic.atlassian.net/wiki/spaces/TD/pages/2743304247/Site+base+URL

[rymsha]

When implemented, CS should be adjusted to ignore com.enonic.xp.site applicationKey

[sigdestad]

Just saving some alternative "application key" names

"cms"
"portal"
"site"

[sigdestad]

For inspiration - this is what the Content Studio UI might look like:

General idea - we filter out selected/system applications and list them in a separate step, and we prevent deleting it. This will align site closer with "project" form as well.