Thanks for your input. We've made the decision to keep our framework in WebForms and not move into asp.net MVC, even though I would love to. It was a close call with many considerations for and against, I assume many people would have had to make this decision before? What was your outcome? We just thought it was silly to rebuild something that was already working, instead we have spent the time optimizing performance of the webforms app.
So it doesn't matter all that much anymore but from a theoretical point I did look at the funnelweb code and I did find the way it used the routing engine to have custom templates. What I didn't find(prob cause I didn't look long enough) was a module ability. By module ability I'm specifically referring to having the ability to add multiple varied modules to a certain area on the template. So pagearea2(right column), can have the twitter module, facebook module and recent post module. Does funnelweb implement this? Actually, I'm just being lazy now I'll go have a dig around. Thanks. *Michael Ridland | ThinkSmart Digital* Managing Director P. 0404 865 350 E. [email protected] W. www.thinksmartdigital.com.au T. www.twitter.com/rid00z L. au.linkedin.com/in/michaelridland On Thu, Sep 15, 2011 at 9:03 AM, Corneliu I. Tusnea <[email protected]>wrote: > +1 - It's a good example of a very basic CMS but it shows the first set of > techniques you need to master in order to build a full CMS. > And the code is dead easy and dead simple to follow (once you get your head > around the IoC bit) > > > On Tue, Sep 6, 2011 at 3:35 PM, Jake Ginnivan > <[email protected]>wrote: > >> Check out FunnelWeb. It isn’t a full blown CMS, but is kinda a lightweight >> CMS/Wiki/Blog Engine using MVC3 and Razor.**** >> >> ** ** >> >> The code is much simpler than something like Orchard, so it could be a >> good place to start.**** >> >> >> We have our own theme engine, and you can select page templates >> (essentially a different master page) for each page, and also remove the >> blog chrome.**** >> >> ** ** >> >> http://funnelweblog.com/ **** >> >> ** ** >> >> Regards,**** >> >> *Jake Ginnivan >> *Readify | Senior Developer | MVP (VSTO)**** >> >> M: +61 403 846 400 | E: [email protected] | W: www.readify.net*** >> * >> >> ** ** >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Michael Ridland >> *Sent:* Tuesday, 6 September 2011 1:04 PM >> *To:* ozDotNet >> *Subject:* Writing a CMS in asp.net MVC**** >> >> ** ** >> >> Hi >> >> I'm struggling(well I have done for a long time) to get my head around how >> you would write a CMS in Asp.net MVC. >> >> It's really easy to understand how you do this in webforms, this is how I >> understand it and how I've done it before. >> 1. A CMS page is requested, I look up the information for a page >> 2. Locate the custom master page and set it >> 3. I iterate through the page details and then add the appropriate >> controls to the appropriate section on the master page >> >> I just don't understand how I would do this in ASP.NET MVC. >> >> How would/have you done this sort of solution in ASP.NET MVC?**** >> >> *Michael Ridland | ThinkSmart Digital* >> Managing Director >> P. 0404 865 350 >> E. [email protected] >> W. www.thinksmartdigital.com.au >> T. www.twitter.com/rid00z >> L. au.linkedin.com/in/michaelridland**** >> >> >> <http://au.linkedin.com/in/michaelridland>**** >> >> ** ** >> > > <http://au.linkedin.com/in/michaelridland>
