|
|
|
|
|
by zapt02
3411 days ago
|
|
This smells of NIH to me. You built a presentation layer for WP in Ruby because that's what you are comfortable with. There's nothing wrong with that, but don't pretend that you are building anything other than (possibly) useless middleware. If you wanted a fresh stack with WP, you would use the WP API, Vue or React coupled with any caching software (Nginx, Varnish). |
|
Has been considered.
But there where many integrations that were required, and they are simply too simple in Ruby land. Also we needed to take traffic --yet serve dynamic pages-- and support user logins. The solution I mention does use WP-API, but on top of that it also allows "previews" and the "admin bar" (would be quite interesting to implement those with React).
edit: That we had a lot of Rails expertise in house did help, as mentioned. We also do plenty React, but a lot of the integrations needed to be server-side and many were batch-processes.