> For the complete documentation index, see [llms.txt](https://sitesbyseth.gitbook.io/sitesbyseth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sitesbyseth.gitbook.io/sitesbyseth-docs/skeleton/sections/main-password.md).

# Password page

Skeleton's drop mode: a full-screen hero with a background photo or looping video, your logo, an optional launch countdown, and waitlist signup blocks. A lock icon in the top-right opens the password prompt for people who have the store password. The full walkthrough (including turning on password protection) is in [Drop mode](/sitesbyseth-docs/skeleton/getting-started/drop-mode.md); this page is the reference.

**Where to find it:** theme editor → page selector → **Others → Password** → click **Password page**.

## Settings

### Logo

* **Logo image** — falls back to your store name as text.
* **Logo width** (60–280 px, default 120).
* **Logo position** — **Top left** or **Top center** (default).

### Background

* **Background video** — autoplays muted on a loop; used instead of the image when set.
* **Background image** — used when no video is set.
* **Overlay opacity** (0–90%, default 40) — darkens the media behind the text.
* **Text color** (default `#FFFFFF`).

### Countdown

* **Launch date and time** — format `YYYY-MM-DD HH:MM` (24-hour), e.g. `2026-08-01 18:00`. Counts down in each visitor's local time zone. Leave empty to hide the countdown.
* **Countdown label** (default "Dropping in").
* **Text when finished** (default "We're live") — leave empty to hide the countdown when it reaches zero.

### Content

* **Heading** (default "Opening soon").
* **Show password page message** (on by default) — displays the message set in **Online Store → Preferences → Password protection**.

## Blocks

### Email signup (1 max)

Uses Shopify's built-in customer capture — signups appear in **Customers** tagged `prospect, password page`.

* **Placeholder** (default "Email address").
* **Button label** (default "Claim early access").
* **Success message** (default "You're on the list.").

### SMS signup (1 max)

Collects phone numbers and posts them to your SMS provider.

* **SMS provider form URL** — the form endpoint from your provider (Klaviyo, Postscript, Attentive, etc.). The box only appears once this is set.
* **Phone field name** (default `phone`) — the input name your provider expects.
* **Placeholder** (default "Phone number").
* **Button label** (default "Claim early access").

### Custom Liquid

* **Liquid code** — app snippets, embeds, or any HTML/Liquid. Multiple blocks allowed.

💡 **Pro tip:** a 10-second video loop with the overlay at 40–50% outperforms a static image for waitlist signups — motion holds attention just long enough to type an email. Keep exactly one signup method visible unless you genuinely run SMS campaigns; a lone email field converts better than a stack of choices.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sitesbyseth.gitbook.io/sitesbyseth-docs/skeleton/sections/main-password.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.