Answer the question
In order to leave comments, you need to log in
What is the best engine for information sites?
Hi guys. I need an engine for information sites.
From the engine I need a quick and, most importantly, easy addition of my own functionality and changing the template.
And of course, it is interesting to listen to those who work in this niche.
Thank you.
Answer the question
In order to leave comments, you need to log in
For informational sites, static generators are best suited.
Arguments in favor of static generators and against most classic CMS for information sites:
1) Content is inconvenient to store in the database, as most CMS do.
If the content is in the database, then it is difficult to back up and restore it from a backup, it is inconvenient to compare versions before and after the change. It's hard to roll back changes in a particular article without affecting everything else. For all this, the CMS must be programmed with its own functionality.
If you store content in files (as all static generators do), then the “files + GIT” bundle provides an easy backup, comparison and restoration of entire content and individual articles at almost zero cost.
2) Content editors in the admin panel (TinyMCE, CKeditor) are usually inconvenient and often produce mediocre code. Also hard to set up. Content managers who know how to typeset still pull the code into a text editor, edit it there and paste it back.
It's faster to work with files right away in your favorite code editor. From this, you can get additional goodies in the form of highlighting the changed lines compared to the last commit and some others.
3) Markdown is supported by all static generators, and this is the most convenient language for writing content. Markdown compiles to high quality and clean HTML. Markdown can be mixed with HTML as needed.
4) With classic CMS, where the content is in the database, the developer has to keep the localhost and / or dev version of the site with a copy of the live database and synchronize them with each other. More often, synchronization is one-way (from live to localhost), because. it is difficult to merge bases and it is scary to break something on live. And in such cases, content creators have to do everything locally first, and then repeat it live.
With static generators, this is as easy as with files: you can render several versions for testing, make mirrors, etc.
5) Speed and safety. A static site is, by definition, faster than any CMS. The generated site is easy to put in a CDN and get the maximum opening speed under any load. And static sites are not hacked.
https://www.staticgen.com/— a list of all static generators, sorted by popularity.
I myself have been using docpad.org for three years now - a generator based on node.js. I wouldn't say it's the perfect tool. I'm on it because I already know it well, and I have collected a lot of developments for docpad, including automation.
I also note https://octobercms.com/ - a CMS that follows the principles of static generators. I haven't tried it myself yet, but if you need PHP support, then this is the first candidate.
Wordpress, although this is my preference, almost any will do.
Joomla - more than suitable.
Just like this: https://developers.google.com/open-source/gsoc/201...
Alto you can see. The problem is that one and a half people are sawing it, but it seems to be stubborn.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question