November 3, 2014
In January my team was looking for the best available Node.js content management system… and we picked WordPress! Our clients got all the benefits of WP’s content editing interface, and with the in-development REST API plugin we were able to use that content without limiting any of our other technology choices. This talk uses our project as a case study to share lessons we learned while building a Node client for the API, and why we’re so excited about what the next year holds for the evolution of WordPress as a content platform.
WordCamp San Francisco 2014 59
January 6, 2015 at 12:38 pm |
Slides: http://kadamwhite.github.io/talks/2014/wcsf-node-wp
LikeLike
January 6, 2015 at 12:49 pm |
Thanks, I added the slides link to the presentation.
LikeLike
September 20, 2017 at 11:16 am |
Reinventing wheel -ModX does all that for like last 5 years
LikeLike
October 10, 2017 at 8:42 am |
@kadamwhite , thank you for the talk. Even though it is old still very helpful and has helped confirm our team’s decision on using WP as CMS and Laravel strictly as the Control/View layer.
In the recent updates to API V2 do you see user management / authentication being possible strictly on the WP side or still needing to handle it natively in node (for your stack)?
LikeLiked by 1 person
October 10, 2017 at 8:44 am |
@kadamwhite , thank you for the talk. Even though it is old still very helpful and has helped confirm our team’s decision on using WP as CMS and Laravel strictly as the Control/View layer.
In the recent updates to API V2 do you see user management / authentication being possible strictly on the WP side or still needing to handle it natively in node (for your stack)?
LikeLike