Skip to content

Contact System

@iDoMeteor edited this page Mar 3, 2016 · 4 revisions

Flexible Dual Mode Contact System

The contact system in #OnePageWonder is intended to be as simple as possible from a user's point of view, thus encouraging as many contacts as possible!

Inline Mode

The most obvious method it uses is simply by collecting email addresses and Twitter handles using a single field of input directly within the site content. How much easier could it be!

Modal Mode

For those users who have the burning desire to send you a message, there is a handy and hopefully quite obvious contact icon right at the end of the navigation section.

Using this handy button will pop open a modal window with a three simple fields for the user to fill in. This allows for an email address or Twitter handle, a subject or phone number and a message.

Consolidations

Say a user drops off their email or Twitter handle using the inline form. A few minutes or days later, they decide that they want to leave you an actual message.

No problem! The contact system will not allow them to submit another inline request, but it will allow them to send a message. Better yet, it will consolidate the modal request with the inline request, leaving only one message for the administrator to deal with!

Limitations (ie; Anti-Spam Features)

The contact system has several logical limitations, and a couple interesting allowances.

  • Intranet friendly email addresses are allowed
  • Twitter handles must be 15 alphanumeric characters or less
  • There may only be one unread contact request from any particular email address or Twitter handle (with consideration to the aforementioned consolidations, of course)
  • Multiple requests are allowed (by default anyway) for a single IP address, if they are from unique email/Twitter accounts
  • The current default limit of unread requests per IP address is 10, but can be changed in Meteor settings file

This system allows from some flexibility, say if a number of people in a cafe, classroom, meeting or conference all behind the same router or firewall wish to lodge a contact request.

With the ability to change the max requests per IP on the fly, you can have a sane limit or 1-10 for regular usage, but crank it up to 2000 if you're at a big conference.

Aren't I considerate? :)

Viewing Contact Requests

While in the administration modal, click on Logs and then Contact Requests. There is a badge on the right hand side of the button with the number of unread requests.

When you click on the button, you will see a table of requests. Inline requests are simply one table row, while modal requests are two.

Inline requests have a label corresponding to their CSS ID (nicely translated to English-ish for you), so that you know from which part of your site they entered the request.

Modal requests have a user entered label (prompt is for a subject or phone number) and a message.

Clicking any part of a request will mark that request as read and remove it from your log view. It will remain in the database, and eventually you will be able to view those as well.

Configuration

For now, check out the contact section of the configuration section.

Clone this wiki locally