Content Types

Weceem provides many content types as standard. Each content type has a specific purpose, with different fields in the editor.

Some content types are directly rendered when requested, others are used by other content nodes to compose the page seen by the user.

If you have a custom Grails application using Weceem Plugin, you can easily create your own custom content types.

The following content types are supplied out of the box:

• Action - A server-side action that will execute the code in a Groovy Script node, for example to create new content nodes or send an email
• Blog - The root node of a Blog, which has Blog Entry nodes as children
• Blog Entry - An entry (child of) a Blog node
• Comment - A comment on a content node. Any nodes can have comments attached or created.
• External Link - A URL of another website. When this URI is rendered, it redirects to the external site
• Folder - A folder for grouping together content nodes and creating URI hierarchy
• Groovy Script - A piece of Groovy code to execute on the server, used by Action nodes
• HTML - A piece of HTML which may contain GSP (Grails Server Page) tags
• JavaScript - A piece of JavaScript source 
• Server File - A file uploaded to the Weceem repository and stored on the server filesystem, e.g. an image file
• Server Directory - A directory on the server filesystem which contains Server File nodes
• Stylesheet - A CSS style sheet
• Template - A GSP template used to layout and decorate the current content node
• Widget - A reusable GSP fragment for rendering sections of a page, e.g. a header/footer or a remote news feed.

The Template, Widget and HTML content nodes can use Weceem tags and other Grails tags to perform view rendering logic.