docs(customization): updates to customization document to align with custom assets feature

[ossdhaval]

Prepare

• Read PR guidelines
• Read license information

---

Description

Target issue

closes #issue-number-here

Implementation Details

---

Test and Document the changes

• Static code analysis has been run locally and issues have been fixed
• Relevant unit and integration tests have been added/updated
• Relevant documentation has been updated if any (i.e. user guides, installation and configuration guides, technical design docs etc)

Please check the below before submitting your PR. The PR will not be merged if there are no commits that start with docs: to indicate documentation changes or if the below checklist is not selected.

• I confirm that there is no impact on the docs due to the code changes in this PR.

[dryrunsecurity]

DryRun Security Summary

The provided text summarizes the details of how to customize the web pages in the Janssen Server application, including managing custom assets, customizing built-in web pages, adding new web pages, customizing resource bundles, and modifying the page layout, header, and footer, while emphasizing the importance of secure customization practices to maintain the overall application security posture.

Expand for full summary

Summary:

The code changes provide detailed information on how to customize the web pages in the Janssen Server application, including managing custom assets, customizing built-in web pages, adding new web pages, customizing resource bundles, and modifying the page layout, header, and footer. From an application security perspective, the key points to highlight are the importance of secure asset management, proper input validation, secure template customization, and secure resource bundle management. While the customization features are valuable, it is crucial to ensure that the customization process is carried out securely to maintain the overall application security posture.

Files Changed:

• docs/admin/developer/customization/customize-web-pages.md: This file has been updated to provide detailed instructions on how to customize the web pages in the Janssen Server application. The changes cover the following key points:

  1. Managing Custom Assets: The Janssen Server allows customization and extension of web pages, images, templates, etc. by using "Custom Assets", which can be managed using Janssen Server configuration tools.
  2. Customizing Built-in Web Pages: Existing web pages can be customized by creating a new XHTML page and adding it as a custom asset.
  3. Adding New Web Pages: New web pages can be added as custom assets and then referenced in the custom scripts.
  4. Customized Resource Bundles: Custom resource bundles can be added as custom assets to override the built-in ones or to add support for new languages.
  5. Custom CSS and Images: Custom CSS files and image files can be added as custom assets and then referenced in the XHTML pages.
  6. Page Layout, Header, Footer Customization: The common layout, header, and footer of the web pages can be customized by uploading a modified template.xhtml file as a custom asset.

From a security perspective, the key points to highlight are the importance of secure asset management, proper input validation, secure template customization, and secure resource bundle management to maintain the overall application security posture.

Code Analysis

We ran 9 analyzers against 1 file and 0 analyzers had findings. 9 analyzers had no findings.

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.