The Events module allows you to manage events and their attendees. It can be used to schedule various types of event like meetings, conferences, training sessions, social events, etc. Events can be displayed on your website in a calendar and you can let your website users to register for the events. Registered attendees can be managed in the module's user interface.

 

In the CMS, events are represented as standard documents stored in the content tree. The Event (booking system) document type (code name CMS.BookingEvent) is used for the events. Once you have some events in the content tree, you can use web parts of the module to display them on the live site and enable registration.

 

Web parts of the module are stored in the Events & Booking web part category. The Event calendar web part appears as a standard calendar, while events located in a configured path are displayed in respective day fields. It is possible to enable registration for the events by means of the Event registration web part, which enables registration for the event currently selected in the calendar.

 

In Developer's Guide -> Modules -> Events -> Publishing events, you can find an example demonstrating how these two web parts can be used together in a typical scenario. The example also shows how events to be displayed can be created. Another example is located in the Using the Event calendar with other document types topic — this one shows how the Event calendar web part can be used to display other document types than the default Event (booking system). The E-mail invitations topic in the same part of the guide provides information on invitation e-mails sent to new attendees when they perform registration to an event.

 

User interface of the Events module can be found in CMS Desk -> Tools -> Events. This is where you can see an overview of all events, view registered attendees and perform other related actions. Management of event attendees is described in the Managing attendees topic. Access to this part of the user interface, as well as to creating documents, can be limited by means of permissions. Their configuration is explained in the Security topic.

 

The Events internals and API sub‑chapter provides information about the database tables and classes used by the module, as well as examples of how booking events and their attendees can be managed using Kentico CMS API.

 

Page url: http://devnet.kentico.com/docs/6_0/contexthelp/index.html?booking_system_overview.htm