We’re looking at using CiviCRM as a backend for managing our membership database in the interim until a better system can be found or developed.
I am having difficulty reasoning about the best way to go about linking a custom membership application form to the CiviCRM API such that we can do the following (in order of priority):
- Have a standalone form on a separate server (isolation, security, flexibility, etc)
- Handle the requirements of state party registrations (different data needs to be entered)
- Allowing members to update their details without Secretarial intervention and without needing an account (using UUID, date of birth and last name as credentials for example)
If someone wants to help me try to bash out a logical spec on this, it would be much appreciated.