Find a post...

At DNN-Connect.org we have spend effort to collect and create language packs for various modules. And it is slowly comming into shape.

DNN Corp is on the verge of releasing their latest DNN Platform release, version 9.0.0.  As a DNN MVP, I of course had to take a look around at the new stuff coming.  It’s still in the early stages though, so there are a few areas where the new updates have some smoothing out to do, but overall, the updates we’re seeing in version 9.0 are very nice.  In short, it’s a much more contemporary user experience for all involved – but a very important step in the right direction for the future of all DNN’ers.  Here’s my preview and insights after using DNN 9.0 for the first time – a pre-release version of DNN 9.0, that is.

We just released a brand new set of content templates, optimized for Bootstrap 3 themes (skins). Now, both layout and content look great!

Technically both the App and the Content module could be used for the same things - but you shouldn't, because they behave differently and provide a different UX. Here's an overview.

Many cool visualizations run in JavaScript, so your scripts must be able to get the content-items as JSON. Here are the 4 most important ways to do it. 

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. 

During DNN Connect 2016 a group of interested attendees got together to discuss their experiences of using Azure Web Sites to host DNN Community and Evoq versions. Here is a summary of the notes taken during the session along with the key pieces of advice and top tips.

Getting DNN to dotnet core seems daunting - or maybe not? I believe the solution can be very simple - let's explore...