|
|
|
|
|
|
by matt4077
3385 days ago
|
|
|
To repeat a comment I made too late to be seen in the CMS announcement thread yesterday: I wish people would actually use open protocols instead of private APIs, at least in cases where both seem to be available. As far as I can see, the only feature this needs that only github provides is pull requests – omitting those would still leave you with a useful CMS, and the information could also be communicated in, for example, branch names. That way, you could conceivably use any client you want to work on the repo.
So instead of implementing Gitlab next, why not make it work with git? This situation reminds me of email clients and libraries, many of whom now use private APIs of a bunch of providers instead of SMTL and IMAP. |
|
|
Netlify CTO here.
You're right, everything that the CMS does currently could also be done with raw Git messages. The CMS is designed to have pluggable backends. We had an early version working with Git directly. We decided to focus in one backend at a time rather than having several half integrated because the core features were evolving too fast to support several backends initially.
We plan on support raw Git in the future again. It's a matter of making sure it's useful for more people other than developers that already know how to use Git.