Tweet
Tweet

Slide 1

Slide 1 text

The  Future  of  WordPress Michael  Schofield  |  LibUX

Slide 2

Slide 2 text

Hi.  I’m  Michael! Good  to  meet  you.

Slide 3

Slide 3 text

Library  funds  are  better  used  investing   in  a  full-­‐time  WordPress  developer  than   most  third-­‐party  vendor  products.

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

Read my friends’ books :)

Slide 6

Slide 6 text

w3techs.com

Slide 7

Slide 7 text

Libraries  not  using  WordPress  yet  will  eventually. Bold claim, Schofield.

Slide 8

Slide 8 text

No content

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

How  WordPress  works From  database  to  the  browser 1. Content  starts  in  the  database

Slide 12

Slide 12 text

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.”


Slide 13

Slide 13 text

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.

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

How  WordPress  works with  the  WP  REST  API 1. Content  starts  in  the  database

Slide 16

Slide 16 text

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.

Slide 17

Slide 17 text

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

Slide 18

Slide 18 text

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

Slide 19

Slide 19 text

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

Slide 20

Slide 20 text

“Get  your  content  ready  to  go  anywhere,   because  it’s  going  to  go  everywhere.” Brad  Frost

Slide 21

Slide 21 text

No content

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

Create  once,  publish  everywhere C.O.P.E.

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

No content

Slide 26

Slide 26 text

This can be
 WordPress

Slide 27

Slide 27 text

w3techs.com

Slide 28

Slide 28 text

Cool,  huh?

Slide 29

Slide 29 text

So,  what  does  this  mean  for  users?

Slide 30

Slide 30 text

So,  what  does  this  mean  for  users?

Slide 31

Slide 31 text

So,  what  does  this  mean  for  users?

Slide 32

Slide 32 text

So,  what  does  this  mean  for  users?

Slide 33

Slide 33 text

So,  what  does  this  mean  for  users?

Slide 34

Slide 34 text

So,  what  does  this  mean  for  users?

Slide 35

Slide 35 text

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

Slide 36

Slide 36 text

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

Slide 37

Slide 37 text

So,  what  does  this  mean  for  organizations?

Slide 38

Slide 38 text

So,  what  does  this  mean  for  organizations?

Slide 39

Slide 39 text

So,  what  does  this  mean  for  organizations?

Slide 40

Slide 40 text

How  much  do  libraries  spend  on  proprietary  software they  don’t  control?

Slide 41

Slide 41 text

Library  funds  are  better  used  investing   in  a  full-­‐time  WordPress  developer  than   most  third-­‐party  vendor  products.

Slide 42

Slide 42 text

Library  funds  are  better  used  investing   in  a  full-­‐time  WordPress  developer  than   most  third-­‐party  vendor  products.

Slide 43

Slide 43 text

Library  funds  are  better  used  investing   in  a  full-­‐time  WordPress  developer  than   most  third-­‐party  vendor  products.

Slide 44

Slide 44 text

Library  funds  are  better  used  investing   in  a  full-­‐time  WordPress  developer  than   most  third-­‐party  vendor  products.

Slide 45

Slide 45 text

Library  funds  are  better  used  investing   in  a  full-­‐time  WordPress  developer  than   most  third-­‐party  vendor  products.

Slide 46

Slide 46 text

Library  funds  are  better  used  investing   in  a  full-­‐time  WordPress  developer  than   most  third-­‐party  vendor  products.

Slide 47

Slide 47 text

Library  funds  are  better  used  investing   in  a  full-­‐time  WordPress  developer  than   most  third-­‐party  vendor  products.

Slide 48

Slide 48 text

Library  funds  are  better  used  investing   in  a  full-­‐time  WordPress  developer  than   most  third-­‐party  vendor  products.

Slide 49

Slide 49 text

Library  funds  are  better  used  investing   in  a  full-­‐time  WordPress  developer  than   most  third-­‐party  vendor  products.

Slide 50

Slide 50 text

No content

Slide 51

Slide 51 text

Thank  you Michael  Schofield  |  LibUX