Introduction: Grav CMS

I have tried using grav content management system several times.  It is lightweight grown rather popular in recent years. Php based, and  does not use a database. In the past I have had challenges with its twig templating and over successive failures. In the first week of March 2020, I decided to give it another try. 

(This page was created using a speech to text program, and has several errors which I will correct within one week of publication of this post)

My Story with Grav

image of login page for grav cms using admin plugin.Blog of Amar Vyas

I realized that it is not really worth struggling with it. More often than not, things have broken down, when I installed a theme, or a plugin, or changed a parameter or two. In majority of cases, it was not knowing what went wrong was the real cause of frustration. More on that later.

Image: Installation of Grav on a NAT VPS (Virtual Private Server) with 128 MB RAM

Login page for Grav

So, the reason for using graph, was I wanted something lightweight. Something that supports markdown. It’s a form of language, like HTML, that I like to use, and have grown, particularly fond of in recent years. Thirdly, the idea was not to load up this site with multiple PDF files, and other heavy documents, rather, this would focus, largely on text. I recall reading in one of the documentation for graph that 1000 pages can be supported with ease that in mind. Since my current goal is to write 100 posts for the next hundred days, I believe, graph suffices the requirements for now without having to install too many plugins as might be the case for WordPress, or templating. That has been the case with some other content management systems, even within graph, I tried four different ways of installation. One was on a VPS or a virtual private server, which still exists, by the way, it’s a documentation site that I’m developing for a proposed book. More on that in a later post. Secondly, I tried installing using softaculous, the stock installation. And right to tweak customize the theme on a different web host, or a shared host, which is smallweb.net.

READ
Blogging Challenge: The Problem of Plenty

Update : this site is hosted on a VPS as on May 6, 2020
Third, I tried uploading the standard installer on this particular server early and try to tweak it along with the admin plugin. Things broke, as always, because the theme I wanted had certain templates or tweaks that the stock graph installed did not like, as I mentioned before, I did not want to spend too much time in tailoring or customizing. Therefore, I moved to a standard setup, or skeleton, as it is called within the graph world, and started reusing or repurposing, some of the content that was already there in during the folder structure. The links etc. Even within that. I tried Sora article hipster. And then also, I tried Saturn, as three options, hips, as a theme or skeleton that I particularly like right now I’m still trying to figure out how to introduce page breaks so that on the front page as you come to the site. The whole post does not show, you would see the first 200 characters or so, and then see the more something to work on. But that’s my story with graph. I was first introduced to it in 2018 mid 2018. So here we are almost a year and a half later, I am actually using it on this writing site. Hopefully, with a longer term goal. I have of course installed it multiple times and uninstalled it as well, because of the frustrations for the twig templating Like I said before, now as a content creator, as a writer. If my task or requirement is to find the easiest least cumbersome way of writing and creating awesome content. I should not really be struggling with aspects such as templating plugins, you know, maintenance, etc. So, this is what kept me away from graph. Finally, used one of the stock skeleton sites, hopefully this will work.

READ
Relaunch of this blog and website

Error on Grav CMS- Example

server error in Grav CMS