No Description

Bachir Soussi Chiadmi 333ee13a91 Release Candidate 0.1 9 years ago
assets ad38015ea9 first commit : grave core and admin plugin 9 years ago
backup ad38015ea9 first commit : grave core and admin plugin 9 years ago
bin ad38015ea9 first commit : grave core and admin plugin 9 years ago
images ad38015ea9 first commit : grave core and admin plugin 9 years ago
system ad38015ea9 first commit : grave core and admin plugin 9 years ago
user 333ee13a91 Release Candidate 0.1 9 years ago
vendor ad38015ea9 first commit : grave core and admin plugin 9 years ago
.gitignore f2f2bf50bd created first user 9 years ago
.htaccess ad38015ea9 first commit : grave core and admin plugin 9 years ago
CHANGELOG.md ad38015ea9 first commit : grave core and admin plugin 9 years ago
LICENSE ad38015ea9 first commit : grave core and admin plugin 9 years ago
README.md ad38015ea9 first commit : grave core and admin plugin 9 years ago
composer.json ad38015ea9 first commit : grave core and admin plugin 9 years ago
composer.lock ad38015ea9 first commit : grave core and admin plugin 9 years ago
htaccess.txt ad38015ea9 first commit : grave core and admin plugin 9 years ago
index.php ad38015ea9 first commit : grave core and admin plugin 9 years ago
nginx.conf ad38015ea9 first commit : grave core and admin plugin 9 years ago
robots.txt ad38015ea9 first commit : grave core and admin plugin 9 years ago
web.config ad38015ea9 first commit : grave core and admin plugin 9 years ago

README.md

Grav

SensioLabsInsight Gitter

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

You have two options to get Grav:

Downloading a Grav Package

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

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