Can we blame hosts for their poor HTML editors?
Description: A short article on HTML editors provided by Web site hosts.
Created: April 30th 2005
Notes: The full posting can be found at http://www.cameraontheroad.com/?p=429.
Doing some research on the Internet regarding WordPress and iPowerWeb, I ran into a post that one Lorelle VanFossen had written. In this piece, she gives a letter/email that she had written to iPowerWeb, a Web site provider, regarding their poor HTML editor. In addition, she also states that iPowerWeb should enforce some level of standard compliance upon Web site creators that are using their HTML editor.
I felt that while her warning was appropriate, it should be taken with a grain of salt. While it is true that most Web-based HTML editors work extremely poorly, especially those provided by hosts, most professionals, by which I mean non-amateurs, don't use such editors. In response to her posting, I posted the following comment (some typographical and grammatical mistakes have been fixed).
I have to disagree (and I apologize if this post of yours is quite old). One should not judge a web site host on the basis of its HTML editor.
Most people, for good reason, don't look at the HTML editor a host uses on their admin side.
Is this an oversight?
Hardly. HTML editors provided by hosts are notoriously bad. Its space and bandwidth that people are concerned about, and rightly so. Most people that are serious about Web sites don't use the editor that hosts provide them - why when you've got Dreamweaver, FrontPage, …?
If you know you're going to be away, but will need to update code, try something like the following:
1) Save the file as txt and upload to your server. Need to make a modification? Download the file (as txt), make the necessary modifications on the computer you are using, save, and then rename to .html. Upload the HTML version via your admin interface (or Windows explorer if you're setup to handle this). Then rename to .txt and upload your new plaintext doc. Then delete off of the computer you're using, unless you'll be using the same computer to modify code again.
2) Email yourself the HTML doc as an attachment. I've long done this with papers, and doing it with HTML docs is no different. After all, if you can enter your site admin chances are you can also check your email.
Those are just two suggestions to get around your situation from occurring. These have worked for me in a variety of situations, and I'm sure they can work for you, and anyone who stumbles upon this post via search like I did, as well :)
I completely stand behind these comments. From my own experience, those who rely upon host provided HTML editors either have to or are just beginning with the Internet, or have been using the HTML editor for so long that they can't work without it.
Those who really care about their code either use a local, versus a Web-based, application to create their HTML. For some, this means WYSIWYG applications such as FrontPage or Dreamweaver, while for others this means a text editor such as Notepad, WordPad, HTML-Kit, or a slew of other, non-WYSIWYG focused, programs.
There are indeed cases where, however, a hosts HTML editor would be necessary. For example, if an individual uses a WYSIWYG editor to generate their pages, yet is on a computer that does not have that WYSIWYG editor, they may have to use the host's editor (for perhaps their HTML knowledge is lacking).
Yet, I don't believe that such an individual would really care about standards, unless they programmatically cleaned up their normal WYSIWYG's code, for WYSIWYG programs are notorious for inserting unnecessary code that messes with almost every W3C standard. Therefore, if someone uses a WYSIWYG, chances are they don't look at their code all that often anyways. Of course, there are exceptions. Yet, I would still argue that one of these exceptions would know enough to not use a host's editor.
But perhaps I don't hold hosts to the standards that I should. Perhaps they should develop HTML editors that don't mess with people's code. Unfortunately, I have had the experience of using such HTML editors that don't mess with people's code, as they use a plaintext form to hold the data. For the vast majority of Web-based HTML editors, however, plaintext forms are going to be of little assistance - they need the WYSIWYG in order to generate their code, and couldn't care any less about the code itself.
So I suppose I'm trying to say that current host HTML editors serve a purpose, for a niche of individuals. For those who aren't in that niche, HTML editors serve little purpose at all, and are not something that gets an individual to choose one host over another. In fact, I'd be extremely interested in a host that actually has information regarding their Web-based HTML editor. For the number of years that I've been online, and the number of sites that I've checked out, I've seen not a single reference to the HTML editor that the host uses. After all, aren't they pretty much all the same? Are there really that many people posting to boards saying that x's HTML editor sucks compared to their old host y?
- Review: Cooler Master CK550 Gaming Mechanical Keyboard
- Review: Fisher-Price Rock-a-Stack & Baby's First Blocks Bundle [Amazon Exclusive]
- Review: Summer Infant 3DPac Stroller
- Review: Sony SRS-XB31 Portable Wireless Bluetooth Speaker (SRSXB31/Ll)
- Review: Under Armour Vacuum Insulated Stainless Steel 18 Ounce Tumbler
Support This Site
If my blog was helpful to you, then please consider visiting my Amazon Wishlist.