Not Your Father's CMS-Custom Clients for WordPress and Drupal - by Doug Johnson

A lot of the internet runs on CMS (content management system) software. WordPress is responsible for approximately 25% of all sites and while Drupal is only responsible for about 7%, they are usually major sites.

In the past, the CMS has been responsible for both content management and the front end display, but both projects have recognized that their content could be made more valuable if offered in an API format so that other tools could be used to create the front end or custom applications based on that content. And this also allows them to compete with frameworks like Laravel, Symfony and Zend Framework.

In this presentation, we will look at how to create a client to consume content from WordPress, using the WP-API, and from Drupal 8, using the API module. We will also look at how to offer custom content creation clients for those organizations that want to use apps rather than the provided CMS backend. We'll look at the benefits and liabilities and will cover some of the security issues involved.

BIO:
Doug Johnson has been at this since you had to build your own chips from sand over a campfire. But with the attention span of a gnat, he likes to learn new technologies as they come out and use them in real world applications.

He has developed web and desktop applications for companies from tiny shops to Fortune 500 companies. Although he has done work and taught a bunch of languages (19 at last count, depending on how you define language) he is currently working mostly with PHP and Javascript building web applications as page add-ons to web sites.