GitXplorerGitXplorer
m

meduz-articles

public
0 stars
0 forks
0 issues

Commits

List of commits on branch master.
Unverified
33f1fdb47f37547403576e22d9f05d1fa81bef9c

Update Grav to 1.0.10, Admin Panel to 1.0.9.

committed 9 years ago
Unverified
f70b44de38e463ba2c787fb47c09279ea03c4472

Update Grav to 1.0.9, Admin Panel to 1.0.8, and Gitignore with Github auth token

committed 9 years ago
Unverified
8daac17efc77a3619a7e34323441de3a3e664b07

Temporary about page

committed 9 years ago
Unverified
917c984377d05f15566da2e2f5bd4ed6eef6eaf0

System config: Gzip enabled, Markdown extra, various default Admin Panel values

committed 9 years ago
Unverified
65e6c4a2e2e3197d8d42b22a6852a3ecdeb3cd47

Site infos updated

committed 9 years ago
Unverified
d468bf1d5c74f824ae8ac64a891b25bf96a1f679

Blank commit with Grav 1.0.8 and Admin Panel 1.0.6

committed 9 years ago

README

The README file for this repository.

Grav

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

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