I'm unsure about this really as I think a lot of the time people are as well just sticking their school email addresses etc. on a contact page, but probably there's that expectation of having a contact form on a website.

Questionnaires similar topic I suppose if were to use webforms module instead of core contact to create a contact page... as webforms could then be re-used to create more custom questionnaires/feedback forms.

Comments

jgraham’s picture

jgraham commented
Title: contact form / questionnaire » provide contact form
Assigned: Unassigned » penguininja

I think a generic contact form could be a good fit.

Questionnaires and webform as a solution for this though are too far down the path of custom implementation. Rather than attempting to force a solution for these scenarios I would rather leave this unaddressed as these will generally need a customised solution that a distribution will not likely address very well.

Adjusting ticket title as a contact form is worth considering as an additional feature set. I'm thinking user level contact forms and more importantly a sitewide contact form. Let's figure out if this is something that Julio can and/or should provide.

penguininja’s picture

penguininja commented

Actually, Julio comes with a static contact node, but the menu link to that page seems to be missing. Is there a strong benefit to including a contact form (that may need to get customized) over just a generic contact page that schools could put phone/email/address info on? I agree with jgraham that webform is more complex that we want to go with this, so I think this is just a matter of contact page vs. contact form. Currently I'm leaning towards a static contact page (with the menu link in place).

Thoughts?

lightsurge’s picture

lightsurge commented

@penguininja I did find that contact page... and I totally agree really, but frequently come across problems with users where mailto: links go to dead email clients. Like you I'd rather just have school contact details on, but perhaps both (i.e. +form) would be best?

And if there could be some UI for adding markup to the content of the contact form page, at least schools could embed a map etc. I know how this could be done in d.6.x but not sure about 7.

Understand the webform feature is over the horizon though, I can't really see how it would work in practice ;)

penguininja’s picture

penguininja commented

Thanks for the feedback. Honestly I haven't looked at the contact form much in D7, and my primary concern is ease of customizing the form. I'll check it out and see if it's viable to include as an option.

lightsurge’s picture

lightsurge commented

Easy way without a form_alter might be to have a block in the 'content' area (disadvantage: it goes below the form), sidebar (but is there enough width for most uses to look okay?), or maybe 'Featured' (but this goes above the sidebar) with either block settings to appear only in '/contact' path, or the same as a context.

The advantage of having such a block in the sidebar might be to fill it with something useful as per #1515116: blank sidebar