Integrating Github and Wordpress can be simple

http://lanyrd.com/2014/djangocon-us/sdcyrf/

Transcript

1. Integrating Django and Wordpress Can Be Simple collin anderson collinanderson.github.io/djangocon2014slides
2. collin anderson
3. php user 2002-2006
4. Django user since 2006
5. one:ten communications
6. ~20 live Django websites for clients
7. ~20 live Django websites for clients • many started pre-1.0
8. ~20 live Django websites for clients • many started pre-1.0 • all are at least 1.6
9. ~20 live Django websites for clients • many started pre-1.0 • all are at least 1.6 • most can run against master (1.8) without warnings
10. situation client had 5-year-old WordPress site with a modified theme we built back in the day
11. situation and a Django site that was completely different.
12. problems mixing WordPress and Django
13. problem: security out of date WordPress frequently gets hacked
14. problem: plugins no one likes buggy plugins
15. problem: php once you taste python, there’s no going back “I don’t know how to stop it, there was never any intent to write a programming language […] I have absolutely no idea how to write a programming language, I just kept adding the next logical step on the way.” 
 - Rasmus Lerdorf, creator of php
16. problem: templates it’s no fun to combine php and django templates
17. problem: multiple databases maintaining two databases is twice the work
18. problem: apache i’m worried about mixing php and python
19. problem: apache i’m worried about mixing php and python well, Graham Dumpleton can tell you how to do it
20. problem: apache i’m worried about mixing php and python well, Graham Dumpleton can tell you how to do it
21. solution: Django everywhere
22. ok, do we use an open source blog app?
23. or, do we make our own blog model? so we have full control
 (and it’s fun)
24. if so, what fields?
25. how much work will it take to migrate?
26. how do you edit content? • raw HTML?
27. how do you edit content? • raw HTML? • install and configure TinyMCE?
28. how do you edit content? • raw HTML? • install and configure TinyMCE? • install and configure CKEditor?
29. how do you edit content? • raw HTML? • install and configure TinyMCE? • install and configure CKEditor? • teach the client Markdown?
30. how do you edit content? • raw HTML? • install and configure TinyMCE? • install and configure CKEditor? • teach the client Markdown? • teach them ReST?
31. images and videos? uploading and embedding
32. are you going to build?
33. are you going to build? • “read more” split
34. are you going to build? • “read more” split • comment moderation
35. are you going to build? • “read more” split • comment moderation • autosave
36. are you going to build? • “read more” split • comment moderation • autosave • revisions
37. are you going to build? • “read more” split • comment moderation • autosave • revisions • thumbnail for each post
38. are you going to build? • “read more” split • comment moderation • autosave • revisions • thumbnail for each post • media browser
39. are you going to build? • “read more” split • comment moderation • autosave • revisions • thumbnail for each post • media browser • etc
40. how long will this take? will there be bugs?
41. let’s keep it simple what if we…
42. use Django for everything else keep the Wordpress admin
43. apparently WordPress has a decent editing experience
44. apparently WordPress has a decent editing experience WYSIWYG html editor
45. apparently WordPress has a decent editing experience WYSIWYG html editor Autosave, Revisions
46. apparently WordPress has a decent editing experience WYSIWYG html editor Autosave, Revisions Media Library
47. apparently WordPress has a decent editing experience WYSIWYG html editor Autosave, Revisions Media Library Custom Key/Value meta data
48. apparently WordPress has a decent editing experience WYSIWYG html editor Autosave, Revisions Media Library Custom Key/Value meta data Comment moderation
49. apparently WordPress has a decent editing experience WYSIWYG html editor Autosave, Revisions Media Library Custom Key/Value meta data Comment moderation Mobile Friendly
50. apparently WordPress has a decent editing experience WYSIWYG html editor Autosave, Revisions Media Library Custom Key/Value meta data Comment moderation Mobile Friendly Pretty CSS
51. apparently WordPress has a decent editing experience it all Just Works out of the box few bugs WYSIWYG html editor Autosave, Revisions Media Library Custom Key/Value meta data Comment moderation Mobile Friendly Pretty CSS
52. apparently WordPress has a decent editing experience it all Just Works out of the box few bugs they’ve spent years improving
 the user experience WYSIWYG html editor Autosave, Revisions Media Library Custom Key/Value meta data Comment moderation Mobile Friendly Pretty CSS
53. post model aged well in 13 years I don’t need to think about what fields I need
54. time saver • few bugs in the admin. TinyMCE has already been decided and fully configured. • models and fields have already been decided • piece of cake to migrate (just start using the database :) • rapid development: it means i have more time for front-end and other sections of the website
55. but it’s php! yuck! didn’t we just go through how bad PHP/WordPress is?
56. keep it simple follow these rules
57. keep WordPress running using php-fpm (fpm = fastcgi process manager)
58. php-fpm is simple nginx.conf sudo apt-get install php5-fpm php5-mysql
59. php-fpm is simple nginx.conf sudo apt-get install php5-fpm php5-mysql (and if you’re not using nginx, why not?)
60. WordPress will keep itself secure
 (as scary as it sounds)
61. don’t touch WordPress
62. don’t install any plugins it opens you up to more problems
63. don’t write any php (except wp-config.php)
64. mysqldump wordpress | mysql django much easier to maintain and backup consolidate the databases
65. use django-wordpress github.com/sunlightlabs/django-wordpress
66. or do it from scratch • you get full control (and it’s fun!) • it’s really not that much work
67. inspectdb > models.py
68. set up ForeignKeys
69. queries are simple • Post.objects.filter(
 post_type='post',
 post_status='publish',
 )
70. rss/atom feeds are simple
71. parsing shortcodes: messy [caption id="attachment_3768" align="alignnone" width="612"] full of hacks!
72. comments are simple
73. disadvantages
74. disadvantages • php. we use Python because it’s simply better.
75. disadvantages • php. we use Python because it’s simply better. • I can’t support every possible feature of WordPress on the Django side, but I can support them as I need them.
76. disadvantages • php. we use Python because it’s simply better. • I can’t support every possible feature of WordPress on the Django side, but I can support them as I need them. • WordPress database could change over time, though has been pretty stable recently.
77. it’s simple
78. it’s simple • website up and running very quickly
79. it’s simple • website up and running very quickly • if I “shut off” WordPress, the website is still there, it’s just read-only
80. it’s simple • website up and running very quickly • if I “shut off” WordPress, the website is still there, it’s just read-only • always free to ditch WordPress and use django admin
82. a few anecdotes on
 web applications vs.
 web content part ii
83. content web pages
84. content web pages • content pages should work without Javascript
85. content web pages • content pages should work without Javascript • served via GET only
86. content web pages • content pages should work without Javascript • served via GET only • content pages generally don’t change per-person
87. content web pages • content pages should work without Javascript • served via GET only • content pages generally don’t change per-person • content shows up as Google search results.
88. content web pages • content pages should work without Javascript • served via GET only • content pages generally don’t change per-person • content shows up as Google search results. • generally read-only to the user.
89. content web pages • content pages should work without Javascript • served via GET only • content pages generally don’t change per-person • content shows up as Google search results. • generally read-only to the user. • easy to build, easy to cache
90. web applications
91. web applications • usually behind login, invisible to search engines
92. web applications • usually behind login, invisible to search engines • make use of POST and maybe other http verbs (REST)
93. web applications • usually behind login, invisible to search engines • make use of POST and maybe other http verbs (REST) • usually ok to require javascript, often javascript-heavy
94. web applications • usually behind login, invisible to search engines • make use of POST and maybe other http verbs (REST) • usually ok to require javascript, often javascript-heavy • user specific. user is editing things.
95. web applications • usually behind login, invisible to search engines • make use of POST and maybe other http verbs (REST) • usually ok to require javascript, often javascript-heavy • user specific. user is editing things. • much much harder to get right than content.
96. 
 WordPress is an application Django serves the content my case:
97. end of anecdotes
98. and, now for a really crazy idea for the future part iii
99. crazy idea for the future • rewrite WordPress admin php using Django • keep feature-full Javascript and pretty CSS in sync with upstream • enjoy life php-free • (though it would take a lot of work)
100. that’s all I got! thanks!