Quote:
Originally Posted by Alex Stroup
I'd never seen the unicode trick used for an entire site before (but it used to be a good way to hide email addresses from bots) but there are so many tools out there for re-enabling right-click that my recommendation would be that this is probably more trouble than it is worth and also completely blocks non-javascript users (according to our workplace stats, about 3% of surfers do so with javascript turned off). And more importantly, it will block many search engine crawlers since they frequently ignore javascript (Google seems to have you indexed, though).
|
I use webcryptpro, I can enable and disable exactly what I am encrypting. So I will do that next time I update. as you suggest below.
Quote:
Originally Posted by Alex Stroup
My recommendation would be to re-enable that stuff and watermark your photos and images. This will ease traffic to your site (while your text is indexed at Google, it seems your images are not) and make even theft a form of advertising (and theft will happen anyway if someone really wants to and it doesn't even require going around your code, all the photos are in their cache.
|
A good idea, since all my new images are not up yet, this might be the best and easier route.
Quote:
Originally Posted by Alex Stroup
I haven't done it yet but you might want to run your HTML and CSS through the W3C HTML and CSS validators to see if there are any big errors (though it will generally only find syntactical errors these are the cause of a lot of display disparities between IE and Mozilla browsers).
|
A very capital suggestion!
I will investigate this and do this, I'm all for having correct and readable code (of course you should have seen the horrible mess my hand/hard coded site was, UGH)
Quote:
Originally Posted by Alex Stroup
As for other products, if you're willing to pay, Dreamweaver is much superior to FrontPage though still not great. No WYSIWYG editor is great.
|
Not that money is an object and I have no problem paying for software, I'll have to look into it to see what I can come up with that will work for me.
Quote:
Originally Posted by Alex Stroup
By the way, another obvious coding problem is that you have your initial javascript declarations before the <head> section of the page. Browsers are generally smart enough to work with that, but it could cause problems (and will throw errors if you run the validators).
|
Hmm, I will look at that as well. Not sure if the original template is formatted this way or I stuck soemthing in the wrong place (the second is the more likely scenario)
Thanks for your wise consul and good advice!
Now, back to Firefox!