2sxc 11.01 adds some long awaited features like in-page list management, add-existing-item and system to create custom input components. 

Learn in a 5 minute video how list/details apps (modules) are built. Download the code, discover, and create :)

The template/data-paradigm is very common, where a template visualizes data provided by a query. This results in typical list/details systems like blogs, news, showcases and more. But when managing content on normal pages, this approach doesn't really work, which is why we need the template/content-paradigm. 

I often see developers solving content challenges with the data-oriented principles. This is fundamentally wrong, like writing a sentence using letters instead of words. Such data-solutions work - but only after educating the editor in database concepts. Our customers find DNN-solutions simpler than Wordpress - because of a paradigm shift which changes everything we do. I would love to help you to see the world in this way - here's an attempt at it…

Content Management has some unique challenges which are very different from working with data. One of these is how a module knows which content to show. 2sxc has various features, here I'll provide you a deeper understanding to help you create advanced solutions.

A common use case for an app like disqus is to include it in a list/details scenario like a blog, where you only want the discussion items to appear on the details page. Since most such setups use the same DNN page for the list and the details, we need another mechanism to sometimes include this functionality. I present to you: conditional server-views in apps.

This is a part of my series The New Features of 2sxc 7 and introduces you to importing existing data into 2sxc. You will usually want to do this when starting with existing data (like customer addresses) or when migrating from another tool (XYZ-Articles, XYZ-News, XYZ-Gallery) or from another CMS like Umbraco, Drupal, typo3 etc.