This repository contains samples related to Project Feather.
feather - This repository contains the core infrastructure related to the Feather project.
feather-widgets - This repository contains custom MVC widgets which are part of the Feather project.
feather-packages - This repository contains front-end packages for the Feather project.
| Feather version | Sitefinity version |
|---|---|
| v.1.4.360.0 - latest | 8.2.5900.0 to 8.2.9999 |
| v.1.3.300.1 - 1.3.350.0 | 8.1.5800.0 to 8.1.9999 |
| v.1.2.120.0 - 1.2.290.1 | 8.0.5700.0 to 8.0.9999 |
| v.1.1.20.3 - 1.1.110.0 | 7.3.5600.0 to 7.3.9999 |
| v.1.0.0.0 - 1.0.10.2 | 7.2.5300.0 to 7.2.9999 |
| v.0.5.1000.4 | 7.1.5208.0 to 7.1.9999 |
| v.0.4.1000.2 | 7.1.5200.0 to 7.1.9999 |
| v0.1.1000.1 - v.0.3.1000.4 | 7.0.5100.0 to 7.0.9999 |
This project has been released under the Apache License, version 2.0, the text of which is included below. This license applies ONLY to the project-specific source of each repository and does not extend to Telerik Sitefinity CMS itself, or any other 3rd party libraries used in a repository. For licensing information about Telerik Sitefinity CMS, see the License Agreements page at Sitefinity.com.
Copyright © 2005-2016 Telerik AD
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
The Feather Community is essential for keeping Feather great. We want to keep it as easy as possible to make you part of this project. You can contribute your samples directly to this repository.
A simple pull request is all you need to make your sample available for the Feather Community. Keep in mind that your sample will be more valuable if it is well structured, documented and solves a well-defined problem. A readme file is highly desired to help users understand what is the purpose of your sample or how and what problem you are solving. A great sample addresses a single problem, describes it well, describes all its prerequisites to work, has clean, structured and well-documented code, describes the way it solves the problem and works out of the box. You can reference the AuthorWidget sample as a guide - it has all the above mentioned features and it works out of the box.