Tiron Agency · Internal Guide

Logging into Payload CMS
& Adding a New Brand

A step-by-step walkthrough for adding a new brand entry to the Brands collection — from signing in to publishing the live page.

Payload CMS Brands Collection ~5 min read
01

Log in to the CMS

Go to the admin URL for the site (the live domain followed by /admin) and sign in with the email and password provided by your admin. If you don't have credentials yet, ask your project lead to create an account for you.

Note: once logged in, you'll land on the Dashboard — this is your home base for every collection on the site.
02

Open the Brands collection

From the Dashboard, find Brands in the left-hand sidebar under Collections, or click the Brands card in the main panel. Both take you to the same place.

Payload CMS dashboard with the Brands item highlighted in the sidebar
Dashboard view — Brands is listed under Collections in the sidebar
03

You'll now see the full list of existing brands, sorted by when they were last updated. Each row shows the brand's Name, Slug, and publish Status.

Brands collection list showing published brands and a Create New button
Brands collection — 18 brands currently published, paginated 10 per page
04

Create a new brand

Click the Create New button at the top of the Brands page, next to the page title. This opens a blank brand entry ready for you to fill in.

05

Add the name & images

Start with the essentials at the top of the form:

  • Name *
  • Logo
  • Featured Image

Type the brand name into the Name field — the Slug on the right generates automatically from it (click Unlock if you ever need to edit the slug manually). For Logo and Featured Image, either drag a file in, upload a new one with Create New, or reuse something already in the Media library with Choose from existing.

Top of the brand edit form showing Name, Logo, Featured Image and the start of the Hero section
Brand edit screen — name, media fields, and the Hero section
06

Fill in the content sections

Scroll down to build out the rest of the page. Each section maps to a block on the published brand page:

  • Hero — Eyebrow / Title / Text
  • Features
  • About — Text + Background Media
  • Bento Grid + Cards
  • Categories

Use Add Feature, Add Card, and Add Category to add as many repeatable items as the brand needs — none of these sections are required to publish, so it's fine to leave sections empty if a brand doesn't need them.

Bento Grid, Cards, and Categories sections of the brand edit form
Further down the form — Bento Grid, Cards, and Categories
07

Add FAQs & SEO details

Near the bottom, link any relevant entries under Faq using the dropdown, or click the + to create a new one on the spot.

Then fill in the SEO block — a Title (50–60 characters) and Description (100–150 characters). Payload checks the character count live and flags anything missing in red, so aim to clear all checks before publishing.

FAQ selector and SEO title/description fields with live character-count checks
Faq and SEO — character counts update as you type
08

Publish the changes

Once everything looks right, click Publish changes in the top-right corner. The status label will switch from Changed — Revert to published to Published, and the brand goes live at its slug.

Tip: Payload autosaves drafts as you work, but nothing appears on the live site until you click Publish.
09

Check the live page

Visit /brand/[slug] on the live site to see the brand page exactly as customers will. Everything you entered — Hero, About, Cards, and Faq — renders in order down the page.

Live HP brand page showing the About section and feature cards
Live brand page — About section and "What sets it apart" cards
Live HP brand page showing product cards, a quote CTA banner, and the FAQ accordion
Live brand page — product cards, quote CTA, and Faq accordion

That's it

New brands follow this same pattern every time — the only real variables are the content and images you drop into each section. When in doubt, look at a published brand like Mikrotik or HP as a reference for how much content each block expects.