Hear Dan Munz, David Kennedy and Greg Boone discuss how CFPB was born, what challenges they faced and how WordPress became their CMS backbone throughout it all.

2. Today’s agenda
 A little background
 WordPress at CFPB
 Behavior-driven WordPress development
 View-source, the WordPress way!
2

4. 4

9. consumerfinance.gov
 Launched in February 2011 (5 months ahead of
schedule)
 The Bureau’s (only!) owned digital property
 Consumers are our core audience
 About 900K unique pageviews/month
9

11. Our stack
11

12.  Standard content types
 Good CM interface
 Distributed editorial
workflow
 Custom app development
 Highly interactive or
database-driven
 Infrequent content
updates
CMS vs. Framework?
12

13. More people
doing
fewer things
Fewer people
doing
more things
In other words
13

14. What we’ve learned
 WP is not (natively) a web application framework
 Some core capabilities are still maturing
 Easy to do things right; even easier to do things wrong
 Understand how Security thinks about OSS
14

15. Big hairy questions
 Consistently structuring complex taxonomies and data
relationships
 Pushing reusable code blocks into modules or plugins
 Making templating platform-agnostic
15

16. That’s how we’re thinking about WordPress…
…but how are we using it?
16

17. 17

19. The plugin
We needed an easier way to register:
 Post types with default settings
 Taxonomies with custom entry boxes
 Meta boxes
 Capabilities
We were doing it all in the theme; we transitioned to a
plugin with a UI.
19

20. How to know it’ll work
Two choices:
1. Manual entry of each post type, then manual entry of
one term for each taxonomy
2. Automated behavior testing!
20

21. Enter behave
Simple, scenario based tests…
 Scenario: Get more information about us
 Given I visit the homepage
 When I click the "About us" link
 Then I should be directed to
/about/
 Optionally, add an and condition after a when
or then
21
…organized into simple features!
 Feature: Transparency in the Bureau
 As a member of the public
 I want to learn more about this organization
 So that I can understand their work better
 And a real browser (Chrome) to perform them!

22. [DEMO]
22

23. Okay, so you can teach a computer to log in…
23
What about a real test?
1. Log in
2. Go to the Custom Post Type page
3. Create three post types
4. Deactivate all three
5. Re-activate all three
Total execution time: 33 seconds (with about half of that going to wp-
login)

24. Benefits of testing
24
1. You know your plugin works
2. You can spot bugs on the fly
3. Programming toward specific behaviors
4. It's way faster than doing it all by hand
5. Eventually, you write better code.
6. You always know if the feature works or not

25. Still learning…
25
 It'd be nice to not have to log in _every_ time
 Writing the steps can be tricky (but it's python, so not too tricky)

27. We all start somewhere
27

28. But as we go, we learn
28

29. Building, building, building…
29

30. Embrace the WordPress community
They’re the source for solving your problems and giving
you inspiration to solve theirs…
 Automattic’s Github
 WordPress.org Forums
 Themeshaper.com
 WordPress.org Plugin Directory
 Also, blogs!
30

31. How is the CFPB “viewing source”?
 Hello Underscores! Forked; becoming our new base!
 WordPress goodness baked in.
 Miminimalistic; easily extendable.
 Solid framework and conventions
31

32. How is the CFPB “viewing source”?
 Talking it out with P2
 A trial run for managing our internal workgroups.
 Turns out blogs are great for conversations!
 A child theme allows us to brand it and extend it.
32

33. How is the CFPB “viewing source”?
 Going more modular
 Embracing <?php get_template_part() ?>
 We were already doing this, but where can we do it more?
 Find a best practice and ask how are we doing that?
33