> For the complete documentation index, see [llms.txt](https://docs.openspaces.design/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openspaces.design/plain-jane-interactive/customer-accounts/register-page.md).

# Register Page

### **What You’ll Learn**

* How to enable and customize the legacy register page for new customer accounts
* How to update form styling, placeholder text, button design, and links
* How to use your theme’s visual settings to match your brand

***

### 🧩 Overview

This register page is built using the **legacy customer account system** and is fully supported by your theme’s visual editor. It includes flexible layout tools, form styling, and optional brand imagery — ideal for a branded account sign-up experience.

> ⚠️ Shopify's newer one-click login system bypasses this page. These settings apply **only when using legacy accounts**.

***

### 🎨 Page Structure

The register page typically includes:

* **Logo & Clock** (Optional)
* **Register Form** (Main section)
* **Music Player** (Optional)
* **Footer** (Optional)

***

### ✏️ Customizing the Register Form

Navigate to:\
**Theme Editor → Templates → customer/register.liquid**\
Click on the **Register Form** section to open settings.

***

#### 🖼 Register Side Image

* Upload a **side image** for the form (optional)
* **Switch Side Image Position** – Left or right
* **Remove Side Image** – Toggle off completely
* **Curve Side Image** – Adds rounded visual styling

***

#### 🧾 Header Content

* **Header Text** – Typically “Register” or “Create Account”
* **Sub-Header Text** – Add a short intro message
* Customize **text colors** for both elements

***

#### 🧍 Form Fields

Each field group includes individual label, border, and text color controls.

**First Name**

* Label, Border, Text Color

**Last Name**

* Label, Border, Text Color

**Email Address**

* Label, Border, Text Color

**Password**

* Label, Border, Text Color

> 💡 Tip: Consistent styling improves perceived trust during onboarding.

***

#### 🔘 Join Button

* **Button Text** (e.g. “Join” or “Create Account”)
* **Background Color**
* **Text Color**

This button submits the registration form.

***

#### ❗ Error Message Styling

* Set **Register Error Info Text Color** to match alert or warning styles (e.g. red)

***

#### 🔗 Additional Links

* **Already Signed Up?**\
  Add a prompt to redirect users to the login page
* **Back To Store Link**\
  Useful if customers want to return to the homepage

Each of these can be renamed and recolored.

***

#### 🌀 Miscellaneous

* Toggle **"Enable Radius On Inputs & Buttons"** to apply rounded corners

***

### ✅ You’re Done!

Your register page is now styled and ready at:\
`yourstore.com/account/register`

> 💡 Tip: Use the same brand imagery and language across your Login and Register pages for visual consistency.

### **Need Help?**

* 💬 **Join our community on Discord:** <https://discord.gg/hcc2GvgZc6>
* 📧 **Email us at:** <support@openspaces.design>
* 💻 **Live chat with us:** Available Monday–Friday, 10AM–6PM EST, directly on our website


---

# 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://docs.openspaces.design/plain-jane-interactive/customer-accounts/register-page.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.