Semantic Typography: Bridging the XHTML gap : Journal : Mark ...
Popularity Report
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
URL Tag Cloud
- web
- , design
- , semantic
- , xhtml
- , typography
- , html
- , css
- , markup
- , type
- , standards
- , semantics
- , informationdesign
- , forbook
- , webdesign
- , xml
- , article
- , ajax
- , web2.0
- , development
- , webstandards
Bookmark History
Saved by 11 people (-1 private), first by anonymouse user on 2006-03-02
- Bashford on 2008-03-27 - Tags design , development , html , semantics , type , typography , web
- Zomigi on 2007-08-21 - Tags article , forbook , html , markup , semantic , webstandards , xhtml
- Johnydada on 2007-01-23 - Tags css , design , webdesign , standards , semantic , typography , xhtml
- Armandoalves on 2006-02-23 - Tags Web , Design
- Thedlab on 2006-02-23 - Tags Web , Design
Public Sticky notes
My HTML/Web design ‘skills’ are not only self-taught but also until recently old
skool until it hurt. Of course I appreciate the argument for semantic CSS etc
but I think what has been difficult for me in seeing the light has been thinking
in the correct manner. CSS/XHTML from a learning POV is awash with code-first
type of teaching - this example is another “moment of clarity” for me on my
journey to a better web.
Highlighted by joel
The document conceptual structure is retained, we now have our XHTML structure
(our semantic markup). Focussing then on the design we can make
the typographic structure match the conceptual structure (still retaining our
XHTML structure)
Highlighted by joel
Be presented, typographically, to match the document's conceptual model
The XHTML underlying the web page will also match the conceptual model
The meaning, or semantics, of the web page will match that
intended by the original document.
Highlighted by joel
The benefits of going through the process in this manner is that it's from a
designer's perspective, there's less of a leap conceptually into the land of
code where document structures are common place (OOP etc.) I've been following
this model for a couple of weeks now and it works pretty well. It streamlines
the process of assigning heading tags for example which have always been quite
arbitrary in the past.
Highlighted by joel


Public Comment