App Root Page: when I click the CTA buttons I am directed to a new organization request form

[kasugaijin]

The CTA buttons on the app root page should take the user to a form for organizations to fill out so they can request access to the app (see how we implemented the Feedback form available in the footer and on dashboards). When the user submits this form, it should send an email to the dev email account (TDB) with a title New Organization Request and provide the details from the form, below.

This email will inform the devs that they need to vet the organization, discuss their preferred slug, and then run the service to create a new organization.

The form should collect this information:

• Organization Name
• Your name (the person filling out the form) (we don't need to separate first and last, it's just for conversational purposes)
• Organization Phone Number
• Organization email
• Country
• City/Town
• Province State

Please also change the CTA button text to Request an account Please also update the Org footer link to point to this new form

App root page CTA buttons x 3

[DreamVenerable]

I'm interested ✋🏻

[kasugaijin]

@DreamVenerable all yours

[kasugaijin]

@DreamVenerable how's this going? Let me know if you have questions.

[DreamVenerable]

@kasugaijin Honestly I've been a bit busy, hence the lack of progress.

If I find myself stuck or unable to complete it I'll inform you.

[DreamVenerable]

@kasugaijin Should I create a new model or handle it from the controller?

If we are going to to end up using the data then I think we should have a model for it, if not, then we don't need to persist the data

[kasugaijin]

@DreamVenerable please add a new controller - see app/controllers/contacts_controller.rb for an example. We don't need a model as the data will be sent to email.

I think we can call it something like app/controllers/organization_account_requests_controller.rb unless you can think of a better name. Please also add the route organization_account_requests, and view for this.

I also note that this will be the third contact form we are adding to the app/controller scope. I think there is a good argument to add a module like contact_forms in the controllers and views so we can keep these controllers and views together. We can move all three controllers/views to this module. Let me know if you want to tackle that also...or we can put in a new issue.

e.g.

scope module: 'contact_forms' do
  resources X
  resources y
  resources Z
end

[DreamVenerable]

I made a new controller called OrganizationRequestsController, but I like your naming better as it's more clear.

Regarding the refactoring, I'll see to it after finishing this issue.

[kasugaijin]

@DreamVenerable sounds good! FYI @Aaryanpal as you are working on one of the contacts controllers

[DreamVenerable]

@kasugaijin Hey, sorry I've been busy lately. Can you keep it open so that if someone wants to work on it can get assigned?

[kasugaijin]

@DreamVenerable For sure. Issue is ready for someone to be assigned.

[Meri-MG]

hi, @kasugaijin maybe i could start working on this one once the other pr is merged?

[kasugaijin]

@Meri-MG for sure!