Creating your own module

Introduction

All your Java class files, third party jar files, JSP templates, resources and schemes go into your module. It is a very bad bad habit to include content in your module and let a user access it directly. Always keep your code separated from content. All content must go beneath the /sites folder in the OpenCms Virtual File System (vfs). When you want to supply documentation as web pages with your module, you can include those web pages in your module (preferably in a separate module that contains the documentation and maybe some demonstration pages only) and create an export point in that module to export the content to e.g. /sites/default when the module is imported. The user then can access the documentation in a normal way.

In this series of articles on OpenCms we will be implementing our own template and we will do that in our own module. Therefor I will create a module called info.rsdev.template that will serve as a container for our template.