The organization system of the Knowledge Center has been updated for improved navigation and accessibility. Key points include:

• The existing content has been reorganized for better clarity; no information has been deleted or added.
• The update aims to enhance the ability of users to find answers independently.
• Users are encouraged to report any repeated questions or missing information for further enhancement.
• The FAQ section will be replaced by a new support feature in the near future.

• The Customer Success department will now manage all migration processes from start to finish.
• Users initiating a migration will be redirected to a designated Google Form for submission.
• The Customer Success team will address any issues that arise during the migration process.
• Customer Care will no longer be involved in the migration process.
• A Macro has been created to assist with inquiries related to the migration process, directing users to contact Customer Success for support.
• Ongoing migrations in the Data Cleaning stage should be referred to the Migration Meeting for further handling.
• Existing migrations nearing completion will continue as previously scheduled.

We are pleased to announce the addition of new articles to the Help Center:

• A new article on "Installments" has been published, providing guidance on selling products through installment plans.
• The "Getting Started with Subify" article has been updated to enhance user experience. The revised content includes:
• An overview of Subify
• Potential use cases
• Key features
• Instructions for creating the first plan
• Customization options
• Testing subscriptions

These articles are linked to the existing resources in the Help Document for comprehensive support.

The Subify platform has been updated to version 2.27. This release does not include any new features. Users can review the associated changes and bug fixes in the release notes.

Release 2.24 has been deployed. The following changes are now visible to users:

• Two minor updates have been implemented that enhance the merchant experience.

For more details, please refer to the official documentation.

The following updates are included in Release 2.23:

• Added a Help tab with an "Email Us" section for improved user support.
• Reordered the display of selling plans for enhanced clarity and accessibility.

For additional details, please refer to the release documentation.

The following updates have been made in Release 2.22:

• No major changes are introduced that will be noticeable to users or merchants.

For detailed information regarding the release, please refer to the official documentation.

The following outlines the key aspects of widget customization:

• Overall Structure:
• The widget is composed of HTML elements and tags that contain various types of content.
• Customization is limited to the content text; HTML tags themselves cannot be altered.

• Styles:
• Styles are applied to HTML tags to enhance visual appearance.
• Customization of styles is permitted.

• Logical Code:
• This component manages the functionality of the widget, such as updating text and IDs based on selling plan changes or applying discounts.
• Users are not permitted to modify the core logic of the widget. Developers may extend the SDK's logic using the provided documentation, but cannot change the fundamental logic.

• SDK Features:
• The SDK is designed to facilitate widget selection and usage for users without coding knowledge.
• Selling plans created by the backend are intended for use within the platform and do not require the SDK for implementation.
• Merchants with a developer experienced in front-end development can utilize Liquid or API to access and display backend-created selling plans, bypassing the need for the SDK.

We are pleased to announce the release of Subify version 2.21. This update includes the following enhancements:

• Added the ability to incorporate widgets into additional pages and collection pages.
• Introduced permission settings for widgets, now accessible in the widget tab.
• Enhanced merchant visibility and management capabilities for this feature.

For further details, please refer to the accompanying documentation.

• The Jira workflow has been updated to streamline the process by removing unnecessary statuses.
• Users will now work with a single status: "TO DO P SUB" for issue management.
• The workflow process is as follows:
• An issue is created and enters the "TO DO P SUB" status.
• The issue will be reviewed and moved to one of the following statuses:
• DONE
• PENDING SUPPORT
• CANCEL
• TO DO TECH SUB
• If an issue returns to the support team (PENDING SUPPORT), it can be reverted back to "TO DO P SUB" for further action.
• The previous "CHECK-IN" statuses have been removed as they were not utilized effectively.
• The "QA PASSED" status indicates that testing has been conducted on an issue, and the task will be marked as DONE only after all release-related tasks are completed.
• The Intercom board workflow has also been reviewed to ensure synchronization with these changes, and additional columns have been removed.
• All issues currently marked as PENDING SUPPORT will be addressed and updated accordingly.