decaporg / decap-cms

A Git-based CMS for Static Site Generators
https://decapcms.org
MIT License
17.66k stars 3.02k forks source link

Move website to it's own repo #7068

Closed privatemaker closed 5 months ago

privatemaker commented 5 months ago

As I have been updating the documentation it comes to my mind- why does the website exist in this already very dense repo containing all the application logic? In recent years there was this "trend" towards monorepos, and with code projects including multiple related modules a monorepo makes sense vs. git sub-modules.

But why include a whole website which contains documentation and should be regularly updated and maintained? The one argument i've heard (from other projects) is this helps keep the documentation more up-to-date. Nice theory, but in practice (especially that of Decap CMS and my recent efforts to update Beta Features) just having the docs pages in the same repo does not help enforce such updating.

The very obvious benefits I see of a separate website repo are:

Apologies if this is a not-up-for-discussion topic due to history, but it seems like maybe under new leadership this is worth revisting.