First, a short introduction on why we focus on ASP.NET, DotNetNuke and offer tutorials and other learning aids which we hope will further benefit and help grow the .NET community.
What are our immediate plans? Well, we both work full-time jobs, but we're interested in helping spread our belief in web services, module-based development, AJAX and Workflow architecture. In this vein, we're about to release a custom web-scraping module, which has filtering capabilities, the ability to completely replace the stylesheet of the scraped information, to add an unlimited number of web scrapes to the module and many other features. We're also working on a unique enhancement to the DotNetNuke search engine and a number of other modules--all wrapped in web services for SOA optimization and load-balancing, enclosed in class libraries, which use standard object patterns to separate the business rules and data objects.
Don't forget to check our free downloads page for the latest free Wordnet Libraries in VB.NET and other free modules with source, including a DotNetNuke implementation of the Princeton Wordnet 2.1 Dictionary. You can see a demo in action here.
Here's an example of Fingerfuel Web Parts in action--from a 
site I've been building for my writing hobby. We did all the graphic design, page layout and I wrote a custom module and a custom DNN skin object (which replaces images based on the menu level--look at the image strip on the right hand side of the page and how it changes), both of which we'll make available once we upgrade the modules to DNN 4.X.
One benefit of working with DotNetNuke for three years is getting to know the tweaks and knowledge required to overcome the sometimes formidable install process 
becomes more intuitive. We've all had our DNN install nightmares, and I wanted to offer some common sense when it comes to installing any new version. Here's a tutorial on installing DotNetNuke version 4.3 on SQL 2000 (the procedure also works with SQL 2005), that I wrote for DNN Creative Magaizine, which I highly recommend you subscribe to if you're interested in what's happening with DotNetNuke.
We're currently working on a tutorial about working with Microsoft's AJAX.NET and the Client API in DotNetNuke. One obstacle you have to overcome is a basic one: Microsoft uses the JSON (pronounced jayson) standard, while the ClientAPI uses XML.
Finally, since it's important to our belief in the concept of web application parts, we add, well, about two cents worth of comments on all those AJAX libraries 'out there', and which one(s) we are using.
We're excited about building ASP.NET and DNN web parts, whether one calls them modules, parts, flakes, fingers, or snippets. We build all of our web parts in class libraries using MVC and the Provider patterns (among others), wrap our class libraries in SOA web services and present the GUI in .NET, AJAX and DNN formats.
So if you use our products, you can rest assured, when Web 3.0 or whatever arrives, you can wrap whatever new web GUI arrives around our core products.