Workarounds to get lr files get parsed by Netlifycms or are there alternatives?

Basically the title. From Netlifycms doc:

It works with any content written in markdown, JSON, YAML, or TOML files, stored in a repo on GitHub, GitLab, or Bitbucket. You can also create your own custom backend.

I managed to make Netlifycms to be able to edit the content in a gitlab hosted project. But it destroys the files by creating e.g a frontmatter that cannot be parsed by lektor server later.

As far as I am concerned this issue should be closed since the answer is: no. It has been discussed in #532 , #439. Maybe rename this issue to “Let’s discuss the CMS future of the project”? (:

However, by the time Lektor was created it presented a new paradigm: a static site generator with a CMS. It could solve the author’s problem: the CMS could be installed in a computer as long as the website existed.

From a developer’s perspective Lektor is amazing and .lr files are way more flexible than the alternatives vastly used. Lektor still ships a CMS and it is bizarre how succinct and easy it is to model data to get presented/edited by the CMS. But all of that get useless if the non-technical users can not use it.

All my projects were moved to Lektor ('cause it rocks), and I would rather avoid coming back to Jekyll and Hugo. The Javascript kids (Gatsby, Nuxt) are solving someone else’s problems. But all of them make it possible to develop on the terminal and still get content managed (netlifycms, forestry.io etc). In my user’s use-case: a lektor project on gitlab-pages and with a CMS would be perfect.

• It would be amazing to add Lektor’s own CMS in the same way Netlifycms can be added to the project.
• If that’s not possible, I would be glad to use the terminal, have some of my technical users to install lektor and use its Admin/CMS, and the totally non-technical users using Netlifycms.

If there is no workaround to get .lr files parsed by Netlifycms, what kind of content management solutions does lektor’s userbase have available?

No rants at all, creating this issue because I do believe in Lektor’s future, and I would rather stay with Lektor even when not developing for personal use. Thanks all devs for the amazing work!

[runfalk]

I think the confusion is self-hosted/SaaS vs locally running on your own computer.

[mountainash]

@lsrdg Can you please confirm if you’ve seen that Lektor has and Admin interface? If not see https://youtu.be/lTWTCwuPdrU?t=189

I think some of the confusion about what you are requesting is based on your opinion of a CMS.

CMS = Content Management System.

Lektors /admin allows you (and non-devs) to manage content (text, images and other downloads). Were I work we have an internal/password protected server running lektor serve (Lektor in server mode where you can use the Admin). When Marketing/HR/Customer Service teams make changes to content through the “CMS” these changes are saved locally, when they use the publish button the changes are committed to git and then a CI using lektor build creates the static files which are copied to a live/prod server. Your pipeline can change for different environments - there are many easier choices in deployment built-in - Lektor is flexible.

While the CMS in Lektor is basic at this stage, it does the job and I’d still consider it a CMS. What are you needing that it doesn’t offer (also please raise as a new issue [if it doesn’t already exist])?