Skip to main content
Getting Started Installation & Setup Server requirements Hosting SSO Setting up your calendar How LWC Works Deployment Using your CMS Adding groups and users Group settings User settings Importing Importing events Linked calendars One-time imports Custom imports Creating shared assets Event types Tags Locations Images and Files Using LWC Getting oriented Logging in The LWC toolbar Changing user settings Events list Event display Bulk event management Filtering events Creating events The basics Event details RSVP Sharing and Privacy Canceling events Working with images and files Images Files Add your other calendars The basics Events stay in sync Customize linked events Other details Community Features Sharing events between groups Marking events as "shared" Suggesting events Finding shared events Sharing and privacy settings Public event submissions The submit form More things to consider Bulletins and internal communications Who can send Bulletins? Customizing group calendars All About Widgets Widget basics What's a widget? Why would you use one? The default events widget Deployment Customization Creating new widgets The basics Widget customization options Custom widget formatting The format argument Widgets in your CMS Advanced widgetology For Developers
Welcome to the LiveWhale Calendar user guide.

Our goal is to create a simple overview of our calendar product from start to finish: for event creators, marketing and communications professionals, and developers.

If you’re coming to this site as a calendar user— someone whose primarily use of LiveWhale Calendar is to post your events— then the Using LiveWhale Calendar section should contain all the information you need to get your work done.

Developers will find material of interest throughout this user guide, and if you’re going to be working with the calendar a great deal, you should probably become familiar with all of it. Don’t just skip to the “For Developers” section looking for the geek stuff. :) 

Marketing and communications staff should also be very familiar with the Using LiveWhale material— as you promote LWC around your campus, it’ll be helpful for you to have a good handle on using the product. (It’s very self-explanatory and easy to use, but there’ll always be a question or two.) The sections on Community Features and Content Strategy and Governance are tailored directly to communications staff.

What are we missing?

This user guide is intended to be a work in progress. We invite your feedback, and your suggestions for any topics that may not be covered (or covered sufficiently) in this guide. Please submit your suggestions below, and thanks for reading and using LiveWhale Calendar!

We take your feedback seriously. Please let us know how this user guide is working for you!

All fields marked with asterisk (*) are required.

required textarea field
required text field
e-mail address field


Table of Contents
Getting Started

This section covers topics related to installation and configuration, hosting, and initial setup (adding groups and users, importing events, and more).

Using LiveWhale Calendar

An introduction to LWC for calendar users, from the basics (like creating and managing events) to the not-quite-as-basics (like adding other event feeds to your calendars).

Community Features

Basics of sharing events, receiving public submissions, internal communications (primarily via Bulletins), and options for per-group customization.

Widgets and Widgetology

An introduction to LWC widgets— what they are, how they’re used, and how to create them (with an emphasis on end users but some more advanced topics for developers).  And that’s that.

Content Strategy and Governance

Ideas for managing a LiveWhale Calendar community— including some key decisions that communicators have to make about workflow and process, and some models in use at other schools.

For Developers

This section is a grab bag of topics, how-tos, links, etc. for developers who want to work with LWC under the hood. We’ll be expanding it as our developers get more engaged with this documentation; if there’s something you’d like to see here, hit us up.