Mini Site Builder — Complete Reference

A no-code visual editor for event websites. This chapter documents every panel, every block and every individual setting in the builder — what each control does, the range it accepts, its default, and which plan it needs.

1. How the editor is laid out

The builder has three columns. Almost everything in this chapter lives in the right-hand panel.

Pages

A site is Home plus optional inner pages (About, Schedule, Contact and so on). Use the page selector above the canvas to add or switch pages. Every page has its own blocks; site-wide settings and the header/footer are shared. Inner pages count against your plan — see §11 Plan limits.

2. Controls that appear on almost every block

Rather than repeating these for all 19 blocks, they are documented once here. Section 4 then lists only what is unique to each block.

Settings are organised into collapsible groups, always in the same order so the panel feels identical from block to block:

Groups remember whether you left them open or closed, per block type.

Spacing, alignment and background

Typography (per block)

Every content block carries its own Typography group. Sizes are pixel sliders and each text role has its own colour, so you can restyle one section without touching the rest of the site.

Colour controls in the same group target individual roles — Section Title, Subtitle, Content Text, Card Background, Time, Venue, Role / Title, Tier Name, Divider, Link Text and so on, depending on the block.

3. Adding images and video

Images

Anywhere an image can be set, you get the same field with three ways to supply one:

• Paste a URL — any public image link, including a Google Drive image link.
• Upload — pick a file from your device (up to 8 MB).
• From Drive — opens the Google Drive picker. This button only appears once your Google account is connected, so it is never shown where it could not work.

Image layout controls

Video

Video can be used as a Cover background or inside About, Footer and the Video block.

4. Editing the mobile version separately

A Mini Site is one site, not two — but several settings hold a separate mobile value so a hero that looks right on a laptop does not arrive oversized on a phone. That is what the Desktop | Mobile switch pinned to the top of the settings panel is for.

How the switch behaves

• It chooses which set of values the controls below write to — it does not change the block's content.
• The panel switch and the canvas preview are one control. Flipping the panel to Mobile flips the preview too, and opening a block while the phone preview is up starts you on Mobile — so you are never editing mobile values while looking at the desktop render.
• It is per block and lives only in memory. It is not saved with the site and does not affect what visitors see.
• Groups it governs carry a small Desktop / Mobile chip on their heading, so you can always tell which values you are editing.

Which groups are per-device

"Auto" — the inheritance rule

Every font-size slider has an Auto button beside it.

• On Desktop, Auto means "use the built-in default".
• On Mobile, Auto means "use whatever the desktop value is". The slider reads Auto (32px) so you can see the inherited number, and it starts at that position so dragging never makes the text jump.
• Set a mobile value only where the desktop one genuinely does not work. Anything left on Auto keeps following desktop, so later changes stay in sync automatically.

Things that adapt on their own

Some behaviour is handled for you and needs no mobile setting:

• Hero Horizontal Padding is ignored on phones — the hero stays full-bleed.
• Carousel padding collapses to a slim edge fade on phones.
• The Speakers list keeps a 20 px gutter on phones regardless of its padding slider.
• Background video does not autoplay on phones unless you switch Play on phones too on.

5. Every block, setting by setting

Every block also carries the universal Section Style (padding, alignment, background) and Typography groups from §2, so only what is distinctive is listed below.

6. Site Settings

Prebuilt Themes

One click applies a coordinated colour and font set across the whole site: Cyber, Midnight, Forest, Gold Class, Festival, Ocean, Paper, Clean White, Tech, Elegant, Festive, Editorial, Minimal. Start from a theme, then adjust individual values below.

Colors

Typography

• Paired Fonts — curated heading/body combinations that are known to work together.
• Custom Fonts — set Title Font and Content Font independently from the Google Fonts library.
• Content Colour — default body text colour for the site.
• Title Size and Content Size — site-wide defaults. Any block's own Typography group overrides these for that block.

Registration

Registrations Open — a master switch. Turning it off closes sign-ups everywhere on the site at once and shows a closed message in place of the form.

Site Info

Site URL Slug — the unique name in your public address (for example my-event-2026). Keep it short and readable; it appears in every link you share.

Loading screen

7. Google Analytics (GA4)

Pro Connect your own GA4 property to see real visitor numbers for your event page. The data goes only to your Google Analytics account — no other GalSol user can see it.

Getting your Measurement ID

1. Go to analytics.google.com and sign in. Google Analytics is free.
2. Open Admin (the gear icon, bottom-left) and choose Create Property. Name it after your event.
3. When asked for a platform, choose Web, and enter your published Mini Site URL as the website URL.
4. Google then shows a Measurement ID that starts with G-. Copy it.
5. In the editor, click the Analytics button, paste the ID and press Verify & Save.

8. Custom domain

Pro Serve the site on your own address instead of a GalSol URL.

1. Open the Deploy panel and find Custom Domain.
2. Enter the domain you own.
3. GalSol shows a CNAME record. Add it with your domain provider exactly as shown — the panel has copy buttons for each part.
4. Click Check Status. DNS changes can take anywhere from a few minutes to a few hours to propagate, so check again later if it is not live yet.
5. Remove detaches the domain; the site stays reachable on its GalSol URL.

9. Deploying and updating

1. Click Deploy. The panel shows the exact public URL your site will be live at, with a copy button.
2. Confirm the Registrations Open state — you can flip it here without leaving the panel.
3. Press Deploy to publish. The button reads Publishing while it works.
4. To change anything later, edit the canvas and deploy again. Updates replace the live page immediately.

10. Collaboration

Sites can be shared with teammates so more than one person can edit. Live presence shows who else is in the editor with you. The number of people you can invite depends on your plan.

11. Plan limits

Prime Site — Complete Reference

Describe the website you want and Prime Site writes the actual code, publishes it and hosts it on your own domain. Unlike Mini Site — which is a block editor — Prime Site produces a real code project you can keep editing by conversation. Pro Not available on Free.

1. Projects

Each site is a project. The dashboard lists Recent projects, All projects and Owned by me. Create New starts one from a description.

2. Building by conversation

1. Describe what you want — "Generate a full event site", "Add a countdown timer".
2. Gal AI produces a Build plan before it writes anything, so you can see the intended change first.
3. The build runs and streams its progress.
4. Review the result. Changes arrive as Changes pending — Accept to keep them or Discard to roll back.

The model is selectable — Gemini 3.5 Flash or Claude Haiku 4.5.

3. The editor

4. Publishing

Publish makes the current build public — "Everyone can see it now." Copy link gives you the address. Publishing again replaces the live version.

5. Plan limits

GS Forms — Complete Reference

A form builder that also issues entry passes, sends automated email and feeds your Analytics dashboard. This chapter covers every field type, every setting tab and the whole registration-to-gate pipeline.

1. How the builder is laid out

Forms start either from Start blank or from a template. Every form is a Draft until you publish it; the Forms list shows Drafts, Published, Closed and Shared separately.

2. Field types

Sixteen types, grouped by what they collect.

Settings every field has

3. Design tab

With no field selected, the Design tab styles the whole form.

4. Settings tab

Submission Rules

After Submission

Embed on Your Website

Gives you the snippet to drop the form into any page. Inside GalSol you do not need this — the Mini Site Registration Form block connects natively by picking the form from a list.

5. Email tab — automated mail

Turn Send Automated Mails on to email respondents the moment they submit. Mail is sent from your own connected Google account, so it arrives from you, not from GalSol.

Mail groups and conditions

Rather than one fixed message, you build mail groups — each a template plus a rule for who receives it.

• Always send — everyone who submits gets this one. Use it for the standard confirmation.
• Conditional — send only when an answer matches. Conditions test a field against a value with equals or contains, so a workshop choice, a ticket type or a city can each trigger different wording.

6. Pass tab — entry passes and attendance

An entry pass is a designed ticket with a QR code, generated per respondent and emailed to them.

Mapping the pass to your fields

1. Enable Entry Pass & Attendance.
2. Set Attendee Name field and Attendee Email field — which of your questions supplies the name printed on the pass and the address it is sent to. Without these the pass has nobody to belong to.
3. Fill in the event details shown on the ticket: Event Name, Venue, Date, Number of Days.
4. Add branding — Logo and Card Image.
5. Set QR Size (default 140 px). Bigger scans faster from a phone screen in poor light.

Pass layout blocks

The pass page is built from blocks: Header, Entry Pass (the ticket itself), Response Summary (what they submitted), Text, Button and Footer.

Scanning at the gate

Staff open Pass Scanner on their phone, enter the staff code and scan. Check-ins appear live in Analytics.

7. Publishing, sharing and responses

1. Publish the form. Until then it is a Draft and the link will not open for respondents.
2. Share the link, or the generated Form QR Code — useful on posters and slides.
3. Responses flow into your connected Google Sheet and into the GalSol database at the same time.
4. Track everything in Analytics: response counts, individual submissions and pass check-ins.
5. Close the form when you are done — manually, or automatically via Max Submissions or Close Date.

Forms can be renamed, duplicated, shared with collaborators, or deleted from the Forms list.

8. Plan limits

Entry Pass & Pass Scanner — Complete Reference

The attendance pipeline end to end: a pass is issued when someone registers, emailed to them, scanned at the gate by your staff, and recorded in Analytics.

1. The lifecycle

1. Registration — someone submits your GS Form.
2. Issue — a pass is generated with a unique QR token, using the form's mapped Attendee Name and Attendee Email fields.
3. Deliver — the pass is attached to the automated confirmation email.
4. Scan — staff scan the QR at the gate.
5. Record — the check-in appears live in Analytics › Passes.

2. Designing the pass

Built in GS Forms › Pass. See the GS Forms chapter for the full field list: Event Name, Venue, Date, Number of Days, Logo, Card Image and QR Size, plus the pass page blocks (Header, Entry Pass, Response Summary, Text, Button, Footer).

3. Staff codes

4. Using the scanner

1. Staff open Pass Scanner on a phone — it is built for mobile and needs no install.
2. Enter the Staff Code.
3. Grant camera access when prompted ("Camera Access Required").
4. Point the camera at the attendee's QR pass.
5. The result is immediate: Admitted! for a valid pass, or a rejection with the reason. Scan Next moves straight on.

Flag this admission marks a scan for follow-up without stopping the queue. On multi-day events the scanner shows which day it is checking in for.

5. Managing passes

Day-to-day administration lives in Analytics › Passes — activate, block, review status and see who has arrived. Pass Holder Management in the form's Pass tab can re-send or revoke an individual pass.

Analytics — Complete Reference

Turns form responses, pass check-ins and external spreadsheets into dashboards you can read at a glance — with an AI assistant that builds widgets from a sentence.

1. The Analytics home

Lists every data source you can open, with headline numbers across the top: Total Responses, Live Forms, Forms with Data and Most Active Form. Filter by Published, Closed, Has Data or Shared.

2. Data sources

External sources are capped by plan on both size and row count — see §7.

3. The three views

4. Building widgets

Insert Widget adds a visualisation. Each widget has a Widget Title, a Column to read, an Aggregation and optional filtering.

Chart types

Thirty-three visualisations are available:

bar hbar sbar line stepline area pie doughnut scatter bubble dotplot radar gauge bullet stat histogram heatmap treemap sunburst funnel pareto waterfall bridge tornado sankey chord timeline stock leaderboard countdown datatable form ext

A Countdown widget takes a Target Date and Timezone and displays Days / Hours / Minutes / Seconds — useful pinned to the top of a live dashboard.

5. Analytics Intelligence (Gal AI)

Describe the chart you want — "responses per day", "top 5 colleges" — and it builds the widget and offers to Apply to Dashboard. It reads your real columns, so you do not have to know the schema.

6. Pass management

The Passes tab is where attendance is administered.

Select passes individually or in bulk (Select all, Select active, Select blocked) and then Activate or Block them. Useful for revoking a duplicate or reinstating someone turned away by mistake.

7. Sharing, editing and export

• Manage Access — grant others Viewer or Editor rights on a dashboard. People without access see "Access Restricted".
• Edit Mode — a spreadsheet editor that writes back to the connected Google Sheet. Supports Insert, Delete, Freeze, Data validation and Export, and can Open Sheets directly. Columns the platform owns are protected so a stray edit cannot break the pass or mail pipeline.
• Refresh now pulls the latest rows; you are told when new responses are available.

8. Plan limits

Event Assets — Complete Reference

Five live tools for running the room on event day: a stage countdown, judge scorecards, a Q&A slide runner, a leaderboard and a team buzzer. Each has an operator view you drive and a stage view you put on the projector.

1. Countdown Timer

A fullscreen timer with separate presenter and stage views. It has three modes.

2. Judge Scorecard

Template-based scoring with live aggregation across judges.

1. Create a scorecard with an Event name and a Description — short context shown to judges.
2. Load participants: Import CSV / Excel (.csv, .xlsx, .xls), Link Google Sheet, Enter manually (one per line), or let judges add participants live for open-entry formats.
3. Define the criteria judges score on, and the Max per judge ceiling.
4. Give each judge their own passcode — they open the judge view on their own phone, so no shared device and no cross-influence.
5. Watch totals aggregate live as scores come in.

3. Q&A Slide Runner

Quiz and question slides with timers and animated reveals.

Per-set styling covers Heading font, Body font, Transition, per-slide Timer and an Urgency treatment as time runs out. The presenter view drives the stage view.

4. Leaderboard

Live rankings and total scores, fed from the scorecard. Put it on the projector between rounds.

5. Buzzer Round

A fast first-press buzzer for quiz rounds.

1. Open the host view. It creates a buzzer room with a join code.
2. Teams join on their own phones and appear under Connected teams.
3. Press Open Buzzer to arm the round. The first to buzz is locked in and shown to everyone.
4. Award points; the built-in leaderboard tracks the running total.
5. Rotate code issues a fresh join code; Reset all scores clears the board.

6. Plan limits

Gal Studio — Complete Reference

Describe your event once, and Gal Studio builds the whole set — mini-site, registration form, entry pass, confirmation email, response dashboard and budget plan — already wired together.

1. How it works

1. Start a New event and describe it in plain words.
2. Gal Studio runs a short interview, asking only what it genuinely needs — scope first, then branding. It tracks what it has already asked, so you are not made to repeat yourself.
3. Branding arrives as structured cards you approve or change: logo, cover image, palette and fonts.
4. It then builds each deliverable, streaming progress as it goes.
5. Everything lands in your account as real, editable objects — open any of them in its own tool afterwards.

2. What it builds

3. Library and history

Library shows everything Gal has created, grouped by event. Recent events and Search chats get you back to an earlier conversation — the thread is kept, so you can continue refining rather than starting over.

4. Models and AI budget

Choose between Gemini 3.5 Flash and Claude Haiku 4.5. AI usage draws on a monthly allowance:

Your remaining allowance is visible in Settings under AI usage, broken down by tool.

Bulk Certificates — Complete Reference

Design a certificate once, map its text fields to your data columns, and generate a personalised PDF for every recipient — optionally saved to Drive with the links written back to your sheet.

1. Loading recipients

Once loaded, Your Sheet Columns lists the available columns for mapping.

2. The visual certificate editor

Upload your certificate background (drag & drop), then place text fields on it.

3. Output settings

4. Generating

Start the run and watch Progress with live Generated, Failed and Total counters. When it finishes, Download ZIP gives you everything in one archive; the run is recorded in Campaigns.

5. Plan limits

Bulk Mailer — Complete Reference

Send personalised HTML email from your own Gmail account, to a list from a sheet, a file or a GS Form — built with a block editor and an AI writing assistant.

1. Campaign setup

Recipients come from Google Sheets, Upload File (CSV / Excel), Manual Entry, or Import responses from a GS Form.

2. Consent and compliance

Before sending you must declare the basis for contacting these people.

You also classify the mail as Transactional, Promotional, Newsletter, Event, Certificate or Welcome. This is not paperwork for its own sake — it drives the unsubscribe and List-Unsubscribe headers that keep your mail out of spam folders. See the Anti-Spam Policy.

3. Designing the email

Start from a Starting Template or a blank canvas, then Add Block and click any block to edit it in the Properties panel. Tabs split the work into Design, Write and Theme.

Gal AI is available as an email design and writing assistant — describe the message and it drafts copy and layout.

4. Sending and reporting

Sending streams progress with Emails Sent, Failed and Total. Afterwards, Delivery Report and Send Summary show per-recipient status, and the campaign is saved to Campaigns.

5. Daily sending limits

Limits reset daily at midnight IST and depend on your Google account type.

Combined Pipeline — Complete Reference

Generate certificates and email them in one run. It is the Certificate editor and the Mail editor joined by a single job, so nobody is missed and nothing is matched up by hand.

1. When to use it

Use Bulk Certificates when you only need files, Bulk Mailer when you only need email, and Combined Pipeline when each person must receive their own certificate by email — the case where doing it in two steps is where mistakes happen.

2. Setting up the job

1. Job Info — name the run.
2. Load data: Google Sheet link, CSV / Excel upload, manual entry, or Import responses from a GS Form.
3. Design the certificate — the same visual editor, field mapping, fonts and Primary field naming as the Certificates chapter.
4. Design the email — the same block editor, templates and Gal AI assistant as Bulk Mailer, plus the consent declaration.
5. Choose how the certificate reaches people (below), then run it.

3. Delivery options

Certificates can also be bundled after the send so you keep a full set — Download ZIP.

4. Running it

Pipeline Running… streams both halves at once: Certs Generated and Emails Sent, with Failed and Total counters, ending in Pipeline Complete!. The run appears in Campaigns as a Combined job.

Campaigns — Complete Reference

The permanent record of every certificate run, mail send and combined pipeline you have executed.

1. What is recorded

2. Why it matters

Campaign History is the answer to "did this person actually get their certificate?" weeks later. The backup sheet means the record survives even if the original spreadsheet is edited or deleted afterwards.