-
Notifications
You must be signed in to change notification settings - Fork 153
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
CRM form integration #15
Comments
Does the CRM expose a REST API for us to push data to? |
@gvn - looking into this, will update shortly. |
We will use and reuse a short form (email input only) and a longer form (email + a few bits of info) like name, country/city, issue areas of interest. It'd be good have a reusable component for the short version. Maybe the long version too. It definitely would be good to set one of these up early so we can find hiccups before we get closer to launch. |
Agreed. Hoping I can get endpoint specs soon. |
cc @ScottDowne |
@gvn docs for basket: http://basket.readthedocs.io/ |
@gvn what's this blocked by? |
It may not be if the docs linked above are sufficient. I'll unblock for now... |
Temporarily blocked by hatchet configuration |
Nevermind, going to be posting directly to Basket since Sawmill would need another server set up (given that this project is going to be staticly served) |
CRM integration itself is done, just a matter of where it's being used. Currently works in the (not yet completely designed?) join us component. |
# This is the 1st commit message: fixed rebase conflicts # This is the commit message #2: fixed rebase conflicts # This is the commit message #3: fixed rebase conflicts # This is the commit message #4: updated elements on the page based on the latest comps # This is the commit message #5: added the last 2 sections in # This is the commit message #6: removed redundant code # This is the commit message #7: fixed rebase conflicts # This is the commit message #8: fixed rebase conflicts # This is the commit message #9: to match the updated comps # This is the commit message #10: fixed broken links # This is the commit message #11: named URL patterns # This is the commit message #12: custom template tag 'active_nav' # This is the commit message #13: applied custom template tag # This is the commit message #14: fixed linting error # This is the commit message #15: fixed linting error # This is the commit message #16: Related to #951 - fellowship type template & science fellowships # This is the commit message #17: featured fellow
For launch, our email sign-up form will ideally feed directly to our CRM. Other integrations (#8) can be added post-launch.
Let's gather requirements and insights from our advocacy peers. @gvn @arlissc
The text was updated successfully, but these errors were encountered: