Skip to content

Feature: Personalized webpage including rich contact form

No due date 100% complete

User is given a personalized contact page with same origin as EasyForm and path = github userID. It is a single page app, or website, containing at least custom text, avatar, socials, status and even blog posts.

Comments may be enabled in this personalized page too. In that case the above-mentioned storage contains all past contents to be retrieved and di…

User is given a personalized contact page with same origin as EasyForm and path = github userID. It is a single page app, or website, containing at least custom text, avatar, socials, status and even blog posts.

Comments may be enabled in this personalized page too. In that case the above-mentioned storage contains all past contents to be retrieved and displayed dynamically.

One good way to deal with this is to use 404 pages on the easyform github page website.

Visitors can opt for "I prefer to be contacted by Phone | Email | Whatsapp | Telegram" or "I will check on this page later".

Visitors to this page are shown message delivery status on form submit. They can also come back to see if there is any reply from the owner user. This is achieved using localStorage (shared by all ready form pages thanks to their same origin) and a random but unique visitorID=UUID. As long as the vistor's localStorage survives they can see their chat history with the owner. Because a visitor can simultaneously visit personalized pages of multiple github users, their localStorage stores their chat history as values to github user ID keys.

Use cases:

  • personal website
  • "Contact (vehicle) owner" sticker with QR code of the URL.
Loading