The StartUp Agency - A Case Study on CFPB
 

The StartUp Agency - A Case Study on CFPB

on

  • 12,803 views

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.

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.

Statistics

Views

Total Views
12,803
Views on SlideShare
1,226
Embed Views
11,577

Actions

Likes
0
Downloads
2
Comments
0

13 Embeds 11,577

http://vip.wordpress.com 11460
http://cloud.feedly.com 45
https://vip.wordpress.com 24
http://news.google.com 18
http://www.newsblur.com 10
http://translate.googleusercontent.com 5
http://digg.com 4
http://reader.aol.com 3
https://www.google.co.in 2
https://translate.googleusercontent.com 2
http://newsblur.com 2
http://yoleoreader.com 1
http://www.goread.io 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Unique agency:Explicitly consumer-focusedFocus on product, regardless of institutionBanks and nonbanks for first timeUDAAP, not safety and soundnessFull range of toolsResearch and analysisSupervisionEnforcementRule-writingConsumer educationComplaint resolutionBorn digital

The StartUp Agency - A Case Study on CFPB The StartUp Agency - A Case Study on CFPB Presentation Transcript

  • Today’s agenda A little background WordPress at CFPB Behavior-driven WordPress development View-source, the WordPress way!2
  • 4
  • consumerfinance.gov Launched in February 2011 (5 months ahead ofschedule) The Bureau’s (only!) owned digital property Consumers are our core audience About 900K unique pageviews/month9
  • Our stack11
  •  Standard content types Good CM interface Distributed editorialworkflow Custom app development Highly interactive ordatabase-driven Infrequent contentupdatesCMS vs. Framework?12
  • More peopledoingfewer thingsFewer peopledoingmore thingsIn other words13
  • 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 OSS14
  • Big hairy questions Consistently structuring complex taxonomies and datarelationships Pushing reusable code blocks into modules or plugins Making templating platform-agnostic15
  • That’s how we’re thinking about WordPress……but how are we using it?16
  • 17
  • The pluginWe needed an easier way to register: Post types with default settings Taxonomies with custom entry boxes Meta boxes CapabilitiesWe were doing it all in the theme; we transitioned to aplugin with a UI.19
  • How to know it’ll workTwo choices:1. Manual entry of each post type, then manual entry ofone term for each taxonomy2. Automated behavior testing!20
  • Enter behaveSimple, 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 whenor then21…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!
  • [DEMO]22
  • Okay, so you can teach a computer to log in…23What about a real test?1. Log in2. Go to the Custom Post Type page3. Create three post types4. Deactivate all three5. Re-activate all threeTotal execution time: 33 seconds (with about half of that going to wp-login)
  • Benefits of testing241. You know your plugin works2. You can spot bugs on the fly3. Programming toward specific behaviors4. Its way faster than doing it all by hand5. Eventually, you write better code.6. You always know if the feature works or not
  • Still learning…25 Itd be nice to not have to log in _every_ time Writing the steps can be tricky (but its python, so not too tricky)
  • We all start somewhere27
  • But as we go, we learn28
  • Building, building, building…29
  • Embrace the WordPress communityThey’re the source for solving your problems and givingyou inspiration to solve theirs… Automattic’s Github WordPress.org Forums Themeshaper.com WordPress.org Plugin Directory Also, blogs!30
  • How is the CFPB “viewing source”? Hello Underscores! Forked; becoming our new base! WordPress goodness baked in. Miminimalistic; easily extendable. Solid framework and conventions31
  • 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
  • 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