I’ve been working with this for a couple days now. Installation couldn’t get any easier. Thumbs up on that.
But while I can see the definite benefits of Grav, I am also having to do a lot of digging in the code to find where things are located. There are still some obvious things that I still haven’t found.
From a hosting providers standpoint, this is going to be a hard-sell to customers. They need an easy to use admin panel, or an inline editor from the front side, to get done what they need done quickly and without the frustration of digging into the code.
There seems to be a hard-coded directive for the CSS and images. When I changed the files to the root directory or changed the subdirectory name of where Grav is located, it broke the site.
All in all, I’m looking forward to the future of Grav.
This will definitely make it easier for average users and will require less ‘poking-about’. We have however tried hard to document as much as possible, and if you have not already done so, I strongly suggest going through the documentation on http://learn.getgrav.org. The Lifecycle section especially with give you a good idea on how things function:
There are no hard-coded directives at all, however, Grav uses extensive caching so if you change something fundamental like a path, you need to clear the cache as I mentioned in the other forum post.
Please let us know if you have other questions! Thanks!