Using Strapi to update MDX files on Github for Docusaurus

I’m investigating options for using Docusaurus v2 (stable release as of August 2022) for a large documentation site shared by multiple editors. Although its not difficult to edit md files on Github, its awkward to ask non-technical folk to use Github to generate documents or blog posts. Has anyone ever used Strapi to update md files on Github? One of the driving forces of Docusaurus was probably to eliminate the need for a headless CMS, but it assumes that all users are comfortable with Github. Any advice is appreciated.

System Information
  • Strapi Version: 4
  • Operating System:
  • Database:
  • Node Version:
  • NPM Version:
  • Yarn Version:

1 Like

I have the same issue, did you get any solution,

[Lifecycle APIs | Docusaurus](https://plugin in docusarus)

maybe we should try this

From your query are you manually creating the files for each page? That is a bit manual. How about using Strapi as a central point like an admin and having the posts for each page to be editable using ckeditor that can return data using an api in md. Use lifecycle api to get the data from docusaurus and using dynamic routes if you wish. If you are using Strapi then you may just need to setup the docs and should help as your docs grow larger.

Another way would be to actually code the docs in a framework you’re comfortable. I had to do that after a certain project documentation grew so large and docusaurus became a nightmare to maintain with multiple editors. If you need help, just reach out.

Hello! Your project integrating Docusaurus with Strapi CMS caught my attention, and I’m very interested in learning more about how to set it up. I’m particularly keen on understanding the workflow and any challenges you might have encountered during the process. Could you please guide me on how to best approach this integration? Additionally, I would appreciate any resources or tips you could share. How can I get in touch with you for further discussion?