Plone eCommerce: Surveying the State of the Art

2,165 views
2,063 views

Published on

GetPaid emerged as a concept 2 years ago (at Plone Conf 2006) and coding began 6 months later. Now there are several use cases for ecommerce in Plone that are leveraging GetPaid. The talk features these sites and provides concise howto information on implementing the features. It also overviews GetPaid and its Zope-3 based architecture.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,165
On SlideShare
0
From Embeds
0
Number of Embeds
136
Actions
Shares
0
Downloads
36
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Plone eCommerce: Surveying the State of the Art

  1. 1. Ecommerce in Plone: Surveying the State-of-the-Art Christopher Johnson ifPeople Cofounder www.ifpeople.net | cjj at ifpeople.net Plone Conference | October 8, 2008 Washington, DC
  2. 2. What is GetPaid? ● Zope3 and Plone-based framework for developing unique and highly customized ecommerce sites ● Very basic features available out of the box for processing payments on Plone site ● Most features and customizability benefit from developer/integrator working on site
  3. 3. What is GetPaid? ● 11k+ lines of code – Two major releases (0.3, 0.6) – Plone 3.0, 3.1 focus (currently also works on 2.5) ● Active community (40+ contributors) – http://www.ohloh.net/projects/GetPaid ● Mailing list: 130+ people – http://groups.google.com/group/getpaid-dev/ ● 9 Languages ● German, Italian, Dutch, French, Spanish, English, Portuguese, Brazilian Portuguese, Chinese
  4. 4. Zope 3 ● Basis of GetPaid architecture – We have no Archetypes! ● Component architecture – Nicely organized, independent packages ● Adapters + Interfaces + Views ● Marker interfaces – Used in GetPaid – Inspiration from Plone4Artist
  5. 5. Features ● Content Integration via Marker Interface – Buyable – Donation – Shippable – Premium content* *Not yet implemented
  6. 6. Features ● Shopping cart ● Checkout wizard ● Payment processor ● Order management
  7. 7. GetPaid Components
  8. 8. How to Get GetPaid ● Distribution: – getpaid.recipe.release ● tinyurl.com/gp-recipe – getpaid.buildout ● http://code.google.com/p/getpaid/wiki/DevGettingStarted ● Download: – Tarball at http://code.google.com/p/getpaid/downloads/list
  9. 9. Add-ons Satisfy Specific Use Cases ● One-page Checkout ● Making a Store ● Managing Inventory ● Discounts
  10. 10. Add button to rich text area ● – Add image – Add link to image for: ● /@@getpaid-cart-add?add_item=True Image: edkohler
  11. 11. ● One-page checkout – See tinyurl.com/tfl-gp ● Addon: getpaid.formgen – tinyurl.com/getpaidfg ● Extend with PFG+Salesforce – Tip: edit GetPaid adapter last
  12. 12. How to Make a Store ● GetPaidStore – tinyurl.com/getpaidstore – Includes product archetype, workflow, views – Used for orderliterature.com ● Thanks to TOT
  13. 13. Inventory Management ● Track inventory stock and quantity available ● Add warehouse location info – Shows on order ● Warehouse location used in shipping calculation (UPS)
  14. 14. Beyond Add-ons: GetPaid Flexibility Image: yogi
  15. 15. Make Your Own Buyable Content ● Example particular archetypes: – Products – Donations
  16. 16. Make Your Own Buyable Content ● How to do it in GetPaid: – Create custom content type – Make it buyable ● Admin interface (Through The Web) ● Programmatically (see tinyurl.com/getpaid-content-doc) – Programmatically: ● Mark content type with IbuyableMarker ● Register adapter to extract relevant data from archetype – Thanks to Michael Dunstan!
  17. 17. Add GetPaid Info On Your Template – from Products.PloneGetPaid.interfaces import PayableMarkerMap, IBuyableMarker – if IBuyableMarker.providedBy(PrettyCoffeePot): – iface = PayableMarkerMap.get(IBuyableMarker, None) # Or any of the other markers – iface(PrettyCoffeePot).price ● ==> Returns the price – See howto at: http://plone.org/products/getpaid/documentation/ho w-to/accessing-getpaid-attributes-on-objects
  18. 18. Pay-to-submit Content ● Examples: – Job posting – Applications – Directory listings – Ads
  19. 19. Pay-to-submit Content ● Subscriber to workflow state change ● Howto at: “how-to-tie- actions-to- payments” (plone.org) www.investorscircle.net
  20. 20. In the works (need more help) ● getpaid.salesforce ● getpaid.paypal (IPN) ● getpaid.credit ● Shipping: Flat rate shipping, FedEx ● Taxes: flat rate ● Recurring billing – blocked by contrib access!
  21. 21. Proposed (not yet sponsored) ● getpaid.workflow ● Downloadable purchases (mp3, etc) ● Memberships ● Premium content
  22. 22. For More on Who Uses GetPaid ● Sites Using GetPaid: ● tinyurl.com/pgpsites
  23. 23. Beyond GetPaid... ● Plone Commerce Background: – Research into what else is available – http://www.plonegetpaid.com/why/plone-commerce- background ● EasyShop in Plone ● Satchmo in Django
  24. 24. Thanks! ● Kapil, Perrito, Lucie and all contributors to GetPaid ● Sponsors of GetPaid: – One/Northwest, ifPeople, Contextual Corp, Trees for Life, Totsie.com, Train of Thought ● Find us at #getpaid and http://groups.google.com/group/getpaid-dev/ ● Dive in!! GetPaid Sprint following Plone Conference ● Find me: cjj at ifpeople.net and cjj on irc

×