The Future of WordPress

Transcript

1. The  Future  of  WordPress Michael  Schofield  |  LibUX
2. Hi.  I’m  Michael! Good  to  meet  you.
3. Library  funds  are  better  used  investing   in  a  full-­‐time  WordPress  developer  than   most  third-­‐party  vendor  products.
5. Read my friends’ books :)
6. w3techs.com
7. Libraries  not  using  WordPress  yet  will  eventually. Bold claim, Schofield.
11. How  WordPress  works From  database  to  the  browser 1. Content  starts  in  the  database
12. How  WordPress  works From  database  to  the  browser 1. Content  starts  in  the  database
 2. A  theme,  written  in  PHP,  queries  the
 database  for  content.  This  is  called
 “the  loop.”

13. How  WordPress  works From  database  to  the  browser 1. Content  starts  in  the  database
 2. A  theme,  written  in  PHP,  queries  the
 database  for  content.  This  is  called
 “the  loop.”
 3. PHP  returns  HTML  on  the  server
 side,  and  the  browser  renders  the
 content.
15. How  WordPress  works with  the  WP  REST  API 1. Content  starts  in  the  database
16. How  WordPress  works with  the  WP  REST  API 1. Content  starts  in  the  database
 2. Functions  written  in  PHP  connect
 the  endpoints  for  the  API  -­‐  how
 content  is  queried  and  how  it  retrieves
 it  from  the  database.
17. How  WordPress  works with  the  WP  REST  API 1. Content  starts  in  the  database
 2. Functions  written  in  PHP  connect
 the  endpoints  for  the  API  -­‐  how
 content  is  queried  and  how  it  retrieves
 it  from  the  database.
 3. Instead  of  HTML  the  server  returns
 JSON
18. How  WordPress  works with  the  WP  REST  API 1. Content  starts  in  the  database
 2. Functions  written  in  PHP  connect
 the  endpoints  for  the  API  -­‐  how
 content  is  queried  and  how  it  retrieves
 it  from  the  database.
 3. Instead  of  HTML  the  server  returns
 JSON
19. How  WordPress  works with  the  WP  REST  API 1. Content  starts  in  the  database
 2. Functions  written  in  PHP  connect
 the  endpoints  for  the  API  -­‐  how
 content  is  queried  and  how  it  retrieves
 it  from  the  database.
 3. Instead  of  HTML  the  server  returns
 JSON
 4. —  and  JSON  can  go  just  about
 anywhere.
 
 All  at  once
20. “Get  your  content  ready  to  go  anywhere,   because  it’s  going  to  go  everywhere.” Brad  Frost
23. Create  once,  publish  everywhere C.O.P.E.
26. This can be
 WordPress
27. w3techs.com
28. Cool,  huh?
29. So,  what  does  this  mean  for  users?
30. So,  what  does  this  mean  for  users?
31. So,  what  does  this  mean  for  users?
32. So,  what  does  this  mean  for  users?
33. So,  what  does  this  mean  for  users?
34. So,  what  does  this  mean  for  users?
35. So,  what  does  this  mean  for  developers? “I  believe  quite  strongly  that  JavaScript   and  API  -­‐driven  interfaces  are  the   future  of  not  just  WordPress  but  the   web.” Matt  Mullenweg
36. So,  what  does  this  mean  for  developers? “I  believe  quite  strongly  that  JavaScript   and  API  -­‐driven  interfaces  are  the   future  of  not  just  WordPress  but  the   web.” Matt  Mullenweg
37. So,  what  does  this  mean  for  organizations?
38. So,  what  does  this  mean  for  organizations?
39. So,  what  does  this  mean  for  organizations?
40. How  much  do  libraries  spend  on  proprietary  software they  don’t  control?
41. Library  funds  are  better  used  investing   in  a  full-­‐time  WordPress  developer  than   most  third-­‐party  vendor  products.
42. Library  funds  are  better  used  investing   in  a  full-­‐time  WordPress  developer  than   most  third-­‐party  vendor  products.
43. Library  funds  are  better  used  investing   in  a  full-­‐time  WordPress  developer  than   most  third-­‐party  vendor  products.
44. Library  funds  are  better  used  investing   in  a  full-­‐time  WordPress  developer  than   most  third-­‐party  vendor  products.
45. Library  funds  are  better  used  investing   in  a  full-­‐time  WordPress  developer  than   most  third-­‐party  vendor  products.
46. Library  funds  are  better  used  investing   in  a  full-­‐time  WordPress  developer  than   most  third-­‐party  vendor  products.
47. Library  funds  are  better  used  investing   in  a  full-­‐time  WordPress  developer  than   most  third-­‐party  vendor  products.
48. Library  funds  are  better  used  investing   in  a  full-­‐time  WordPress  developer  than   most  third-­‐party  vendor  products.
49. Library  funds  are  better  used  investing   in  a  full-­‐time  WordPress  developer  than   most  third-­‐party  vendor  products.
51. Thank  you Michael  Schofield  |  LibUX