> 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/showcase/sections/main-password.md).

# Early access

The password page as a drop teaser: full-screen story-style screens with an email/SMS signup where Add to cart would normally be. A minimal header carries an optional Support link (left), your logo (center), and the lock icon that opens the password entry window (right). Signups are saved as customers tagged `early-access` and `prospect`.

👉 **Customize → page selector → Others → Password → Early access** section. Walkthrough: [Drop mode](/sitesbyseth-docs/showcase/getting-started/drop-mode.md).

## Section settings

### Branding & support

* **Logo** + **Logo width** (60–300px, default 120px) — centered in the header; store name shows as text when empty.
* **Support email** — adds a "Support" link top-left that opens the visitor's mail app. Empty = hidden.
* **Email subject** (default "Early access question") — pre-filled subject line for that email.

### Signup

* **Collect** — `SMS only`, `Email only`, or `SMS and email` (default). Controls which input fields the form shows; with both, one button submits either/both.
* **Signup button text** (default "Get early access").
* **Note under the form** (default "Be first when the doors open") — small print under the fields; good spot for consent wording if you collect SMS.
* **Success message** (default "You are on the list") — replaces the form after a successful signup.

### Experience

* **Screen transition** — `Fade (no sliding)` (default) or `Scroll`. Fade needs 2+ blocks.
* **Show scroll hint on first screen** (on).
* **Slideshow navigation** — `Arrows` (default), `Dots`, `Arrows and dots`, or `None (swipe only)`.

## Blocks

### Product screen

Pulls name, description, and up to 5 images from a catalog product — ideal when the drop items already exist in your admin (the store is locked, so nothing is buyable).

* **Product** — the catalog product to tease.
* **Name override** — replace the real title (tease with "Piece 001"). Empty = product title.
* **Tagline** (default "EARLY ACCESS") — small text next to the screen number.
* **Story override** — rich text; empty = the product's description (trimmed).
* **Background image** / **Background color** (default `#F3F0EA`, used when no image) / **Overlay darkness** (0–90%, default 35%) / **Text color** (`Auto`/`Light`/`Dark`) / **Info style** (`Transparent`/`Glass panel`).
* **Accordions** — **Shipping title** (default "Shipping") + content, and **How to cop title** (default "How to cop") + content. Each renders only when its content is filled.

### Custom screen

Fully manual — for products that aren't in the catalog yet.

* **Product name** (default "Coming soon") and **Tagline** (default "EARLY ACCESS").
* **Description** — rich text.
* **Image 1 / 2 / 3** — up to three uploads for the 3D slideshow. On this screen type, the first image sets the slideshow's frame shape and the others crop to match.
* **Background** and **Accordions** — identical to the Product screen above.

## Pro tip

💡 Mix screen types: open with a Custom screen as a title card ("SS26 — 03.14, 10AM EST" as the name and tagline), then Product screens for the actual pieces. Use the **How to cop** accordion to spell out the drop mechanics — sizes run, quantity per person, restock policy — so launch-day DMs don't eat your morning.


---

# 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/showcase/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.