The scope of PageBlaster can be restricted, but (as far as I know) you can only pick the pages for it to exclude from caching/compression rather than which to include. Its done with RegEx expressions, so maybe theres enough flexibility there for you.

I use CATALook for the shopping sites. It was frustrating at first but now I have figured out how it works I really appreciate the dozens of configuration options and its skinning engine (works just like DNN skinning). The new AspDotNetStoreFront for DNN looks like it offers much more flexiblity in product setup and skinning but is actually weaker than CATALook in the area of order management (orders can't be split, or different items in the order shipped at different times, no returns can be recorded against the order, in fact no changes at all seem to be allowed to the order once it is placed). I was all set to switch to AspDotNetStoreFront when it came out but now I am sticking with CATALook until the order management side matures.

Yeah, I know what you mean shnar.  That's just the first time I saw DNN used as an adjective like that and thought it was funny.

I also use Catalook and really like it's flexability, bit I agree that the UI for administration could use some cleaning up.  Maybe put some of the less used features on other tabs, and work on the layout of the labels with long descriptions in them.  It really doesn't take long to get familiar with it though.

-----

Yes, you could create a negative exclusion in PageBlaster that would act as an inclusion.  It actually has a configuration section for includePaths using regex but I haven't yet found a need for it so I didn't document it.

I would like to answer this question while showing proper respect to everyone.

We have used Ektron for years, since it was Ektron Empower.  There are a lot of great things in their software.  I, in fact, have recommended it to many others.  It really has served us well and the content management features have allowed us to grow our website while only having 1-2 web developers at a University of 3000.  Ektron is a great fit for many companies. 

As a pure CMS, the wysiwig editor, approval chains, and versioning are far superior to DNN, although I am quite meddlesome.  I keep causing errors in the Editor, losing entire pages of content, having timeouts, etc.  Stupid me!  Now because of my issues, I have had bothered the Ektron Support Team too much.

Come to think of it, I've bothered their Support Team on a whole range of issues, but they solve them when they have time.  Like the old addage says, finding the right solution takes a long time.  Sometimes a very long time.  Of course it always helps when the Support Team listens and pays attention to details.  In our business it's hard to find Support Teams that listen well.  When they don't listen it just makes you want to give up.  Sometimes it feels like they're trying to make you give up.  I am glad Ektron works hard at this.

Another great thing about Ektron is how they constantly come out with new features.  However, I have a problem.  Whenever I try out a new Ektron features I struggle to make them work right.  Support is nice enough to have long conversations with me.  They point out exactly where I went wrong.  I try their fixes.  If things still don't work and I give up, it's my fault.  I am sure it must be my fault.  Support agrees that it's my fault.

As a side note, I wish more software companies in our business emphasized QA.  I wonder how many software companies out there get by and grow large without a formal QA department and QA procedures.

Funny, that also reminds me how I occasionaly run into code-bases for enterprise systems that feel like a mass a bubble-gum and masking tape.  I wonder why companies do that?  For example, take a system built on legacy ASP and keep slapping .NET classes around it.  Weird.  Why not go back and rebuild the core engine and the core features with a strong object base?  It's too bad.  It's so easy for companies to become preoccupied with adding new features that ultimately mean the core engine is neglected.  Of course it's good to know that Ektron is commited to doing things correctly in .NET going foward.

On another note, I would love to see Ektron develop a templating/skinning engine like DNN.  A focus in this area would be a great benefit.  Right now I prefer DNNs approach quite strongly.  That's my only complaint and the only I have to switch.