A clear purpose behind
every color and word.

Japan Retro Game Scout Brand Guidelines

September 25, 2026 · Working design guide. This page documents the decisions behind the current website and gives the team a shared basis for revisions. Color associations and brand concepts describe our design intent; they are not proven findings from buyer research or conversion testing. The service name is provisional.

01. Brand identity: the experience we want to create

In one sentence

An item-search consultation service where U.S. buyers can describe the Japanese retro games and consoles they are looking for.

We want to help someone move from “I know roughly what I want, but I am not sure which details matter” to “I can explain the platform, edition, condition, and accessories I want, and understand the next step.” Nostalgia and the pleasure of discovery draw people in. Clear information helps them start a useful conversation.

Who we are designing for

Our initial audience hypothesis is individual collectors in the United States: people seeking a particular Japanese release, a game with its box and manual, or a console in a specific color. Small resellers seeking several items can also describe quantities in their request. The actual audience mix must be learned from inquiries.

What the buyer wants	What the site provides	What to observe
“I want this Japanese edition.”	Platform, title, edition, and model details	How often a request identifies a specific item
“The box and condition matter to me.”	Separate condition and accessory preferences, plus free text	Which details need follow-up questions
“Will it work with my console?”	Questions to check and links to platform guides	The compatibility questions people ask
“What happens after I ask?”	Request, review, and a reply about whether we can help	Drop-off points and first-response time

Our promise

The planned initial service covers receiving preferences, reviewing the details, asking follow-up questions where needed, and replying about whether we can help. A person handles the reply. Response-time commitments will be set after operational testing. The current concept preview offers a form demo only; it does not send or save requests externally.

Stock, price, sourcing, inspection, and shipping must be checked for the actual item and agreed service conditions. What we say on the website must match what we can deliver.

The name and the operator

In the working name Japan Retro Game Scout, “Japan” identifies the origin of the products, “Retro Game” identifies the category, and “Scout” suggests searching and discovery. The logo can stack the longer name, while body copy uses it on one line where practical. The final name, new domain, and trademark checks remain open.

Identify IGNITE as the operator. Design the service around its audience and acquisition goals; IGNITE’s existing colors are not a requirement. Operator information belongs in About and the footer, alongside a clear explanation of the service.

Core English copy

Role	Copy	Purpose
Audience label	FOR U.S. BUYERS / JAPANESE RETRO GAMES	Make the audience and product origin clear immediately
H1	Looking for a Japanese retro game or console?	State what visitors can ask about
Supporting copy	Tell us the title or model, condition, and budget you have in mind. We’ll review your request and let you know whether we can help.	Explain useful details and the expected next step
Main CTA	Tell Us What You’re Looking For	Invite a conversation in natural language
Category CTA	Request a Game / Request a Console	Carry the chosen item type into the form

Our voice is clear, helpful, and specific. Prefer concrete terms such as “request,” “review,” “Japanese edition,” and “item details.” Avoid unsupported claims such as “best price,” “guaranteed,” “in stock,” or “fast shipping.” Publish reviews, results, and quality promises only when the facts and necessary permissions are available.

Visual direction: September 25 update

The current direction reduces oversized two-color headings, stars, orbital graphics, tilted cards, decorative numbers, and repeated boxed sections. The aim is a calmer catalogue: product imagery and specific headings lead, while useful explanations and navigation remain intact.

The homepage uses four illustrative category images with a clear note that they are examples, not actual inventory. Each leads to the relevant category. Links communicate their function through color, underlines, and focus outlines rather than floating cards or scroll effects.

02. Color palette: why these colors

The palette uses dark text for careful reading, blue for the next action, and small coral accents for warmth and discovery. Japanese identity comes from the products, English copy, and edition details, rather than relying on national-flag colors.

Name	HEX	RGB	Main use	Design intent
Ink	#202B36	32, 43, 54	Headings and primary text	A calm foundation for comparing item details
Ocean	#075985	7, 89, 133	Main CTAs, links, and focus states	Suggest a connection across the ocean and give actions a consistent color
Coral	#E76F51	231, 111, 81	Small accents, such as the preview status dot	Add a little warmth and the pleasure of finding a game
Coral text	#AD442D	173, 68, 45	Occasional supporting emphasis	Keep the coral character with stronger contrast; headings normally use Ink
Cool Gray	#F6F7F8	246, 247, 248	Supporting section backgrounds	Gently distinguish sections from white product and article surfaces
Pale Blue	#EDF2F5	237, 242, 245	Explanation panels and request guidance	Group supporting information without competing with it
White	#FFFFFF	255, 255, 255	Forms, articles, and cards	Present copy and product photography plainly
Muted	#53616E	83, 97, 110	Supporting text	Establish hierarchy without making text excessively faint
Border	#D4DCE1	212, 220, 225	Subtle card and section boundaries	Separate surfaces; use stronger outlines where controls need them
Error	#B42318	180, 35, 24	Input errors	Identify what needs correction, together with an explanation
Success	#166534	22, 101, 52	Confirmed receipt	Indicate success only after successful persistence is confirmed

Proportions and text combinations

White and Cool Gray form the base. Ocean is primarily for buttons and links. Limit Coral to small accents rather than repeatedly splitting headings into two colors. Large dark surfaces should be exceptional; the footer is their main location.

Use white text on Ocean buttons and Ink or Muted text on pale surfaces. Do not place small white text on Coral or use Coral for regular body text on light backgrounds. Use Coral text for occasional emphasis on pale surfaces. Errors and completion states need words, state labels, or icons as well as color.

How to decide on a color change

To make the experience more playful, first adjust imagery and the area given to Coral. To make it calmer, increase neutral space and reduce competing emphasis. To make a request button more noticeable, first check nearby spacing and the number of competing links. After changing colors, review the hero, form, article, and footer on desktop and mobile together.

03. Typography: clear explanations with character

Use DM Sans for English headings and body copy. Headings generally use weight 600, body copy 400, and links 600–700. Keep long descriptions and item conditions easy to follow. Pixel fonts do not belong in body copy or form controls.

Element	Reference size	Guidance
H1	Home approximately 39–60px; inner pages 32–49px; line height 1.12–1.2	One per page; prefer a short question and a specific subject
H2	Approximately 27–40px; line height 1.2–1.3	Explain the section directly; article headings are around 29px
H3	Approximately 24–26px	Card headings and subsections
Body	16px; line height 1.65	Keep important conditions in the explanation
Hero description	17px; line height around 1.8	Explain the audience, useful input, and next action
Form input	16px	Keep entered text readable on mobile
Supporting text	12–14px	Do not hide essential information in small print

This guide also uses the English site’s typeface. Longer guidance can use 16–17px body text with more generous line spacing. Review natural English line breaks rather than preserving line breaks from a Japanese draft.

04. Buttons and forms: one clear way to start

Type	Specification	Use
Main CTA	Ocean background, white text, 4px radius, 48px minimum height	Start an item-search request
Small CTA	40px minimum height, 4px radius	Compact areas such as the header
CTA on a pale surface	Ocean background and white text	Closing sections
Secondary link	Ocean text, underline, and optional arrow	How It Works, FAQs, and category information
Disabled control	Disabled state with a clear reason	Unavailable actions or incomplete input

Keep the main action consistent within each section. Carry the selected game or console type into the request form to avoid repeated choices. Prefilling a preference does not confirm that the item is available.

Only two fields are required to begin: what the visitor is looking for or asking about, and their reply email address. Item type, platform, edition, condition, accessories, quantity, budget, U.S. state, and preferred name belong in optional details. More precise requirements and photos can be discussed by email later. The demo validates input and shows a completion example, but does not send or save it externally.

05. Cards: from illustrative examples to real products

Keep the image-led list format. A card should present image → type and name → description → useful preferences → request action. For games, help people distinguish media, editions, and packaging. For consoles, help them distinguish model, color, and accessories.

The current cards show product-type examples because actual inventory data is not available. Move to real product listings when the following information is available.

Real product field	Purpose and rule
Official name and Japanese name	Support search and accurate item matching
Platform, model, edition, and region	Distinguish similar names and different versions
Actual photographs	Match the pictured item to the listed unit or product
Condition and scope of testing	Separate verified details from unverified details
Box, manual, and accessories	List exactly what is included
Listing status and verification date	Distinguish inventory, search examples, and items awaiting confirmation
Request button	Carry the item name or ID forward; purchasing is a separate future decision

Do not invent prices or availability badges. Keep card corners, spacing, and image ratios consistent. Explain important differences, such as condition, in text as well as images.

06. Logo and icons: restrained signs of discovery

The temporary mark is an Ocean square containing “JR.” Avoid star motifs, orbital decorations, and stamp-like embellishments. Use arrows to support a real action or direction, and hide purely decorative icons from assistive technology.

“JAPAN → USA” describes product origin and the intended audience. It is not proof of shipping capability or a delivery-area guarantee. A final logo will need minimum sizes, clear space, and a monochrome version. It should have its own identity rather than resemble a game manufacturer’s logo.

07. Layout: follow the buyer’s sequence of questions

The homepage follows audience and promise → buyer preferences → product categories → three request steps → concrete input examples → FAQ → CTA. A first-time visitor should understand who it is for, what they can ask about, and what to do next.

Use a desktop container of up to 1180px with at least 24px side padding. Keep long-form reading areas around 860px wide. Typical section spacing is about 72px on desktop and 48px on mobile; shorter sections may use less. Cards can move between three, two, and one column without stripping away useful explanations.

Alternate White, Cool Gray, and Pale Blue according to content grouping. Avoid adding a new color for every section.

08. Responsive behavior: make mobile requests easy

Width	Main behavior	Check
Around 1440px	Two-column hero and three-column product cards	Comfortable line lengths and a clear CTA hierarchy
768–950px	Two-column cards and tighter spacing	Text overlap and header fit
375–740px	Single-column hero, body, and form; the small homepage image list can retain two columns	Unwanted horizontal scrolling, usable controls, and input text size

The mobile menu must open and close, with access to Games, Consoles, Blog, How It Works, FAQ, and Request. Keep explanations and CTAs as HTML text rather than embedding them in images. Wide comparison tables may scroll within their own container.

09. Interaction: make actions understandable

Use background changes for button hover states and color or underlines for links. Avoid lifting or translating cards and buttons. Provide visible keyboard focus and respect reduced-motion preferences.

FAQs expand by question so answers remain easy to browse. Distinguish the preview’s demo completion screen from a real receipt. Explain that the demo does not send anything. A future live success screen must appear only after the server confirms successful storage.

10. Photography: help people judge the item

The current generated illustrations are temporary concept images. Real product listings should use original photographs or images with permission to publish. Do not reuse competitors’ product photographs.

Use consistent backgrounds, lighting, and camera distance. Show the whole item, reverse side, labels, wear, connectors, and accessories as needed. Do not edit away scratches or yellowing that affect condition. Keep price and availability in editable text rather than baking them into images.

Use	Suggested ratio	Presentation and management
Product lists	1:1	Match photographs to the listed unit or product
Blog cards	Around 5:4	Use images that explain the article’s subject
Article photographs	As the subject requires	Include captions, sources, and useful alternative text
Decoration	Flexible	Do not place essential information only in a decorative image

For new photography, consider WebP or AVIF and provide sizes appropriate to the layout. The current illustrations are PNG placeholders; the real-photography optimization workflow is still to be established.

11. Page roles and revision criteria

Page	Main role	Preserve when revising
Home	Explain the audience, promise, and entry point	The H1 and opening copy should explain the service on their own
Games / Consoles	Make the requested item more specific	A clear distinction between examples and actual products
Platform pages	Explain details relevant to that platform	Verify original information, imagery, and service scope before general release
Request	Receive the buyer’s preferences	Prefilled item type, minimal required fields, and the next step
How It Works	Explain what follows a request	Promise only stages the team can actually handle
FAQ	Resolve doubts before a request	Specific guidance about price, condition, quantity, region, and compatibility
Blog	Answer questions before buying	Supporting evidence and a useful next action
About / Contact	Identify the operator and contact route	Verified company information and a functioning contact channel
Site Map	Show the overall structure	Update it when pages are added

Assign search intent to each page and connect its title, description, H1, and body naturally. Search volume is not a count of buyers. Draft articles still need article-level keyword and competitor validation where this has not been completed. Compatibility guidance must distinguish verified technical facts from questions that still need checking.

For useful revision requests, include page / location / current issue / intended impression / proposed change / verification method. For example: “The main CTA blends into nearby links. Give it more space and reduce competing emphasis, then compare the result at 375px and 1440px.”

12. Footer, maintenance, and revisions

The footer identifies the operator and links to Games, Consoles, Blog, FAQ, About, Contact, Privacy, Terms, and Site Map. Label future categories and comparison pages as “Future” to distinguish them from available services.

Record the reason for a change, affected pages, decision owner, and verification result. Start color changes in shared variables rather than adding scattered overrides. Check consistency with metadata, imagery, and form copy. After a change, compare the rendered page with this guide.

Technology and current status

The site is currently an Astro-generated concept preview. Its form demo validates input and shows an example completion state without external submission or storage. Before accepting real inquiries, align the displayed service conditions, contact details, Privacy, and Terms with the actual operation.

This guide is a working record of brand intent and implementation. Revise it, with the reason for the change, whenever imagery, content, or operations change.