The DecentCMS and Orchard content type systems compared

Posted by: More Whidbey stuff, on 25 Feb 2015 | View original | Bookmarked: 0 time(s)

The content type system in Orchard is one of the reasons for its great flexibility. The ability to build your own content types from building blocks that are just the right size is essential to building a great CMS. Orchard has content types that are made of content parts, that can have properties and fields. Parts are aspects of a type, such as title, comments, or body, that there can be only one of per type. Fields are named, and there can be any number of each type of field per content type. Confused...

Category: XML | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 478 | Hits: 13

Similar Posts

  • Using Seadragon with ASP.NET MVC more
  • Dynamic Languages: A Separation of Concerns more
  • Silverlight SVC Web Service problems on IIS more
  • Custom Config file for a WCF Service hosted in IIS more
  • You can't hold onto nothing more
  • Mutable and immutable anonymous types in VB more
  • Why I Love F#: Tuples more
  • Generated Date Types in WCF and unexpected 'dateSpecified' fields more
  • What data type should I use? more
  • XML Schema Facets more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD