Contact Us
This will contain:
- contact form
- name *
- email*
- subject* (dropdown)
- message*
- button
- disclaimer
- user guide link
- FAQ link
- service desk link (https://jira.rocketweb.com/servicedesk/customer/portal/6)
Imported Confluence comments (16)
Jakub Kulig (Unlicensed) 2016-04-18
Please review Contact us page here: http://dev.rocketshoppingfeeds.com/contact-us. Feel free to suggest improvements e.g. I'm planning to improve form validation at a later stage, but if you find anything else please let me know.
Vince Malfeo (Unlicensed) 2016-04-18
Looks good
Corey Schmitz (Unlicensed) 2016-04-18
We could also provide resources like Wiki, FAQ, and Tutorials on the Contact Us page. A lot of times peoples questions can be answered by one of the guides or tutorials. This would help save time on support.
An example would be on the Support page.
Matt MacDougall 2016-04-18
Jakub Kulig (Unlicensed) Vince Malfeo (Unlicensed) Corey Schmitz (Unlicensed) do we need a Subject line? If it's not going to provide is value, we should drop it and give people one less thing to fill out.
Corey Schmitz (Unlicensed) 2016-04-18
Would be easier to keep track of emails with a subject line. I think that should stay.
Matt MacDougall 2016-04-18
Emails will have a subject line but by default it would be "Question from rocketshoppingfeeds.com". If there's one thing we've learned over the years is that people will give us crap data. I'm sure we'll see tons of subject lines with just "Question", "A Problem" or maybe WTF
![]()
If you guys think it will be helpful to see custom subject lines, that's fine with me. You'll be the ones getting these emails.
Another idea is to make the Subject a dropdown box with some premade subject lines to help us organize questions "Sales Question", "Technical Question", "Love Letter", "Hate Mail" ... could make it kinda fun
Vince Malfeo (Unlicensed) 2016-04-18
If we decide to stick with custom subject lines, the premade dropdown box is the best option in my opinion.
Corey Schmitz (Unlicensed) 2016-04-18
If it just says Question from rocketshoppingfeeds.com then I agree that is not very helpful.
I like the idea of having a few pre-made options to categorize the emails.
Jakub Kulig (Unlicensed) 2016-04-18
Not a problem. Dropdown it is so
I'll add it tomorrow.
I also like Matt's idea of making it a bit more informal. Not just the dropdown but other UI elements here and there, i.e. headings, buttons, alert messages etc.
Jakub Kulig (Unlicensed) 2016-04-19
I made some improvements to the Contact page as per the comments above. Please review and let me know further adjustments are required.
Vince Malfeo (Unlicensed) 2016-04-19
Looks good with the information to the left of the form fields that Corey recommended earlier.
"Before using the contact form make sure
theto checkout the following support pages."In my opinion, for the subject line premade topics, I like the "Quick Question", "I need Help!", "May I suggest something..." but I think we should change "What's up?" to "Other".
Aesthetically, looks great!
Jakub Kulig (Unlicensed) 2016-04-19
Thanks Vince Malfeo (Unlicensed), I'll make sure to make the suggested amendments. I wasn't sure about "What's Up?" either, might be too informal.
Corey Schmitz (Unlicensed) 2016-04-19
That looks much better! Adding Wiki, FAQ, and Tutorials will both educate the customers, and cut down on the support tickets.
Matt MacDougall 2016-04-19
Cool, I like it. 2 comments, can the subject lines be edited in the cms? If not, we should give these subject lines more thought.
I think the submit button should be something more like "Send to Mission Control". Send to Outer Space implies that someone is sending their message off to die
Jakub Kulig (Unlicensed) 2016-04-19
Thanks for the feedback, Matt MacDougall. To answer your question nearly all the content can be edited in the cms, which includes headings, lead text, paragraphs, form fields, buttons, content blocks, images etc. I tried not to hardcode any static content inside templates but rather use variables and pull data that Grav allows to define as frontmatter or markdown content in user/pages folder for easier manageability. See example of a page edit screen below:
Most of the content is currently defined as frontmatter as it's more flexible to use. To show the frontmatter expert mode needs to be enabled. Eventually I plan to create custom fields for normal mode, similarly as Ana did on RW.com, so that admins don't have to touch the frontmatter. Naturally, I will document the process of editing pages when I'm done with front-end work.
Nothing is set in stone here, admins will have easy access to about 95% percent of content that's currently on the site. For that reason I didn't want to focus on specific wording for now as I was hoping Corey Schmitz (Unlicensed) and Vince Malfeo (Unlicensed) will be able to polish up the content once development is completed.
Matt MacDougall 2016-04-19
Perfect, thanks Jakub Kulig (Unlicensed)
No comments to display
No comments to display