Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove donate page and replace with raisely widget #97

Closed
lulen11 opened this issue Jan 20, 2020 · 8 comments
Closed

Remove donate page and replace with raisely widget #97

lulen11 opened this issue Jan 20, 2020 · 8 comments

Comments

@lulen11
Copy link
Contributor

lulen11 commented Jan 20, 2020

hey @mischacolley could you please provide more context on this one?

@bronz3beard thought you might like to handle this one because it will be similar to what you did on the intercom / contact work.

Basically, we're not going to house /donate anymore. Instead we will use the Raisley widget in a similar manner to intercom widget.

@bronz3beard
Copy link
Contributor

hey Team
@lulen11 @camposcristianeze

I just had a quick chat with Lara and wanted to add a note,
I am putting this on ice just for now, but I will need further context before I get started, when ready.
Is the current plan what we need/want to use or if we are moving to another plan? popup/message/form/crm integration/popup with form?
If I need a key or user/PW for accessing raisley to see setup and custom docs (if they are available.)

Just some basic info to help things move quicker 👍

@camposcristian
Copy link
Contributor

camposcristian commented Jan 21, 2020 via email

@camposcristian
Copy link
Contributor

camposcristian commented Jan 21, 2020

For when we pick this up as I notice in the WFs we thought about removing this page and just implementing a popup as we had in v2.aimementoring.com , which I think it will actually make things easier -->

https://developers.raisely.com/docs/introduction-to-components

@kbardi
Copy link
Contributor

kbardi commented Jan 27, 2020

Hey team, I do not have access to the Stripe account, but I think it is better to configure Stripe in a popup...and I've already done that in other project a couple of years before, so I can check there and reuse part of the code...
It seems to be more stable, and if it is cheaper, even better, haha.
https://github.com/stripe/react-stripe-elements#demo

Let me know if you agree on using Stripe @camposcristianeze and @mischacolley .
I read a lot about Raisely and they mention they are still on Beta version, and also it doesn't seem to be fully done for using components...

@bronz3beard
Copy link
Contributor

This is currently being redirected from /donate to raisley

@camposcristian
Copy link
Contributor

Let me know if you agree on using Stripe @camposcristianeze and @mischacolley .
I read a lot about Raisely and they mention they are still on Beta version, and also it doesn't seem to be fully done for using components...

I really don't like how Raisely and other tools are just another CRM layer on top of a really good API like Stripe... Not 100% sold on any of both paths, but as an NFP I think we could save costs going straight to the low-level source (e.g AWS as PaaS or Stripe as a payment gateway) and add customizations where needed.

On the other hand... I did see Elsa creating campaigns in Raisely and this means anyone can do it.. So I before jumping to Stripe @bronz3beard @kbardi let's make sure we have a PoC of this raisely component in either a pop-up or an inline form at least.

@kbardi
Copy link
Contributor

kbardi commented Mar 9, 2020

Hey @camposcristianeze, as far as I see, the raisely component is only for internal use, and we cannot use that component in our code. @mischacolley also mentioned the same when we talked before my holidays.

What we talked to do is a modal which opens an iframe with Raisely page.
I like Stripe for payments, and it is quite easy (they have good documentation) to configure stripe in react, but we need to create campaigns in a different place (maybe contentful) and load data from there...
It is true we have an extra cost for using Raisely, but not sure if it is the best moment to replace it by a custom setup...we should make a plan maybe, first with the PoC, and defining which tools are we going to use...

@mischacolley
Copy link
Contributor

Lots of debate here so closing in favour of #276

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants