There are multiple levels of customization that you can leverage when applying a different skin to Enunciate's generated documentation. From simplest-but-least-powerful to most-complex-but-most-powerful, these are:
- Custom CSS stylesheet
- Custom Documentation Base
- Custom XSLT
You can customize at all three of these levels in one of two ways:
- The Enunciate configuration file
- Classpath lookup, such that you can just include a jar on your Enunciate classpath and Enunciate will automatically "find" your custom skin.
Custom CSS stylesheet
If you're happy enough with just adjusting some colors and fonts, you can apply your own CSS file to the Enunciate-generated documentation.
Custom CSS Via Enunciate Configuration File
Custom CSS Via Classpath Lookup
Enunciate will look for a file at /META-INF/enunciate/default.css on your classpath. If that file is found, it will be used as your custom CSS file.
Custom Documentation Base
A "documentation base" is simply a set of files that are used and referenced by the generated documentation. For example: images.
Custom Docs Base Via Enunciate Configuration File
Custom Docs Base Via Classpath Lookup
Enunciate will look for a file at /META-INF/enunciate/docs-base.zip on your classpath. If that file is found, it will be used as your custom documentation base.
Custom XSLT
If you need custom HTML, you will have to provide a custom XSLT file that will do what you need. The easiest way to do this is to start Enunciate's default XSLT file and edit it according to your needs.
Custom XSLT Via Enunciate Configuration File:
Custom XSLT Via Classpath Lookup
Enunciate will look for a file at /META-INF/enunciate/docs.xslt. If that file is found, it will be used as your custom XSLT.