- What features do you need? Do you really get it, or need third party anyway?
- Also, what isn't supported my the CMS anyway? Like Analytics? Image/media storage? Commenting?
- Database or flat file? Security risks?
- Do you add the content yourself, or let someone else add?
- Do you regret your decision when you website grows? Is it easy to migrate in / out?
- Does it need to be fast, or even online in production?
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (3)
I have tried creating one, blogdown-cms, which need MongoDB and Cloudinary.
The motive was not only customizable Markdown, but also
/api/qinspired by lunr. Eventually, the syntax get more complex, and require backend, due to page-metadata-parser, which will be CORS disabled, if you use in frontend.The content writers are supposed to install Node.js on their machine.
I actually at first also want I commenting engine, but it is need to let your user CRUD -- currently I use a fork of REMARK42, which does not originally support SPA.
I only expose
/api/qin production, not upload admin endpoint online at all. Still I cannot be sure about security.The markdown syntax is custom, and the result from the backend (page-metadata-parser) has to be store in the markdown; so it requires a little remembering and maintenance, not totally sure if I can maintain it.
Actually, I am not even sure if Markdown is the best idea. Rich Text Editor or WYSIWYG like QuillJS might be better.
Not totally sure if it is a good idea as well to couple third-party like Cloudinary in the CMS.
I wonder if I can use some third party CMS instead, probably also with Full-Text-Search or Elasticsearch.
We use WordPress all the time at work, mainly to allow anyone to make content changes.
However, I've also heard of using WordPress as just a blogging CMS and creating a website mostly from scratch. And then your website could pull WordPress posts into it for the blog only via WordPress's REST API.
So there's that option if you only want a CMS for the blogging portion of a site.
I mostly use WordPress for my clients, because it's intuitive, can be installed on affordable cPanel shared hosting and there is a lot of plugins, themes, you name it that elevate it. At least that's what my clients say.
I personally don't like WP so much because it actually slow and too many unnecessary process run in the background. Or maybe I ain't smart enough to understand how WP works and how I supposed to optimize it.