Seeking a Sustainable Customization Workflow for Dify

[sharpdima]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Content

"Hi Dify Team,

Thank you for the detailed explanation regarding the i18n migration to JSON.

As a developer maintaining a customized version of Dify (project Mora), I face significant manual work and merge conflicts with every major update, especially when core structures (like i18n or UI components) change.

My question is: What is the best practice for maintaining deep UI and backend customizations without having to manually fix dozens of conflicts every time?

Is there a recommended way to override components or translations using a 'themes' or 'plugin' system that remains separate from the core upstream/main?

How can I protect my branding and Persian (fa-IR) localizations from being overwritten or deleted during structural migrations?

I want to stay updated with Dify's great new features, but the current maintenance overhead is becoming unsustainable. Any advice on a more 'modular' approach for custom forks would be greatly appreciated!"