Content deleted Content added
Gabldotink (talk | contribs) No edit summary Tags: Mobile edit Mobile app edit Android app edit |
m date format audit, minor formatting |
||
Line 1:
{{Short description|Software for editing HTML}}
{{
{{Html series}}
An '''HTML editor''' is a [[Computer program|program]] for editing [[HTML]], the [[Markup language|markup]] of a [[web page]]. Although the HTML markup in a web page can be controlled with any [[text editor]], specialized HTML editors can offer convenience and added functionality. For example, many HTML editors handle not only HTML, but also related technologies such as [[Cascading Style Sheets|CSS]], [[XML]] and [[JavaScript]] or [[ECMAScript]]. In some cases they also manage communication with remote web servers via [[File Transfer Protocol|FTP]] and [[WebDAV]], and [[version control systems]] such as [[Subversion (software)|Subversion]] or [[Git (software)|Git]]. Many [[word processing]], [[graphic design]] and [[page layout]] programs
==Types of editors==
Line 17 ⟶ 18:
===WYSIWYG HTML editors===
{{unreferenced
[[Image:W3c amaya 10 fullmode enwiki xfce4therapy.png|thumb|250px|[[Amaya (web browser)|Amaya]] 10 HTML editor]]
[[WYSIWYG]] HTML editors provide an editing interface which resembles how the page will be displayed in a [[web browser]]. Because using a WYSIWYG editor may not require any HTML knowledge, they are often easier for an inexperienced computer user to get started with.
Line 29 ⟶ 30:
;Different browsers and applications will render the same markup differently.
:The same page may display slightly differently in Internet Explorer and Firefox on a high-resolution screen, but it will look very different in the perfectly valid text-only [[Lynx (browser)|Lynx]] browser. It needs to be rendered differently again on a PDA, an internet-enabled television and on a mobile phone. Usability in a speech or braille browser, or via a screen-reader working with a conventional browser, will place demands on entirely different{{
;Web browsers, like all computer software, have [[computer bug|bugs]]
:They may not conform to current standards. It is hopeless to try to design Web pages around all of 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 suit the new bugs and the new fixes. It is generally considered much wiser to design to standards, staying away from 'bleeding edge' features until they settle down, and then wait for the browser developers to catch up to your pages, rather than the other way round.<ref>{{cite web|url=http://www.w3.org/People/Bos/DesignGuide/designguide.html |title=An essay on W3C's design principles |publisher=W3.org |access-date=2013-10-23}}</ref>
;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 we can tell from context and experience whether bold text represents a title, or emphasis, or something else. But it is very difficult to convey this distinction in a WYSIWYG editor. Simply making a piece of text bold in a WYSIWYG editor is not sufficient to tell the reader *why* the text is bold
;Modern web sites are rarely constructed in a way that makes WYSIWYG useful
:Modern web sites typically use a [[content management system]] or some other [[template processor]]-based means of constructing pages on the fly using content stored in a database. Individual pages are never stored in a filesystem as they may be 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.
Line 51 ⟶ 52:
|___location=Boston
|isbn=978-0-321-50363-3
}}</ref>
[[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 U.S., the [[Americans with Disabilities Act]] and in the UK, the [[Disability Discrimination Act]] place requirement on web sites operated by publicly funded organizations. In many other countries similar laws either already exist or soon will.<ref name="RefactoringHtml"/> [[Web Content Accessibility Guidelines|Making pages accessible]] is more complex than just making them valid; that is a prerequisite but there are many other factors to be considered.<ref>{{cite web|url=http://www.w3.org/TR/WCAG20/|title=Web Content Accessibility Guidelines (WCAG) 2.0|publisher=W3.org|year=2008|access-date=2013-10-23}}</ref>
Whatever software tools are used to design, create and maintain web pages, the quality of the underlying HTML is dependent on the skill of the person who works on the page. Some knowledge of HTML, CSS and other scripting languages as well as a familiarity with the current W3C recommendations in these areas will help any designer produce better web pages, with a WYSIWYG HTML editor and without.<ref>{{cite web|url=http://www.w3.org/MarkUp/Guide/ |title=Dave Raggett's Introduction to HTML |publisher=W3.org |date=2005-05-24 |access-date=2013-10-23}}</ref>
Line 68 ⟶ 69:
{{HTML editors}}
▲{{Use dmy dates|date=July 2011}}
{{DEFAULTSORT:Html Editor}}
|