Full-sized drag & drop event calendar (jQuery plugin)
JavaScript CSS Other
Pull request Compare This branch is 106 commits ahead of PaulAik:master.
Latest commit e30d4b0 Sep 17, 2013 @josephleniston josephleniston Merge pull request #11 from amsross/resource_filter
Fixed incorrect property reference when filtering resources
Failed to load latest commit information.
build move Bower and CDNJS configs into build folder Mar 30, 2013
demos merge May 1, 2013
tests fix [unreleased] bug with event text overflow Mar 18, 2013
.gitignore merge May 1, 2013
Gruntfile.js tweak grunt clean:cdn command Mar 30, 2013
fullcalendar.jquery.json update changelog/meta for 1.6.1 Apr 15, 2013
license.txt change to single MIT license. update banners in source files Mar 11, 2013
package.json Make ResourceView compile May 1, 2013
readme.md updated docs for development workflow. added grunt dev command Mar 17, 2013


FullCalendar - Full-sized drag & drop event calendar

This document describes how to modify or contribute to the FullCalendar project. If you are looking for end-developer documentation, please visit the project homepage.

Getting Set Up

You will need Git, Node, and NPM installed. For clarification, please view the jQuery readme, which requires a similar setup.

Also, you will need to have the Grunt build system installed globally (-g) on your system:

npm install -g grunt-cli

Then, clone FullCalendar's git repo:

git clone git://github.com/arshaw/fullcalendar.git

Enter the directory and install FullCalendar's development dependencies:

cd fullcalendar && npm install

Development Workflow

After you make code changes, you'll want to compile the JS/CSS so that it can be previewed from the tests and demos. You can either manually rebuild each time you make a change:

grunt dev

Or, you can run a script that automatically rebuilds whenever you save a source file:


You can optionally add the --sourceMap flag to output source maps for debugging.

When you are finished, run the following command to write the distributable files into the ./build/out/ and ./build/dist/ directories:


If you want to clean up the generated files, run:

grunt clean

Writing Tests

When fixing a bug or writing a feature, please make a corresponding HTML file in the ./tests/ directory to visually demonstrate your work. If the test requires user intervention to prove its point, please write instructions for the user to follow. Explore the existing tests for more info.