Fork me on GitHub
2sxc 9.33 for DNN 7 to 9
Website Builder, Content Manager, App-System: open-source and amazing
You are here: Home  >  Docs

2sxc Documentation

We are currently re-working the documentation structure. The new structure will be:

  1. API documentation for Razor/C#, JavaScript (incl. $2sxc and $cms), WebServices, Edit-UIs etc. will be found on the 2sxc wiki.
  2. Features-documentation will be found on this page
  3. Learning tutorials and concepts will be in Learn
  4. Blogs, examples etc. are of course in Blog

Features of 2SexyContent with Details and How-To-Use

Filter by

Now you can easily add any kind of data to the pipeline with the DataTableDataSource. This is great for adding XML, RSS, NoSQL sources, Resx-files and much, much more. (added 06.00.06)
Tags: Apps, Data and Data Sources, Database, Entities, For experts, Import/Export, Lists, Lists with Details, new in 6.x, Razor,

Export/Import is now available and handles a variety of complex scenarios. It can match languages, re-link files and much more. (added 05.04.00)
Tags: Import/Export, Content Types, Entities, Images, Linking, Multi-Language,

2sxc provides an extensive, advanced content import/export system to help you migrate from other tools or import data from Excel and other lists. (added 07.00.00)
Tags: New in 7.x, Entities, Data and Data Sources, Import/Export,

When installing Apps or anything else, everything is done automatically and DNN doesn't need to restart. This is very powerful because in a live large system - downtimes and I-Hope-It-Still-Works-Afterwards are not acceptable. (added 06.00.00)
Tags: Import/Export, new in 6.x, Apps,

Amazingly simple integration with knockoutJS. An amazingly simple data-backend using 2SexyContent, a cool JS-Framework to play with the output - all connected with the Data-Pipeline of 2SexyContent. (added 04.00.00)
Tags: JavaScript, Import/Export, Lists, Lists with Details, Razor, Token, Apps,

Links will still work even after moving pages and files in DNN. They also still work when you rename pages or files. (added 05.04.00)
Tags: Field Configuration, HTML and CSS, Linking, Import/Export, Multi-Language,

You can easily use PetaPoco in Razor Templates with DNN and 2SexyContent. (added 06.00.06)
Tags: Apps, Data and Data Sources, Database, For experts, Razor, new in 6.x, Import/Export,

Now 2sxc offers a simple REST API so that you can access content like .../app-content/Feedback/342 to perform all kinds of actions using JavaScript. (added 07.01.00)
Tags: AngularJS, Content Types, Import/Export, JavaScript, New in 7.x, WebApi,

Create vCards based on 2SexyContent-Data. Very easy to use. (added 05.02.00)
Tags: Design, HTML and CSS, Images, Import/Export, Linking,

Thanks to the fully automated WebAPI integration you can easily include and distribute your WebAPIs with you Apps. (added 06.05)
Tags: Apps, For experts, Import/Export, JavaScript, new in 6.x, WebApi, Razor, Token,

Look inside

Content Item

These are the values a content-editor can manage.
Name Type Value
Title System.String App Information - Object and Token
Teaser System.String Using the App-Object you can access path information, settings and resources.
AddedInVersion System.String 05.05.00
DescriptionLong System.String <p>This new variable / token was introduced to help templates become flexible.&nbsp;</p> <p>Usage Tokens</p> <ul> <li>[App:Path]/scripts/knockout.js</li> <li>[App:PhysicalPath]</li> <...
ImageTeaser System.String
Image System.String
DocumentedOnPage System.String Page:463
StatusDocumentation System.String 3
StatusDevelopment System.String 10
DesignedContent ToSic.Eav.Data.EntityRelationship
ReplacementDocs null
Tags ToSic.Eav.Data.EntityRelationship 1840,1841,1910,2440
RelatedFeatures ToSic.Eav.Data.EntityRelationship 1831
DemoAppGuid System.String
DemoPage System.String


Presentation Item

These are additional, optional presentation instructions a content-editor can manage. If none are entered, a default set (predefined by the designer) will be used.

No Presentation parameters specified, using default presentation for this item.


Template file

@using DotNetNuke.Entities.Modules
@using ToSic.SexyContent.Search
@using ToSic.Eav.DataSources
@functions
{
    public override void CustomizeData()
    {
        // Don't customize anything, nothing to customize in this case
        //throw new Exception("demo");
        var relationshipFilter = CreateSource<RelationshipFilter>(Data["Default"]);
        relationshipFilter.Relationship = "Tags";
        relationshipFilter.Filter = "[QueryString:Tag]";
        if (relationshipFilter["Default"].List.Count() > 0)
        {
            Data.In["Default"] = relationshipFilter["Default"];
        }
    }

    /// <summary>
    /// Populate the search - ensure that each entity has an own url/page
    /// </summary>
    /// <param name="searchInfos"></param>
    /// <param name="moduleInfo"></param>
    /// <param name="startDate"></param>
    public override void CustomizeSearch(Dictionary<string, List<ISearchInfo>> searchInfos, ModuleInfo moduleInfo, DateTime startDate)
    {

        foreach (var si in searchInfos["Default"])
        {
            si.QueryString = "mid=" + moduleInfo.ModuleID + "&feature=" + si.Entity.EntityId;
        }
    }


}@if (Request.QueryString["feature"] == null)
{
    // Note: the code inside _List.cshtml could also be inserted right here
    // I just took it out to make everything a bit easier to read
    // The Render-Page will execute that CSHTML and include all data that is in the current view
	@RenderPage("_2SexyContent Feature - List.cshtml");
}
else
{
    // This one will also execute another CSHTML, but will add a variable with the URL-parameter
	@RenderPage("_2SexyContent Feature - Details.cshtml", Request.QueryString["Feature"]);
}