My favorites | Sign in
Project Logo
                
Search
for
Updated Jun 27, 2007 by catchatigerbythetail
Labels: Phase-Design, AdminUI
AddDonationForm  
Donation forms are a simple payable content object that can be added anywhere in the site.

Site Manager can go anywhere in the site and select a piece of content. Using the actions menu, choose "Make this a donation". Any piece of content can be a donation. Flagging an object as a donation object will add on a schema to allow users to enter the following information:

  • Donation title
  • A rich text area for describing the donation.
  • Product code
  • Price (free text)
  • A submit and clear button.
  • Made payable by (automatically generated)

Customizing Buttons / Labels:

  • Provide an option for changing the buttons: "sign up for an event," "add to cart," "select this child," etc...
Jon Stahl: Site admins will want to have a rich-text field so they can add arbitrary marketing content to the page.
Jon Stahl: Site admins will also want the ability to add arbitrary information fields (e.g. checkboxes, radio buttons, text fields). For example, a checkbox "Subscribe me to your email newsletter." I suggest figuring out how to take advantage of PloneFormGen to provide this kind of flexibility.

Comment by jonstahl, Oct 16, 2007

I think something important is missing here.

A typical NGO donation screen should look more or less like:

https://secure.ga3.org/02/supportus

Key features:

-- multiple donation levels, plus an open "other" field into which they buyer can fill in any amount

-- can have text descriptions of each pricing level

-- site administrator can edit extra fields (e.g. email signup, etc.)

The current way that GetPaid? implements donations seems to make this kind of experience nearly impossible.

Comment by kapilt, Oct 28, 2007

suggestions or patches regarding ploneformgen integration are welcome. i'm keen on the idea, but haven't used it, and its not to me what makes sense.

as for producing i think the solution is to ship a donation content type. the mechanism we're using now, doesn't make sense to me if we're replacing the default view of any piece of content, which is whats needed to make this donation flow more natural. its much better as a specific content type, at which point implementing the functionality suggested becomes straightforward.


Sign in to add a comment
Hosted by Google Code