This week was a bit slow starting — I blame Reunions — but once I got going, it was really productive. I spent most of the first day thinking about the architecture for a new project that I will be working on together with Rob Gleeson, a remote dev (Irish, but living in Amsterdam). Should be interesting to build something with someone thousands of miles away. The gist of the project is this: the Sales team wants to be able to separate leads from people who are interested in a course and those who have actually applied, which will also include migrating the whole application process from Wufoo to our own website.
There are two distinct chunks to this project. The first, and easier of the two, is to automatically send emails to people who request more information about a course, thereby freeing up the sales team’s time to pursue more important leads. As far as I can tell, this will require simply creating a new “request info” mailer and updated the Lead Observer to generate this mailer anytime a lead is created from this particular source.
The more complicated piece of this project will be to create a course application flow on Core rather than just linking to Wufoo. Some initial thoughts: (1) beginning an application will generate a new lead, so we need to figure out whether to create duplicate leads if a user already exists as a lead or whether to override the existing; (2) perhaps there should be a single-page summary for completed forms for GA producers to access; (3) we’ll need to create an Application model (or maybe something with a less confusing name) with fields for user, course, completed, instance (maybe), url (maybe), as well as a serialized field for all other data from the forms; (4) how do we deal with the views, which will be different for every application?; (5) do we save the input from each page of the form, and if so, how do change the “completed” attribute to true? I’m sure we’ll start to address these issues when we get started on this project.