One of the many great features about Wicket is that all its templates are plain XHTML, with only a handful of special, unobstrusive tags. This has a number of advantages over templating languages like JSP-taglibs or Smarty.
- Viewable in any browser – offline, without running a server.
- Wicket Tags don’t destroy markup, they are just added to provide hooks for the web application.
- Editable with existing, powerful webdesign software like Dreamweaver.
In this article, I want to focus on the last point, showing how to get the most out of combining Dreamweaver and Wicket. The goal is to have a functional offline-version of our Wicket application. All layout and design changes will be made to the actual Wicket templates – no more copy & paste between what your web designer made, and what you use in your application.