3 ms·
the big alternative is static content - if you are just publishing a webpage, you can use something like Jekyll to manage your content and then it is "compiled
by paulmd 6y ago
the big alternative is static content - if you are just publishing a webpage, you can use something like Jekyll to manage your content and then it is "compiled to HTML".
For simple static content there really is no need for a database or anything at all, people just want the convenience of writing content dynamically and the database is a necessary evil in wordpress to make that happen.
If you need to handle a certain amount of user submissions (that can't be handled by forms/etc) you use JAM stack - javascript + API behind it.
- DigitalSea 6y agoIf you are a developer, a static site generator is the way to go. However, the point that so many developers seem to completely miss when they decide not to choose WordPress is the end user. There might be plenty of alternatives, but there are none (in my opinion) that even come close to WordPress' publishing experience. The admin panel is a refined UI, the publishing experience is really easy for people to grasp, it's the most user-friendly CMS around. What so many developers get wrong is that a lot of average users are used to writing in WYSIWYG environments like Microsoft Word. And despite Markdown being easy, once again, you lose the visual publishing experience in a lot of these static options. Markdown is easy for developers, but average users will struggle (especially with complex markup like tables or even images).