...
Examples of how members of the Bedework community have implemented themes can be viewed by selecting from our listing on the Bedework website, "Who“Who's using Bedework?"”: http://www.bedework.org/bedework/update.do?artcenterkey=35
...
- Ongoing events: you can specify a category to mark events as ongoing, and display these events in a separate listing. By default, the category "Ongoing" “Ongoing” (as shipped with the quickstart's default data) is used to mark ongoing events.
- Featured events: the three graphics at the top of the default theme are "featured events"“featured events”. The images and links used are defined in bedeworkTheme/featured/FeaturedEvent.xml. If you choose to use featured events, you must (for now) maintain this xml file outside the Bedework system (either manually or using an outside process to write the xml file).
- Configurable event icons: the icons used to download or share events can be enabled and disabled by editing the themeSettings.xsl.
- Configurable header, footer, left-sidebar links, and favicon: all can be defined in the themeSettings.xsl file. By editing this file and manipulating the CSS found in css/bwTheme.css, it is possible to create a highly customized instance of Bedework without having to dig deeper into the xsl code.
...
There is a link in the footer of each web client that reads "show XML" “show XML” which adds this parameter to the query string for the current page. When manipulating the XSLT, this is the easiest way to understand the underlying XML that is being transformed.
...
where client is webclient, webadmin, websubmit, or feeder.
Each "page" “page” of an XML response takes the following form:
...
In most cases, the skins look first at the pageName found in the incoming XML and branch to an appropriate XSL template based on that. Look to the default template (the first in the stylesheets, matching on "“/"”) to see a listing of all incoming "pages" “pages” and their associated XSL templates. For example of this branching, look in
...
The key to understanding how the transformations take place, however, is to look at the underlying XML (by switching off the transform in Bedework using the "noxslt“noxslt=yes" yes” parameter and viewing the page source) and recognizing how XPath expressions are used to locate the xml nodes for transformation.
...