Hi Rodney, got your email email and I'll reply here...
I can add just one or two points.
The MobikNuke guy was very keen when he showed up in the forums and worked out his plans for it. I thought did a great job, but as you say, you have to ensure that it's still in active developement before committing to it. I've had no further experience with it, but have kept it on my lilst of apps to get when the need arises.
I'm a PPC/PPCphone user since about 2000 and use it every day. All in all, the only websites that really are useful are ones that trim their offer down to only the most useful and most relevant content and then display that with just basic links and text content.
Mobile content doesn't have to be interactive. If the true goal of providing a mobile site is to accessorise and as a result further monetise the main site, then the goal is largely met by providing basic one-way informative content.
So for example, regarding your Poker site.. list the top 3 must-have items of content and concentrate on providing just those items on the mobile site. You might have a homepage with a tiny logo and a page of text links leading to a selection of your most worthy RSS content.
You could set something like that up using a blank dnn skin and tie it to a mobile.pokerdiy subdomain, or get the pokerdy.mobi for it.
Now, that may not sound as exciting as a fully interactive mobile site, but it would get your content onto people's phone in a broadly used format, and you could also feed it into existing mobile rss aggregators like mobipocket.com or avantgo.com and potentially reach a much greater audience.
That would probably fulfill 90% of the value of having mobile content and be relatively easy to set up.
If you find that people really like it and want more, then you can perhaps consider what the most vaulable interactive procedures would be for your audience. Again. it may just be a single process such as responding to a request with a yes or no, or it may be as much as carrying out a purchase... I'm not really familair with pokering so I dont' know.
The point I'm really making is that it's only 10% of the work to reach 90% of the mobile site goal but another 90% work to gain the last 10%... so be wary, or at least be very clear on achieving measurable results, before spending a lot of time and money building complex interactivity.
If I were creating a mobile site from one of my sites today, I'd probably start by making it a single page with a single module... one of the RSS modules, and try and get the domain to point to it automatically based on mobile browser detection. I recall that was one of the features discussed for MobiNuke. He was going to make an http module for the purpose. I'm not sure if he did but that would be very useful.
Regarding the menu.. none of the DNN menus need even be on the page. If you wanted to link to another page with another module at some point, just use a text link.
I'm not sure you need to make the mobile pages invisible to the web. When I go to google on my mobile, it opens a special google mobile search tool. There'll be some sort of spec at google for controling that aspect I'm sure. Here's a poker search on it: http://www.google.com/m/search?eosr=on&q=poker&site=mobile&sa=X&oi=blended&ct=more-results Note the little phone icons. Some of these are mobile sites, and others will autodetect on entry.
Let us know how you get on with it all.
Rob