UI improvements to scaffolder templates

[stefinie123]

Purpose

This pull request introduces improvements to the display of nested and array data in the custom review step of the scaffolder, as well as minor updates to organization-related descriptions and layout tweaks in the catalog page. The most significant changes are the addition of custom renderers for nested objects and arrays, which enhance the clarity and usability of the review UI.

UI Improvements for Nested and Array Data in Sacffolder Templates Review Step:

• Added NestedObjectRenderer and ArrayRenderer components to CustomReviewState.tsx to display nested objects and arrays in a more readable, structured format during the custom review step. These components handle booleans, arrays, and deeply nested objects, improving the user experience.
• Updated the CustomReviewStep logic to use the new renderers, ensuring that all nested and array fields are formatted for display, rather than shown as raw JSON or flat text.

Screen.Recording.2025-11-21.at.19.38.20.mov

General UI and Layout Updates:

• Adjusted the grid layout in CustomCatalogPage.tsx to allocate more space for personal filters, improving usability on larger screens.

Description and Help Text Updates:

• Changed the organization field description in the CTD-to-template converter to clarify that the organization is auto-selected and cannot be changed, removing redundant help text.
• Updated the organization name field description in template.yaml to more clearly state its purpose as the organization where the project will be created.

Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email [email protected] to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to [email protected] and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

• Unit tests

  Code coverage information

• Integration tests

  Details about the test cases and coverage

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
• Ran FindSecurityBugs plugin and verified report? yes/no
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.