Pampering the Chef
For the few folks that read my blog, I would like to announce that a friend of mine, Audrey Montgomery, recently asked me on Facebook to become a fan of her Pampered Chef consulting.
I did that and will do one better, I will link to her Pampered Chef site from my blog here. Yup leveraging the potentially dozens of folks that read this.
Sarcasm aside, I have been blessed with the opportunity to attend some parties where Audrey has performed her magic using the Pampered Chef accessories and her cooking skillz.
While, I tend to get my supplies from the Mission Restaurant Supply company here in town, I took a look through her wares and saw a few items that I may purchase.
Measure-All Cup (like Alton Brown’s)
For those too lazy to click through to her site, here are some quick links.
I will go ahead and throw out my professional 2 cents (in terms of web stuff).
I think that it is very cool that The Pampered Chef company enables their agents/consultants with a relatively customizable site that they can personalize and brand a little bit. I would say that anyone doing any sort of reseller/agent type business model needs to be able to offer out that type of functionality.
That would be the good part of the critique, the bad part is that the application that their developers put together is in my opinion not ready for the ‘public web’. The URL structure that they use has query string data (being the stuff after the ‘?’). The first thing that you should learn these days about the query string is that indexing robots typically do not like URLs that have that, so using ModRewrite or what not to create clean URLs will greatly help with that kind of thing.
www.pamperedchef.biz/cookingwithaudrey?page=products-category&categoryId=22
With a little bit of reworking of their code they could use a structure like
www.pamperedchef.biz/cookingwithaudrey/products/category/22
or even a little bit more coding, they could give category 22 a name
www.pamperedchef.biz/cookingwithaudrey/products/category/new
Now for me. I am a HUGE fan of sub-domains. Though, I will admit the general public find these confusing, but there are tricks to get around that (little bit of header redirecting after the .com/, will make it easy for folks to be sent to the proper subdomain). The link could look like.
cookingwithaudrey.pamperedchef.biz/products/category/new
While, I am not sure if The Pampered Chef application knows to detect if it is being executed in an iframe, there are things that consultants, like Audry can do to add their own branding to these types of sites.
Register the domain ‘CookingWithAudrey.com’, setup a GoDaddy hosting account (the cheap one). Setup a simple HTML page that does an <iframe> and is set to pull up http://www.pamperedchef.biz/cookingwithaudrey?page=home
That would would allow you to go to the CookingWithAudrey.com and keep her private URL in the address bar. Would have to test it to see if there are any warnings that come up from the SSL layer when you try to do a checkout. If there are, then rather than doing an <iframe> the CookingWithAudrey.com domain name can do a simple redirect to her Pampered Chef site.
I would probably say that she might want to try and do a splash page, that has some photos of some of the stuff she has cooked and then has a graphic/button/link to take the user to her Pampered Chef site.
So ends my professional 2 cents bit.
Again, congrats to Audrey on the Facebook fan stuff and The Pampered Chef site.
back to the grind.
laterz