Semantics and Formatting"

This website contains links to software which is either no longer maintained or will be supported only until the end of 2019 (CKFinder 2). For the latest documentation about current CKSource projects, including software like CKEditor 4/CKEditor 5, CKFinder 3, Cloud Services, Letters, Accessibility Checker, please visit the new documentation website.

If you look for an information about very old versions of CKEditor, FCKeditor and CKFinder check also the CKEditor forum, which was closed in 2015. If not, please head to StackOverflow for support.

(New page: In the web development and design world we can identify two different segments when talking about the quality and the way pages are built: * Strongly skilled developers who are aware of s...)
 
(No difference)

Latest revision as of 23:28, 20 February 2008

In the web development and design world we can identify two different segments when talking about the quality and the way pages are built:

  • Strongly skilled developers who are aware of standards, accessibility and semantics, aiming to control every single aspect in their web sites, evangelizing their user base about the benefits of it.
  • Good developers, probably unaware about semantics, who aim to provide rich features to their user base, still having some control over it.

In HTML, the above needs are reflected in markup, which can be grouped in semantics markup, for the first segment, and formatting markup, for the second one. But even if we can identify those two groups, we are technically talking about the same thing: markup.

Inside V3, we aim to provide features so developers can precisely setup the editor to their needs and preferences. There is no specific separation for semantics and formatting though, as in the UI level both behave in the same way. Because of that we join semantics and formatting into a unique name: styles.

This page was last edited on 20 February 2008, at 23:28.