How to use Modules

Most website builders make you bolt on a separate app for every bit of functionality: one tool for forms, another for scheduling, a plugin for payments. Frontpage Modules are built in. You describe the functionality you want and the agent wires up the real, working version: the platform handles the behavior, you own how it looks. Here's what's available and how to use each one.

What a module is

A module is a piece of genuine, full-stack functionality the platform runs for you, surfaced on your page through simple markup the agent writes. The split is clean: the platform handles the behavior (storing submissions, emailing you, taking payment, tracking conversions) and you own the presentation, so a form or a booking widget looks like part of your site, not a third-party embed.

Crucially, none of it is fake. A form really reaches your inbox; a payment button really charges a card. You'll never get a dead placeholder or an "integration coming soon" stub.

The modules you can add

Each is added just by asking for the thing it does:

• Forms — contact, quote, and lead forms. Submissions are stored, spam-filtered, emailed to you, and counted as conversions. Ask for "a contact form" or "a request-a-quote form with name, email, and project details."
• Signups — email capture for a newsletter, waitlist, or launch list. Entries land in a list you own and can export. Ask for "an email signup for my newsletter."
• Booking — appointment requests you confirm in one click, after which the visitor gets a calendar invite. Ask for "a booking form so people can request a consultation."
• Call bar — a sticky tap-to-call (and text) bar on mobile, ideal for local businesses. Ask for "a tap-to-call bar with my phone number."
• Payments — real payment buttons running through your own Stripe, for deposits, one-off charges, or tips. Ask for "a $50 deposit button."
• Store — a product catalog with a cart and Stripe checkout. Ask for "a shop with these three products."
• Pickup orders — a menu and checkout for takeout, powered by your Square account. Ask for "let people order pickup."
• Articles — a real home for guides, news, and how-tos you can edit on the page. Ask for "start a blog."
• Instagram — your latest posts on the site, kept fresh. Ask for "show my Instagram feed."
• Google reviews — real reviews from your Google listing, kept fresh, plus a write-a-review button and an optional "how likely are you to recommend us" ask. Ask for "show my Google reviews." If you already have a Place ID or Maps link, you can also connect and curate from the terminal — see Google Reviews for your website (From the terminal).

Adding a module: just ask

You never edit markup or paste a snippet. Describe what you want where you want it and the agent builds it:

• "Add a contact form to the bottom of the home page."
• "Put an email signup in the footer with a 'Join the list' button."
• "Add a booking form to the services page for a free consultation."
• "Add a tap-to-call bar for mobile using (555) 123-4567."
• "Show my Google reviews on the homepage, and add a Leave a review button."

Because you own the presentation, you can keep refining the look by chatting: "make the form two columns," "move the signup above the footer," "change the button to say Get early access."

Zero-setup vs. connect-once modules

Modules come in two flavors. The difference is whether Frontpage needs something only you can confirm: a Stripe account, a Square account, an Instagram login, or the right Google listing.

The first group activates the moment it's added, nothing to configure. When you ask for a connect-once module, the agent builds the whole thing right away, then a prompt appears in your status bar to finish the connection. Those elements stay hidden from visitors until that's done, then go live automatically. For Google reviews you search for your business (or paste a Maps link) and confirm "This is my business." You never paste a Place ID or open Google Cloud.

Where everything lands

The point of a module is that the results reach you. Form and booking submissions are emailed to you and logged as conversions in your analytics. Signups build an exportable list you own. Payments settle into your Stripe account. Recommend-us scores from the Google reviews ask land in the same inbox and are emailed to you. You're never logging into a separate dashboard to find your leads.

Settings from the terminal

If you already use the Frontpage CLI, you can change the same settings without JSON or opening the editor: call-bar phone, a form's notify email, booking hours, and mailing-list confirmations. To start Stripe or Square from the terminal, frontpage modules payments|shop|ordering connect opens Frontpage (you must be logged in there), then Stripe or Square — finish there, then run status. See Modules for the commands.

---

A quick checklist

• Decide what each page needs to do: collect a lead, book a call, take a payment.
• Ask for that functionality in plain English, where you want it.
• Refine the look by chatting, since you own the presentation.
• For payments, a store, Instagram, or Google reviews, finish the one-time connect from your status bar.
• Point your notifications wherever you want leads to land.

New to building here? Start with Getting started with Frontpage, and learn the prompting habits in How to edit your site just by talking.

Frequently asked questions