Continuous Delivery with Content Management and UGC

  • 715 views
Uploaded on

Like salmon swimming upstream, user-generated content (UGC) and changes from content management systems (CMS) need to flow in the opposite direction to most software product changes. …

Like salmon swimming upstream, user-generated content (UGC) and changes from content management systems (CMS) need to flow in the opposite direction to most software product changes.
What strategies exist for reconciling the bidirectional flow (applications & features vs. content)? How can we bring upstream-moving content into our deployment pipeline, in which everything flows down towards Production?

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
715
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
3
Comments
2
Likes
3

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Continuous Delivery with Content Management Systems (CMS) and User-Generated Content (UGC) Matthew Skelton 23rd October 2013 #londoncd meetup group @matthewpskelton
  • 2. CMS and UGC • Content Management System – WordPress, Drupal, CQ5, Magnolia, Sitecore, SharePoint (?!) • User-Generated Content – Reviews, photos, ratings
  • 3. What‟s the Problem? Much contemporary CMS-managed content and UGC is not simply static but changes application functionality Photo: Ingy the Wingy http://www.flickr.com/photos/ingythewingy/5740856803/
  • 4. Made in Production ® • Non-technical content authors – New pages, widgets, workflow • End users – Graph connections, tagging
  • 5. New Functionality • Ideal: flow down new functionality and behaviour from Dev • Reality: CMS and UGC introduce new behaviour and functionality directly in Production
  • 6. What do Humble & Farley say? “In most cases, don‟t use dumps of the production dataset for testing purposes. Create custom datasets by carefully selecting a smaller subset of production data”p.344 ... but not much more than this
  • 7. Example Strategies 1. Remove the Problem – Avoid CMS – Decouple UGC 2. Embrace the Problem – Testing – More testing
  • 8. Remove the Problem • Ditch the CMS – Use plain HTML fragments + tooling – Flow down the pipeline – Package Management for dependency graph • Decouple UGC – JavaScript client-side integration
  • 9. Embrace the Problem • Front-end tests in Production – Use Staging? • Identify new pages/features, extract, bring back – Track content with UUIDs • Pre-live environment with data regularly synched from Prod
  • 10. Content Flow: „Upstream‟ Photo: Karen Miller, http://www.flickr.com/photos/tmtht/4029281127/
  • 11. Other Approaches? • Performance Testing? – Data dumps • „Content Platform‟? – ETL approaches • (No correct answers)
  • 12. Matthew Skelton @matthewpskelton Discussion Time! London Continuous Delivery meetup group: @londoncd http://londoncd.org.uk/