An HTML editor is a computer program for HTML editing , the markup of a webpage . Although the HTML markup of a web page can be written with any text editor , For example, many HTML editors handle not only HTML, but also related technologies like CSS , XML and JavaScript or ECMAScript . In some cases they also manage communication with remote web servers via FTP and WebDAV , and version control systems such as SubversionGold Git . Many word processing , graphic design and page layout programs are not dedicated to web design , such as Microsoft Word or Quark XPress , also have the ability to function as HTML editors.

Types of editors

There are two main types of HTML editors: textual and WYSIWYG (what you see is what you get) editors.

Text editors

Text editors intended for use with HTML syntax . Some editors add feature templates , toolbars and keyboard shortcuts to quickly insert common HTML elements and structures. Wizards , tooltip prompts and autocompletion can help with common tasks.

Text editors Commonly used for HTML Typically include Either built-in functions or integration with external tools for Such tasks as version control , link-checking and validation , code cleanup and formatting , spell-checking, uploading by FTP WebDAV or, and structuring as a project. Some functions, Such as link checking or validation May use online tools , Requiring a network connection.

Text editors require user understanding of HTML and any other web technologies the designer wants to use CSS, JavaScript and server-side scripting languages.

To ease this requirement, but not limited to more than just color highlighting, but not considered WYSIWYG. These editors Typically include the option of using Windows pallet or dialog boxes to edit the text-based parameters of selected objects . These palettes allow editing parameters in individual fields, or inserting new tags by filling out an onscreen form, and may include additional widgets to present and select options when editing parameters (such as previewing an image or text styles) collapse HTML objects and properties.


WYSIWYG HTML editors provide an editing interface which resembles the page will be displayed in a web browser . Because using a WYSIWYG editor may not require any HTML knowledge, they are often easier to achieve.

The WYSIWYG view is achieved by embedding a layout engine . This may be custom-written or based on a web browser. The goal is that, at all times during editing, the rendered result should be represented in a typical web browser.

WYSIWYM (what you see is what you mean ) is an alternative paradigm to WYSIWYG editors. Instead of focusing on the format or presentation of the document, it preserves the meaning of each element. For example, page headers, sections, paragraphs, etc. are displayed as such in the editing program, and displayed appropriately in the browser.

Difficulties in achieving WYSIWYG

A given HTML document will have an inconsistent appearance on various platforms and computers for several reasons:

Different browsers and applications will render the same markup differently.
The same page may differ slightly in Internet Explorer and Firefox on a high-resolution screen, but it will look very different Lynx browser. It needs to be rendered differently again on a PDA, an internet-enabled television and a mobile phone. Usability in a speech or braille browser, or via a screen-reader working with a standard browser, will place demands on the HTML. All an author can do is an appearance.
Web browsers, like all computer software, have bugs
They may not conform to current standards. It is hopeless to try to design Web pages around the common browsers’ current bugs: each time a new version of each browser comes out, a significant proportion of the World Wide Web would need re-coding to follow the new bugs and the new fixed. It is more than just a question of design, staying away from ‘bleeding edge’ features until they settle down, and then wait for the browser developers to catch up on your pages, rather than the other way round. [1] For instance, no one can argue that CSS is still ‘cutting edge’, and [2] even if many WYSIWYG and other editors . [3]
A single visual style can represent multiple semantic meanings
Semantic meaning, derived from the underlying structure of the HTML document, is important for search engines and also for various accessibility tools. On paper, can we tell you about the situation? But it is very difficult to convey this distinction in a WYSIWYG editor. Simply making a piece of text in a textbook of the text is bold enough to tell the reader * why * the text is bold – what the boldness represents semantically.
Modern web sites are rarely made in a way that makes WYSIWYG useful
Modern web sites typically uses a Content Management System or some other template -based means of constructing pages on the fly using content stored in a database. Individual pages are never stored in a filesystem as they are designed and edited in a WYSIWYG editor, thus some form of abstracted template-based layout is inevitable, invalidating one of the main benefits of using a WYSIWYG editor.

Valid HTML markup

HTML is a structured markup language . There are some rules on how to write the W3C standards for the World Wide Web . Following rules means clustering That thesis websites are available and are all kinds of computer Makes, to able-bodied and people with disabilities, and it aussi Wireless like devices mobile phones and PDAswith their limited bandwidths and screen sizes. However, most HTML documents on the web do not meet the requirements of W3C standards. In the most popular web sites, 94 percent of websites fail the web standards and markup style and validation, or apply character encoding improperly. [4] Even those syntactically correct documents may be inefficient due to an unnecessary use of repetition, or based upon rules that have been deprecated for some years. Current W3C recommendations in the field of CSS with HTML were first formalized by W3C in 1996 [5] and have been revised and refined since then. See CSS , XHTML ,W3C’s current CSS Recommendation and W3C’s current HTML recommendation .

These guidelines emphasize the separation of content (HTML or XHTML) from style (CSS). This is the advantage of delivering information for each site, let alone in each HTML element. WYSIWYG editor designers have been struggling with the best reality. Modern WYSIWYG editors all succeed in this to some extent, but none of them

However, it is possible to maintain the ability to maintain the ‘worldwide’ value of the Web itself. of valid markup and code. [6] It shoulds not be regarded ready for the World Wide Web, up to icts HTML and CSS syntax-have-been successfully validated using W3C validator Either the free services ( W3C HTML Validator and W3C CSS Validator ) or Some Other alternatives trustworthy. [6]

Accessibility of web pages by those with physical, eyesight or other disabilities is not only a good idea considering the ubiquity and importance of the web in modern society, but is also mandated by law. In the US, the Disability Actand the United States Disability Discrimination Act places requirements on websites operated by publicly-funded organizations. In many other countries similar laws [6] Making pages accessible is more complex than just making them valid; that is a prerequisite but there are many other factors to be considered. [7] Good web design, whether done using a WYSIWYG tool or not needs to take into account these too.

Some software tools are used to design, create and maintain web pages, the quality of the underlying HTML. Some knowledge of HTML, CSS, and other scripting languages. W3C. [8]

See also

  • Comparison of HTML editors
  • List of HTML editors
  • Web template system
  • Website builder
  • Validator


  1. Jump up^ “An essay on W3C’s design principles” . . Retrieved 2013-10-23 .
  2. Jump up^ “Cascading Style Sheets” . . Retrieved 2013-10-23 .
  3. Jump up^ “Cascading Style Sheets” . . Retrieved 2013-10-23 .
  4. Jump up^ “Responsive Web Design, Domain Registration, Web Hosting” . . Retrieved2013-10-23.
  5. Jump up^ “Cascading Style Sheets, level 1” . . Retrieved 2013-10-23 .
  6. ^ Jump up to:c Harold, Elliotte Rusty (2008). HTML Refactoring . Boston: Addison Wesley. ISBN  978-0-321-50363-3 .
  7. Jump up^ “Web Content Accessibility Guidelines (WCAG) 2.0” . 2008 . Retrieved 2013-10-23 .
  8. Jump up^ “Raggett’s Dave Introduction to HTML” . 2005-05-24 . Retrieved 2013-10-23 .