News

A number of us from Engage attended DNN Summit last month in Denver. It was a great opportunity to strengthen our relationships within the DNN ecosystem, share our DNN and development expertise, and get a better understanding of the state of the community. This post provides links and summaries of the sessions I presented at the conference.

We just returned from DNN Summit 2017, where I gave two presentations (I also helped coordinate the Code-a-Thon, and my colleague Anthony Overkamp gave one presentation and led a full day of theme training). I wanted to put together a quick post to let people know where to access the materials from my presentations.

I've written about the high level benefits of using the Elm language, this post deals with the developer experience of using Elm.

At Engage, we've been excited to embrace a new technology for creating web applications that are more maintainable, performant, and reliable. Elm is a programming language that compiles to JavaScript, designed from the ground up for creating web applications, in a way that guides developers towards well-architected code, which we've been excited to explore and have now officially decided to adopt as our primary front-end development language.

TL;DR Install the Security Analyzer module if your DNN website is on a version below 7.4.1 (starting in 7.4.1 this module is included within DNN itself). If you're on DNN 8, make sure you've upgraded to 8.0.3.

I've written a post about using JavaScript Libraries in DNN on the DNN community blog. We're excited about what it will look like for the community to start making use of this feature of the DNN Platform. Check it out!

A couple of weeks ago, Engage shut down our offices for a day so that everyone in the company could work on making DNN better. The primary component that we wanted to focus on was the rich text editor, specifically making some investments in the CKEditor provider, so that it can replace the Telerik RadEditor provider (the community had already decided to migrate to the CKEditor for a number of reasons, so we wanted to ensure that we were migrating to something that we would want to use). I wanted to give a quick rundown of what we accomplished and what's next for the CKEditor in DNN.

Engage is hosting a hackathon in our St. Louis office to work together to better the DNN Platform.

A number of big changes have been going on in both the DNN and Microsoft communities.  I provide a run-down on my blog at https://weblogs.asp.net/briandukes/changes-everywhere-we-look

The Engage team just got back from attending DNNCon, where I gave two presentations, Creating URL Providers for Your Custom Extensions and Contributing to Open Source Projects on GitHub and CodePlex.  Jason Stone also presented Enterprise Social Networking - A Primer.

I'll be speaking at DNNCon in October, but maybe you should've been.  A call for more diversity in the DNN community...

For I ♥ DNN, we wanted to bring the barrier to entry very, very low, so that anyone could join the conversation simply and easily, without having to create yet another website account. To that end, we wanted to allow folks to sign in with their existing social network logins: Facebook, Twitter, and Google. Since these are provided with DNN, we assumed it would be fairly simple to achieve our vision. However, we ran into a handful of obstacles that we worked to overcome in implementing the core social login providers, ultimately copying and extending them to better meet our needs.