MVC4 is the current version, so I think MVC3 is a bit overdue for any new development if there should be any efforts in that direction w Razor instead of WebForms for YAF... I do my own site in MVC4 now, but I did start it out with MVC3 last summer... Had to redo/rethink a couple of things when updated, but MVC4 & .Net Framework 4.5 does it much better than MVC3 & 4.0...

He who asks a question is a fool for five minutes. He who does not ask a question remains a fool forever. [Old Chinese Proverb]

MVC4 is the current version, so I think MVC3 is a bit overdue for any new development if there should be any efforts in that direction w Razor instead of WebForms for YAF... I do my own site in MVC4 now, but I did start it out with MVC3 last summer... Had to redo/rethink a couple of things when updated, but MVC4 & .Net Framework 4.5 does it much better than MVC3 & 4.0...

MVC4 is the current version, so I think MVC3 is a bit overdue for any new development if there should be any efforts in that direction w Razor instead of WebForms for YAF... I do my own site in MVC4 now, but I did start it out with MVC3 last summer... Had to redo/rethink a couple of things when updated, but MVC4 & .Net Framework 4.5 does it much better than MVC3 & 4.0...

1. Finish the plugin architecture -- this would help with design decisions going forward.2. Minification3. API4. Open for discussion: Convert to Bootstrap CSS (with tons of existing themes) and Controls -- also less use of JQuery UI.5. MVC design that would minimize use of web form pages and specifically logic in the web forms.6. NuGet gallery for YAF.NET plugins and themes.

1. Finish the plugin architecture -- this would help with design decisions going forward.2. Minification3. API4. Open for discussion: Convert to Bootstrap CSS (with tons of existing themes) and Controls -- also less use of JQuery UI.5. MVC design that would minimize use of web form pages and specifically logic in the web forms.6. NuGet gallery for YAF.NET plugins and themes.

Not that I am asking you to explain yourself to me, but I would like to help somehow and if you could elaborate a little more on the items perhaps I could? I really love YAF and in anyway that I can help, I'd like to.

Plugin architecture for something like TapaTalk?

Minification? shrink lines of code?

API ... what would the intent/goal be?

I think from what you've said about Bootstrap, this would be HUGE for YAF.

My experience with MVC is that it's quite nice and very good for code reuse. Also, I think it might shorten up URL's too.

I'm not precisely beyond any doubt now. I can't shoot for it to be a definitive BB - I truly don't have that sort of time. The issue is there are heaps of gaps. To be perfectly honest, I would prefer not to fill them all. I am cheerful that a couple people (who are exceptionally useful) can make this thing work great and fill some of these voids. Yet, I am additionally an extremely bustling man – I simply would prefer not to see YAF bite the dust and I will help when I can, however not to the detriment of my life.