Brian Mark - Guitaraholic

I posted on a couple of forums (both private and public forums) about the site-wide HTML validation service that I'm working on and mentioned here yesterday . So far, the response has been overwhelming. Of course, people want it to do everything imaginable out of the box, but most of the things that have been asked of it are in the plans for down the road. Most people are happy to hear that it's at least in the plans. Now, as for pricing models, I have a lot of ideas there. Obviously this thing could get to be a bandwidth hog if I let everyone check every page of their site multiple times per day. So my plan is to have the free plan, the $5/month plan, the $20/month plan, $50/month plan and the $100/month plan. This will allow for different number of automated page checks per month based on the plan cost. Oh, and I plan on allowing to pay for 10 months for 1 year of service as well. But I'm not going to say exactly what's allowed for each pricing level yet. You'll ...

If you've ever tried validating a large site (more than 100 pages), you know why I say that's a huge headache. Well, I'm getting ready to roll out a full-site HTML validation service. It'll do all the checks of the W3's validator, using their tools in fact. But what it does differently is validate all of your pages automatically without having to check each one individually, with follow-up checks available. You'll even be able to sort them by most or least errors. Obviously I'm not going to be able to help everyone fix the errors, but I should be able to give them a list of errors to work from. If you're interested in this service, I'll have a form up fairly soon to be notified when more beta testers are being accepted as well as when the full roll-out occurs. Until that happens, you won't be able to use HTML Monitor , just the W3 validator .

That's right... I'm attempting HTML validation on our checkout pages. This process is a real pain, but it seems like one of the few places for me to look yet when trying to troubleshoot our MSN customer checkout problems . So far, it's been mostly forgetting to end fonts before the end of a td section, so it hasn't really changed anything. Oh, and forgetting a few # signs at the beginning of colors. I used to be terrible at that. But so far, quite a few errors corrected and nothing in the way of changing the phone overload problems we've been facing. I guess it's good that we're getting record sales yet, but imagine where we'd be if our site visitors could get things to work on their own. Who knows how much business we're losing as a result? I sure don't, but I have a guess, and that guess wouldn't make me happy if I dwelled on it too much instead of looking at other possible causes of the problems. As long as I keep busy, things seem much b...