MDN/Projects/Development/Git Backend: Difference between revisions

Jump to navigation Jump to search
Line 7: Line 7:
So, it might be interesting to look into swapping out Kuma's use of MySQL for version control and replacing it with a Git-based backend.
So, it might be interesting to look into swapping out Kuma's use of MySQL for version control and replacing it with a Git-based backend.


Other benefits could include:
Overall, this could offer a lot of generative opportunities to consume & manipulate the MDN document corpus:


* mirroring the entire public document corpus on GitHub
* mirroring the entire public document corpus on GitHub
** e.g. Content for 3rd party apps
* allowing the MDN document corpus to be manipulated by non-MDN tools and scripts
* allowing the MDN document corpus to be manipulated by non-MDN tools and scripts
** e.g. Don't like the Kuma editor? Build your own.
* accepting Pull Requests against the corpus, allowing for reviewable changes that span multiple documents
* accepting Pull Requests against the corpus, allowing for reviewable changes that span multiple documents
** e.g. Mass atomic page moves, external tools to update compatibility info across many pages


== Inspirations ==
== Inspirations ==
Confirmed users
920

edits

Navigation menu