.ORG
/
news
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

(Grav GitSync) Automatic Commit from dan

This commit is contained in:
dan 2021-12-04 13:06:36 +13:00 committed by GitSync
parent 4d90fd1f89
commit e41ea25267
1 changed files with 10 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
pages/01.blog/our-news-blog-is-online-with-grav/item.en.md
View File

@ -8,19 +8,19 @@ taxonomy:
media_order: 'ts&grav.png'
aura:
author: dan
date: '01-12-2021 09:37'
published: false
date: '04-12-2021 12:40'
published: true
---
We are very excited to launch our new News section!
# WordPress, Drupal, Grav ... which one?!
After comparing a few options out there like WordPress, Drupal & co. we've decided to go with GRAV. Which is a great CMS (Content Management System) written in php. Actually just like the other two mentioned, but GRAV doesn't need a database. It stores data in a type of flat-file CMS that are organised in folders rather than in a database. Which makes it really quick and very lightweight.
GRAV's first release was in July 30, 2014, so it's relatively new compared to WordPress (2003) and Drupal (2001) for example, but it has become a well-known CMS alternative. GRAV is used by less than 0.1% of all CMS systems - [w3techs.com](https://w3techs.com/technologies/details/cm-grav). It's not much compare to the big one - WordPress has the market under control with a respectable [65.1%](https://w3techs.com/technologies/details/cm-wordpress) and Drupal's market share is [2.1%](https://w3techs.com/technologies/details/cm-drupal).
After comparing a few options out there like WordPress, Drupal & co. we've decided to go with GRAV. Which is a great CMS (Content Management System) written in php. GRAV is just like the other two mentioned, but GRAV doesn't need a database. It stores data in a flat-file CMS that are organised in folders rather than in a database. Which makes it really quick and very lightweight.
GRAV's first release was in July 30, 2014, so it's relatively new compared to WordPress (2003) and Drupal (2001) for example, but it has become a well-known CMS alternative. GRAV is used by less than 0.1% of all CMS systems - [w3techs.com](https://w3techs.com/technologies/details/cm-grav). It's not much when compared to the big one - WordPress has the market under control with a respectable [65.1%](https://w3techs.com/technologies/details/cm-wordpress) and Drupal's market share is [2.1%](https://w3techs.com/technologies/details/cm-drupal).
Take a look at the usage statistics of the most popular [Content Management Systems](https://w3techs.com/technologies/overview/content_management).
# Drupal or GRAV
Our main comparison at the end where Drupal and GRAV. Both have excellent security practices.
Our main comparison at the end were Drupal and GRAV. Both have excellent security practices.
Checking the latest vulnerability statistics on CVE-Details for [Drupal](https://www.cvedetails.com/product/2387/Drupal-Drupal.html?vendor_id=1367) and [GRAV](https://www.cvedetails.com/product/59205/Getgrav-Grav-Cms.html?vendor_id=20511), we moved more into the direction of GRAV.
And in the end, our news feeds are just a few letters and pictures. The others would be way too heavy for our little goal.
GRAV uses [Markdown syntax](https://learn.getgrav.org/17/content/markdown), which we prefer, and the configuration files/pages are in [YAML syntax](https://learn.getgrav.org/17/advanced/yaml), which you will find in many tools like Ansible, Kubernetes, Prometheus, Matrix ... just to name a few.
@ -28,10 +28,10 @@ So GRAV not only fits our needs, it also matches our infrastructure.
# Pinpress theme
After the decision was made, we started looking for a theme. And there are quite a few of them. Simple and easy to read was now the next goal. And a similar look to our main website, which is made via [Bootstrap](https://getbootstrap.com/).
The [PinPress theme](https://demo.getgrav.org/pinpress-skeleton/) seems to be a good choice and so far we don't really have anything to complain about. It was a bit difficult to adapt it to our design because the default theme settings didn't work as good as we thought.
The [PinPress theme](https://demo.getgrav.org/pinpress-skeleton/) seems to be a good choice and so far we don't really have anything to complain about. It was a bit difficult to adapt it to our design because the default theme settings didn't work as good as we thought but a little code sorted that out.
## Theme inheritance aka child theme
We started first with an [_Inheriting theme_](https://learn.getgrav.org/16/themes/customization#inheriting-manually) (child theme), with that we can make our changes and keep the possibility to update the theme without overwriting our changes.
We started first with an [_Inheriting theme_](https://learn.getgrav.org/16/themes/customization#inheriting-manually) (child theme), with that we can make our changes and keep the ability to update the theme without overwriting our changes.
Once we had everything ready, our first step was a "clean up". We've removed all third-party connections to get even more performance out of GRAV to achieve a better usability when reading our news and especially clicking through the content, but also for us while we work on it.
In order to host everything directly from the server, we also decided to download [Fork Awesome's](https://forkaweso.me/Fork-Awesome/) icon pack. Yeah, they are really ... awesome!
Finally, we gave the theme our personal touch like favicon, logo, footer etc. and changed the [twig files](https://en.wikipedia.org/wiki/Twig_(template_engine)) to our needs.
@ -69,16 +69,15 @@ MIT License text & copyright notice must still be included with any unmodified M
# Conclusion
The outcome is now visible and we are very happy with it.
But not everything is perfect. There is one big problem GRAV has, especially for news and blog writers. Posting news automatically to various media channels will still be a hassle in 2021. Probably even in 2022, which is not far away. You need to post your messages manually or find other solutions like [IFTTT](https://ifttt.com/explore/new_to_ifttt).
Our plan is to publish news every two weeks or weekly. It's fine for us to manually post this on social media until we find another solution that suits us.
But not everything is perfect. There is one big problem GRAV has, especially for news and blog writers. Posting news automatically to various media channels will still be a hassle in 2021. Probably even in 2022. You need to post your messages manually or find other solutions like [IFTTT](https://ifttt.com/explore/new_to_ifttt).
Our plan is to publish news every two weeks or monthly. It's fine for us to manually post this on social media until we find another solution that suits us.
So we will see what the future will bring and how GRAV works in the long run.
If you want to read more about GRAV check the link - [What is Grav?](https://learn.getgrav.org/17/basics/what-is-grav)
# What next?
As we mentioned in [conclusion](#conclusion) our plan is to publish news every two weeks or weekly.
To allow you to follow our news as you like, we have set up a few more social media accounts. You can find the links in the gray box at the top right or below the news, depending on your device/resolution settings.
We are in the process of setting up a few more social media accounts to allow you to follow our news as you like. You can find the links in the gray box at the top right or below the news, depending on your device/resolution settings.
@reddit followers
Not every article will be published in our subreddit. Reddit rules are not meant to promote yourself, so we will only post information about privacy and other things without promoting our news/blog. This means that any changes to TECH SAVIOURS will only appear on the other channels.