We wanted to ensure that the modules were scaleable and could handle high volumes of users (If you’ve tried the demo on Smart-Thinker (4100+ users) you’ll know that inviting users by name is a little slow and clunky). We aim on identifying these limitations on PokerDIY and enhancing and improving the quality of the modules to handle large amounts of users and traffic.
To cut a long story short, this project has blossomed and has been very well received by the home poker community (note – this is nothing to do with online poker. PokerDIY provides tools and leagues to help the management of home poker tournaments). This has resulted in a lot of new users (obviously the poker market is in a bit of a bubble these days and is a lot larger than the DotNetNuke market) and it gives us the chance to see our modules stress-tested and understand how users actually want to use our modules from a usability point of view better.
Currently PokerDIY is using the Events module to organize games and tournaments (a good example of customized category lists), as well as the UserProfile to show different player profiles. The HomePage module will probably not be needed at this stage. Other 3rd party modules are Scott’s (Ventrian) Private Messages, News Articles and Feedback Center (so owe can get user’s requests and not only developer-centric requests) and of course the usual DNN Core modules such as the Forums, links, FAQ etc.
Please note that we still have a lot of work to do on PokerDIY but it is a fully functional, live website and is being used by home poker players all over the world.
We’d appreciate your help in helping us build PokerDIY into the useful website that it is striving to be, and at the same time helping us stress test and improve the Smart-Thinker Product Suite. If you know of any poker players, and specifically poker players who organize games or tournaments at home, please do us a favor and mention PokerDIY.
Alternatively, if you don’t have an interest in poker, feel free to check out the website and have a browse around to see how we have implemented the Smart-Thinker solution.