Written By Peter Donker
2026-11-17
Hi all. I am guessing most of you are, like myself, trying to catch up daily with developments in AI and trying to process how this will impact our work. The pace is absolutely breathtaking and FOMO keeps me in a continuous state of mild excited stress. This time last year I was definitely still in the camp of "let's wait and see". I had tried a couple of things but results were mixed. I had begun paying a monthly fee for a product called Cursor, but wasn't getting anywhere near using the credits I had for each month. Fast forward to today and I am now closely monitoring my token usage because I'm afraid I'll run out before the end of the month. What a year this has been. I hear the question "are you even coding, still?" more and more often. The transition of our work is now in full swing and as I'm riding this wave I'm trying to stay on my board.
Having used this predominantly for doing smaller interventions for software products I manage, it was only a matter of time before I felt comfortable taking on something "bigger". With a small intervention I mean asking my agents to add a feature. But there were tasks I was shying away from until now. One of those was an overhaul of DNN's Blog module (you're looking at it right now). The Blog module has a history dating back to the early days of DNN. In 2013 I took over as developer of this module and made significant changes. Turning it from a fairly simple "add some text to this webpage" to a publishing engine. Did you know you can manage what gets displayed in which language? Or that you can create a multilingual blog where each post has translations for each language? Or that you can have blogs that you share with a group of people? Or that you can publish to it using the old Windows Live Writer (now Open Live Writer)? Or that you can surface content anywhere on your site with selectors like tags/authors/etc? Or that it has a basic workflow for publishing? Anyway, too much to go through in detail, here.
But, back in the day, I kept it as Webforms and VB.net. And whenever I opened up the code I realized that I (and many others) had moved on technologically speaking. But a rewrite of this module was not a weekend project. It was going to require quite a bit of serious work. And although I love the module, I also realize many of you have switched to structured content solutions like 2sxc for managing blogs. Fair enough. So who am I doing this for? Just myself and the community site? Maybe. So it was hard to justify dropping everything to focus on this for an entire holiday, especially given I am also heavily involved in developing DNN itself.
So, a perfect storm for AI. A couple of weeks ago I began a project in Cursor to rewrite the blog module as an MVC C# module. I created a folder for the project, and I had two subfolders: "Blog" and "BlogNew". In the latter I scaffolded out a new MVC module using my own Yeoman template for this. In the root of the project I began writing out my rules. Where the old dev site and the new dev site were. What accounts to use for which role. Where on my hard disk Cursor could find other examples of the architecture I was going for. How to compile and what to copy to the dev site. Etc. Etc. Then I set about writing out my (initial) thoughts on what I wanted done. I prompted Cursor with this and let it create a module. And just ... wow. Within an hour I had something running in development. It was ugly, but it ran.
That led me down the path of "well, now we're here, let's take care of some more irritations". A better looking UI, where I use Razor where possible and React where necessary. Using React just gives that much more control over the end user experience. So the Blog Edit screen stayed in Razor, but the post edit screen became a React project. And to take things to the next level I wanted to sink my teeth into the rich text editor.
As you all know DNN comes with an in-built rich text editor. It is a third party product called CK Editor and is causing a lot of headaches behind the scenes. The makers have decided to change the license and as a result DNN cannot ship the latest version of this editor. It is also a "one size fits all" approach. This editor is built to satisfy the demands of just about every possible DNN editing solution. But it can't be used inside a React project. So that was ruled out for the approach I took for this rewrite. I did my yearly "what is the state of rich text editors, today"-round and, as always, didn't find a clear winner. What I was looking for was so specific that it dawned on me that I probably had to as AI to create me one. So this rewrite includes a brand new rich text editor embedded in this module. It can do HTML-style editing and also Markdown editing (a feature I wanted to add for this rewrite). It includes the ability to add images and files for a post, that will be written to the blog post's own folder on DNN. In fact, you can now just drop an image or file into the editor and have it show up right there. This is a feature Github's markdown editor has and that I find really neat. No upload boxes, just drop it in place. Other features include the ability to use backticks for code blocks in the markdown editor. Something I have also wanted for years.
Realizing the direction the AI revolution is taking us, I have also added a new "Blog API". Ultimately I think Open Live Writer will be surpassed by using AI to add our thoughts into a blogging engine. To this end I've added WebAPI endpoints in the module that could be accessed using an MCP server that you run locally. The authentication would be through the Api Tokens that I've added a few years ago in DNN. Enable that and users will be presented with an Api Tokens tyab on the manage screen where they can add and manage Api Tokens. I still have to document the API and see about creating that MCP server, but I am confident this is where folks are heading.
Yesterday, I created a first RC for this rewrite. It can be found here: https://github.com/DNNCommunity/DNN.Blog/releases/tag/v7.0.0.rc-1. Note that you need to be on DNN 10.4.0 or higher for this to work. Please let me know what you think and what your experiences are. Is the custom rich text editor enough? Or do you miss features? Do you agree with this direction?