Mirror of Grav cms.
Go to file
2016-02-05 18:01:50 +01:00
assets Added empty assets folder 2014-08-17 15:55:56 -06:00
backup backup to backup folder 2015-04-27 21:45:42 +02:00
bin Init the URI object 2016-02-02 10:34:11 -07:00
cache Created a .dependencies and some other install cleanup 2014-08-06 19:58:51 -06:00
images Created a .dependencies and some other install cleanup 2014-08-06 19:58:51 -06:00
logs Created a .dependencies and some other install cleanup 2014-08-06 19:58:51 -06:00
system Linting fixes 2016-02-05 18:01:28 +01:00
tests Moved Parsedown tests to tests/unit/Grav/Common/Markdown/ParsedownTest.php 2016-02-05 16:59:51 +01:00
user Revert "no message" 2015-11-26 11:54:05 +01:00
webserver-configs LICENSE renamed to LICENSE.txt 2016-02-01 11:48:12 -05:00
.dependencies moved dependencies to master 2015-08-31 15:41:02 -06:00
.editorconfig Forcing 2 space indentation on all yaml files 2014-09-25 15:34:29 -07:00
.gitignore 🚧 Add error log for tests 2016-01-29 18:32:52 +01:00
.htaccess Ⓜ️ Merge branch 'develop' into feature/introduce-testing 2016-01-26 17:36:12 +01:00
.travis.yml Added Slack notifications 2016-02-04 11:24:45 -08:00
CHANGELOG.md Refractored Metadata generator. [BC included] 2016-01-29 10:13:14 -08:00
codeception.yml Drop default db config from config 2016-01-05 11:56:28 +01:00
composer.json Add composer test command for windows 2016-02-03 21:16:28 -05:00
composer.lock Composer update 2016-02-05 18:01:50 +01:00
CONTRIBUTING.md Add a contributing readme 2015-12-23 20:13:37 +01:00
index.php Remove all hardcoded older PHP required version, use GRAV_PHP_MIN constant instead 2015-12-28 18:46:14 +01:00
LICENSE.txt renamed LICENSE to LICENSE.txt 2015-12-01 11:15:00 -07:00
README.md Added automatic Unit Tests runner in Travis 2016-01-29 12:34:52 -08:00
robots.txt Prevent crawling of unnecessary directories 2015-11-20 19:33:24 -07:00

Grav Build Status

SensioLabsInsight ![Gitter](https://badges.gitter.im/Join Chat.svg)

Grav is a Fast, Simple, and Flexible, file-based Web-platform. There is Zero installation required. Just extract the ZIP archive, and you are already up and running. It follows similar principles to other flat-file CMS platforms, but has a different design philosophy than most. Grav comes with a powerful Package Management System to allow for simple installation and upgrading of plugins and themes, as well as simple updating of Grav itself.

The underlying architecture of Grav is designed to use well-established and best-in-class technologies to ensure that Grav is simple to use and easy to extend. Some of these key technologies include:

Requirements

QuickStart

These are the options to get Grav:

Downloading a Grav Package

You can download a ready-built package from the Downloads page on http://getgrav.org

With composer

You can create a new project with the latest stable Grav release with the following command:

$ composer create-project getgrav/grav ~/webroot/grav

From GitHub

  1. Clone the Grav repository from https://github.com/getgrav/grav to a folder in the webroot of your server, e.g. ~/webroot/grav. Launch a terminal or console and navigate to the webroot folder:

    $ cd ~/webroot
    $ git clone https://github.com/getgrav/grav.git
    
  2. Install the plugin and theme dependencies by using the Grav CLI application bin/grav:

    $ cd ~/webroot/grav
    $ bin/grav install
    

Check out the install procedures for more information.

Adding Functionality

You can download plugins or themes manually from the appropriate tab on the Downloads page on http://getgrav.org, but the preferred solution is to use the Grav Package Manager or GPM:

$ bin/gpm index

This will display all the available plugins and then you can install one or more with:

$ bin/gpm install <plugin/theme>

Updating

To update Grav you should use the Grav Package Manager or GPM:

$ bin/gpm selfupgrade

To update plugins and themes:

$ bin/gpm update

Contributing

We appreciate any contribution to Grav, whether it is related to bugs, grammar, or simply a suggestion or improvement. However, we ask that any contributions follow our simple guidelines in order to be properly received.

All our projects follow the GitFlow branching model, from development to release. If you are not familiar with it, there are several guides and tutorials to make you understand what it is about.

You will probably want to get started by installing this very good collection of git extensions.

What you mainly want to know is that:

  • All the main activity happens in the develop branch. Any pull request should be addressed only to that branch. We will not consider pull requests made to the master.
  • It's very well appreciated, and highly suggested, to start a new feature whenever you want to make changes or add functionalities. It will make it much easier for us to just checkout your feature branch and test it, before merging it into develop

Getting Started

Exploring More

License

See LICENSE

Running Tests

First install the dev dependencies by running composer update from the Grav root. Then composer test will run the Unit Tests, which should be always executed successfully on any site.

You can also run a single unit test file, e.g. composer test tests/unit/Grav/Common/AssetsTest.php