IMPORTANT: This version of Sitefinity CMS is out of support and the respective product documentation is no longer maintained and can be outdated. Use the version selector to view a supported product version.
With Feather, you can override the default designer views, JSON, and JavaScript files by creating a file with the same name. This is suitable when you want to change the way your default designers look, but you do not want to create a new designer view for this purpose. For example, you want to brand them with your company’s logo.
Feather has a strict convention for resolving resources. Because of this, if in your SitefinityWebApp you place a project a file with the same name as the resource you want to override (view, JSON, or JavaScript,) your resource file will be used, instead of the default one.
In this scenario, there are some considerations to be taken into account. For example, if you need to add another client component in your view, it is not enough to create a view with the same name, because the default JSON and JavaScript files will be loaded. They do not contain the scripts required for your additional client component, therefore, your overridden view will not work as expected.
This means that if you want to add additional script dependencies, you must override the JSON file and place it in the same place as the view. For more information, see Feather: Extend designers with client logicFeather: Extend designers with client logic. If, in addition, you need custom client logic, you must also have to override the JavaScript file and place it in the folder, by convention.
This article describes the case in which you want to enrich your designer view. In case you want to remove components or scripts that you do not need, you must override the JSON or the JavaScript file. Otherwise, they will be loaded unnecessarily in your designer view.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important