wassname/fullcalendar
1
0
Fork 0
mirror of https://github.com/wassname/fullcalendar.git synced 2026-08-08 11:19:25 +08:00
Code Issues Packages Projects Releases Wiki Activity

fix line breaks in readme

Browse Source
This commit is contained in:
Adam Shaw
2013-08-26 22:15:02 -07:00
parent 4aff669965
commit 532e9b08b7
1 changed files with 5 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
readme.md
+5 -14
View File
@@ -2,18 +2,13 @@
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](http://arshaw.com/fullcalendar/).
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](http://arshaw.com/fullcalendar/).
Getting Set Up
--------------
You will need [Git](http://git-scm.com/), [Node](http://nodejs.org/), and NPM installed.
For clarification, please view the
[jQuery readme](https://github.com/jquery/jquery/blob/master/README.md#what-you-need-to-build-your-own-jquery),
which requires a similar setup.
You will need [Git](http://git-scm.com/), [Node](http://nodejs.org/), and NPM installed. For clarification, please view the [jQuery readme](https://github.com/jquery/jquery/blob/master/README.md#what-you-need-to-build-your-own-jquery), which requires a similar setup.
Also, you will need to have the [Grunt](http://gruntjs.com/) build system installed globally (`-g`) on your system:
@@ -31,8 +26,7 @@ Enter the directory and install FullCalendar's development dependencies:
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:
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
@@ -42,8 +36,7 @@ Or, you can run a script that automatically rebuilds whenever you save a source
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:
When you are finished, run the following command to write the distributable files into the `./build/out/` and `./build/dist/` directories:
grunt
@@ -55,6 +48,4 @@ If you want to clean up the generated files, run:
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.
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.