Chapter 4. Points of Style
Style is an important concept in the AxKit world. Much of the value that AxKit adds as an XML publishing and application server lies in the flexibility and ease with which documents can be associated with one or more sets of transformations that can be selected dynamically in response to a condition. From more common web-publishing tasks, such as vendor co-branding and user customization, to more advanced dynamic data-oriented applications, the key to developing clean, manageable sites with AxKit lies in learning how to apply the appropriate styles to the content to meet the specific need. In this chapter, I introduce AxKit’s basic styling configuration options and show how these options can be combined to create sophisticated, responsive sites.
Adding Transformation Language Modules
Before you can begin associating documents with the stylesheets that
will be used to transform them, you must tell AxKit which lower-level
processors to use to perform those transformations. In AxKit, access
to various transformative processors is provided by its
Language
modules. Many of these modules create a bridge between AxKit and an
existing XML processing tool. For example, the
Apache::AxKit::Language::LibXSLT
module allows AxKit access to Perl’s
XML::LibXSLT
interface and, hence, to the Gnome project’s XSLT
processing library,
libxslt. Other
Language modules, such as AxKit’s implementation of
eXtensible
Server Pages,
ApacheAxKit::Language::XSP, are unique to AxKit and ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access