Skip to content
Sign inJoin waitlist

Forms — Semono HTML

The Semono HTML template has three forms, and they send to the form service or webhook of your choice: a Contact inquiry, a service consultation and a career application.

The inquiry is on the Contact page, a consultation form on every service page and an application form on every career page. Each form checks the required fields, shows a spinner while sending, says “Thank you” and clears the fields, keeps what the visitor typed when something fails (“Something went wrong”), and drops spam with a hidden honeypot field.

Out of the box they run in demo mode: nothing is sent, and the fields are logged in the browser console. Pick a destination before you publish.

A static site has no server of its own, so submissions go to a form service or a webhook. All of these have a free tier:

Service What it does formEndpoint
Formspree Emails you each submission https://formspree.io/f/<form id>
Web3Forms Emails you each submission, no account needed https://api.web3forms.com/submit, and your key in formAccessKey
Getform, Basin Inbox, email, integrations The form’s endpoint URL
Zapier, Make, n8n, Pipedream Send submissions anywhere: Google Sheets, Slack, a CRM, your applicant tracker The webhook (“catch hook”) URL
  1. Create a form at the service and copy its endpoint.

  2. Open assets/js/config.js and paste it:

    window.siteConfig = {
    formEndpoint: "https://formspree.io/f/abcdwxyz",
    formAccessKey: "", // Web3Forms only
    };
  3. Serve the folder (npx serve .), submit each form (one inquiry, one consultation request from a service page, one application from a career page) and check that the submissions arrived.

  4. Upload config.js with the site.

Every page loads the same config.js, so one endpoint serves all three forms. The sample forms in style-guide.html stay in demo mode whatever you set there (they carry data-form-demo), so they never send anything.

Each field by its name, as multipart/form-data.

The inquiry on the Contact page:

Field Name Required
Full Name name yes
Business Email email yes
Phone Number phone
Company Name company
Service Required: Business Strategy, Operational Consulting, Leadership Advisory, Corporate Transformation, Financial Advisory, Brand & Market Consulting, Process Optimization or Organizational Growth service yes
Project Budget: Under $5,000, $5,000 — $10,000, $10,000 — $25,000 or $25,000+ budget yes
Project Details details

The consultation form on every service page (button “Book a free consultation”): name (Full Name, required), email (Business Email, required), phone (Phone Number), company (Company Name), service (Service Required: a text field filled with the page’s own service, so a visitor on “Business Strategy” sends “Business Strategy”) and details (Project Details).

The application form on every career page (button “Submit application”):

Field Name Required
Name name yes
Email email yes
Phone phone
Job Position (filled with the page’s own position) position
LinkedIn URL linkedin
Cover letter letter

Each form also sends form and subject, so you can tell them apart in your inbox or tool:

Form form subject
Inquiry contact New contact inquiry
Consultation consultation New consultation request
Application application New job application

With formAccessKey set, the forms also send it as access_key. The honeypot field is left out. The request asks for a JSON answer (Accept: application/json), so the service answers the page instead of showing its own thank-you page.

The fields are ordinary <input>, <select> and <textarea> elements inside the <form data-form> of contact.html, of each page in service/ and of each page in career/, each in a <label> with its text. Change a label or a placeholder in place; the choices of Service Required and Project Budget are the <option> elements of the two selects in contact.html (the first, empty one is the placeholder). The forms have two columns from tablets up (one on phones); a field that takes both carries md:col-span-2 on its <label> (Project Details; on the service pages Service Required too; on the career pages LinkedIn URL and Cover letter).

  • To make a field required, add required to it, and the red asterisk after its label’s text: <span aria-hidden="true" class="text-red">*</span>. The browser checks it before sending.
  • To add a field, copy a <label>…</label> and give its input a new name. The service receives whatever the form contains, so there are no settings to update. Don’t name a field fax: it is the honeypot’s.
  • To remove a field, delete its <label>…</label>.

The consultation and application forms are copied into every service and career page: change each copy (find and replace in files helps). The Contact form’s service choices are typed in contact.html, not read from your services: they include two that are not services of the demo (“Process Optimization”, “Organizational Growth”), so make the list match your own.

A field arrives under its name, so keep the names you already map somewhere. The button’s texts are written in the button: the label twice (the second copy is read while the form is sending), “Thank you” and “Something went wrong”. “Thank you” and “Something went wrong” are also in the form’s data-success and data-error, which screen readers announce: change both. The title of each submission is the value of the hidden subject field.

To send visitors to a page of your own after a successful send, add data-redirect="thank-you.html" to the <form> (../thank-you.html in the pages of service/ and career/).

  • Submit each of the three forms on the live site with a real address, and reply to the test.
  • The service must answer with a success status (2xx). If it doesn’t, the visitor sees “Something went wrong” and keeps what they typed. Try it once by pasting a wrong endpoint into config.js on your local copy.
  • The browser console tells you what happened: in demo mode it logs [forms] demo mode — set formEndpoint in assets/js/config.js to send submissions with the fields; after a failure, [forms] could not send the form with the reason.

The honeypot stops the usual bots: every form carries a hidden field named fax that a person never sees; a bot that fills it is shown “Thank you” and nothing is sent. The services above filter spam on their side as well. The endpoint is visible in the page source, which is how these services are designed to work.

Submissions go only where you point them. Most countries expect you to say what happens to the data people send you, and the application form collects a name, an e-mail, a phone number, a LinkedIn address and a cover letter. Semono has no consent checkbox. The footer links a Privacy Policy and Terms of Service (legal/) whose text is a sample to replace with your own (Editing the site).