On Wed, 6 Apr 2016 14:36:49 +0300 Vladislav Mitov <vladislav.mi...@miracl.com> wrote:
> I agree with Jamal. We can build it with some kind of static site > generator for convenience, but we don't need this thing on the server > for sure. Indeed. Existing apache projects use a range of publishing models and templates. We could certainly ping infra about using the Apache CMS if some folks would prefer, but I think they'd want a pretty compelling case to support a whole new system. The most likely trigger to adopt it would be demand coming from a range of projects. As in, when git was introduced, or arguably even when svn replaced cvs! > > > That is why it is extremely important to have it clear, > > > understandable, and even more important - easy to access and edit > > > if needed. That is a problem to which many solutions are available. > > > > > > Having that in mind I want to raise a discussion here about using > > > a GRAV https://getgrav.org > > > This is flat file CMS, with no backend database to support. Is that a matter of familiarity and/or legacy? Are there existing docs managed by grav that want importing? Bear in mind that unless there's a pretty substantial legacy to deal with, committers can be expected to come from a range of different backgrounds and adapt to whatever tools are used for a particular project. -- Nick Kew
