Today we're releasing the pre-version of 2sxc 8.3. It has some advanced new features which also required us to clean up some internal code. So if you were using inofficial APIs (which you shouldn't), this make be a breaking change for you. 

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…

And the devil spoke: "Let there be errors". And God Spoke: "Let there be a debugger". This is a short tutorial to get you started in cornering JavaScript errors. 

2sxc 8.2 was released and is now through with the first round of hot-fixes. Time to tell you what's new :)

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.

The User Experience for designers, developers and data-modelers has just been improved by factor 3 in 2sxc 8.1. Now both the template-code and the current content-type are just a click away, and highly optimized. You want to loop through all the items of a list? The code-snippet is already waiting for you - prefilled with the correct variable names. 

Announcing 2sxc 8.1 which has best-in-industry WYSIWYG experience (incl. drag-drop image and document-upload), a template editor with Sherlock-Snippets, ADAM 1.2 with file and folder metadata and more. 

Dynamic Content-Types are extremely flexible. In advanced scenarios you want to share ONE type definition across multiple portals or apps - for example when many sub-portals have a similar setup. 2sxc has supported this since version 5 and in 8.1 there is finally a web-UI to do this. 

2sxc is all about solving common content and web tasks quickly and efficiencly. Because of this we're enhancing the in-page toolbar with advanced features (only visible for users with elevated permissions). Let's discover...

The newest version of ADAM (Automatic Digital Assets Manager) lets you group files (often images) into folder (like albums) and also lets you add custom metadata like author, title, description and much more. Adding assets to a content-item just got 10x more powerful.

After evaluating over 50 editors and deciding to give TinyMCE a try, it's time to integrate it into 2sxc as a replacement for Telerik. Turned out to be easier than I thought…

So after extensive evaluation (parts 1, 2 and 3) and basic integration and design (part 4) it was time for some advanced issues. In this case, DNN integration.

So after extensive evaluation (parts 1, 2 and 3) and integration and design (part 4 & 5) I really want to add value. It's time to integrated ADAM - the Automatic Digital Asset Manager.

Sometimes after installing or upgrading 2sxc the user will see a message that the upgrade did not complete. Here's why, and what you must do.

The built-in telerik editor is going away (thank God!) and the CK Editor is supposed to be the new one, but honestly it looks terrible and old - and IMHO it's not good enough. Time to look around and smell the roses…

Whenever you need to evaluate something, the most important thing is determining what will define a winner. See if you agree/disagree, as this criteria will affect the choice of recommended WYSIWYG.

There are over 100 WYSIWYG editors out in the wild. So it's important to filter them based on the critical criteria (mostly management criteria). Here's the full and short-list.

Grunt (or Gulp) are a critical cornerstone for modern style web development - without these it's basically impossible to create anything complex. Let me show you some real life examples where we use Grunt in the development of 2sxc. 

The move to JavaScript applications has a profound impact on the concept of Platform Market-Share. A JavaScript App could run on any kind of host from Apache to Azure - so the only question of compatibility is if the hosting platform (like DNN) has an appropriate JSON-WebAPI to answer the requests of the JS-App. Oh brave new world…

Here's a little Christmas present from 2sic to the DNN community: we just pimped ADAM, the Automatic Digital Asset Manager.

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.

What I really, really love about 2sxc is they way you can leverage existing tools and integrate them into DNN in minutes. Here's what I just did with the disqus service…

Very often you'll create a custom input-type (like a select-value-from-json-feed) and then want to provide the web-designer with additional configuration options - like specifying the web service which will deliver the json-feed. Here's how…

The future of the internet is not on the server. The fight around php vs. asp vs. mvc-on-the-server is suddenly irrelevant, because the future for online-systems is JavaScript-Based. What really got me excited is that WordPress.com just redid their entire system to also go this way. Since we just spent around 100 days refactoring 2sxc into this architecture, I will write a bit about this, beginning with some background why and hows…

There are loads of reasons why to create a custom input type. Maybe you want to create a color-picker or you want to create a dropdown which provides options based on a JSON-feed. No matter what you want - here's how to do it.