4 ms·
"used in production" is not the same as being a serious wordpress alternative. Would bet that none of those production deployments are without some non-negligib
by openrisk 2y ago
"used in production" is not the same as being a serious wordpress alternative. Would bet that none of those production deployments are without some non-negligible developer time investment.
On top of that (assuming that extra investment is possible / desirable) the abstractions layered on top of django are quite opaque and have a steep learning curve. Having to code standard CMS functionalities becomes an eye-rolling exercise.
- ruthmarx 2y ago> "used in production" is not the same as being a serious wordpress alternative. You only said you thought it wasn't ready for prime time, which I think a reasonable interpretation is that you were saying you didn't think it was ready for production use. > Would bet that none of those production deployments are without some non-negligible developer time investment. That's the thing, I think the time invested is pretty negligible. Especially when compared to maintaining wordpress and having to deal with plugin craziness. > Having to code standard CMS functionalities becomes an eye-rolling exercise. You only really have to setup models for pages, tags, categories etc, after that the editor is incredibly functional.