About Platform Resources Articles Contact
IMA AI  ·  Resources

IMA AI Website
Naming Standard

A consistent file and asset naming convention for every IMA AI web project — marketing sites, client sites, and group products. Applied without exception across all tiers.

Version  v1.4 — June 2026
Scope  All IMA AI web projects
Classification  IMA AI Internal · Strictly Confidential
Section 1

Core Rules

All file names across every IMA Group property must follow these rules without exception.

RuleStandardExample
CaseAlways lowercase — no uppercase lettersindex-hero.webp  NOT  Index-Hero.webp
SeparatorHyphens only — no underscores, no spacesabout-team-img-1.webp  NOT  about_team_1.webp
SpacesNever use spaces in any file nameproduct-banner.webp  NOT  product banner.webp
NumberingIf the type can ever have siblings — always number, even if only one exists todayindex-sep-1.webp, index-who-we-are-img-1.webp
No numberingIf the type can only ever be one — never add a numberindex-hero-1.webp, index-og-1.webp, about-ceo-avatar-1.webp
DescriptorsUse short, meaningful English wordsindex-who-we-are-img-1.webp
ExtensionsAlways include correct file extension.webp .mp4 .svg .pdf
VersionsAdd -v2, -v3 only for archived alternatives — live files have no version suffixindex-hero-1-v2.webp (archived draft only)
Section 2

The File Name Formula

Every asset file follows one consistent pattern. The order is always page → descriptor → type → number.

[page]-[descriptor]-[type]-[number].[ext]

Examples: service-web-sep-2.webp  ·  index-who-we-are-bg-1.webp  ·  about-ceo-avatar-1.webp

[page]
Which page this file belongs to
Required
[descriptor]
Identifies the section or content on the page
When needed
[type]
What kind of asset — the role it plays
Required
[number]
Sequence number — always required, start at 1
Always
Critical order rule: The descriptor always comes before the type. index-who-we-are-bg-1.webp ✓  ·  index-bg-who-we-are-1.webp

2.1  Numbering Rules

Always include a number. Every file. Every type. No exceptions.

Why always number? If you name today's only hero image index-hero.webp and later add a second for a slider, you are forced to rename the first file and update every reference in your code. If you start with index-hero-1.webp, adding a second is just adding index-hero-2.webp — nothing else changes. Rule of thumb: always start at 1. When you add a second file, just add 2. Nothing ever needs to be renamed.
ScenarioWrong ✗Right ✓
Single hero imageindex-hero.webpindex-hero-1.webp
Hero slider — first imageindex-hero-1.webpindex-hero-1.webp
Hero slider — second imageindex-hero-2.webp (forces rename of first)index-hero-2.webp (no rename needed)
Single separatorindex-sep.webpindex-sep-1.webp
Single OG imageindex-og.webpindex-og-1.webp
CEO avatarabout-ceo-avatar.webpabout-ceo-avatar-1.webp
Product cardproduct-baju-kurung-moden-card.webpproduct-baju-kurung-moden-card-1.webp
Product demo videoproduct-baju-kurung-moden-demo.mp4product-baju-kurung-moden-demo-1.mp4

2.2  Language Variant Suffix

When the same asset exists in more than one language, add a language code immediately before the number.

[page]-[descriptor]-[type]-[lang]-[number].[ext]
RuleDetail
CodesISO 639-1, two letters: en (English), zh (Chinese/Mandarin), ms (Malay)
When to useOnly when language variants actually exist. Single-language assets keep the plain pattern — English is the unmarked default, so no existing file needs renaming.
PositionAlways between type and number. ✅ ...-gallery-en-1.webp   ✗ ...-en-gallery-1.webp
No text in imageAn image with no text is language-neutral — no suffix needed. The suffix only marks the language of text rendered inside the image.
Example fileWhat it is
social-platform-marketing-playbook-gallery-en-1.webpIG carousel — cover card (English)
social-platform-marketing-playbook-gallery-zh-1.webpRedNote carousel — cover card (Chinese)
Section 3

Page Codes

Use these standardised short codes as the [page] prefix for all files.

CodePageURL example
404Error / not found page/404
aboutAbout us / company page/about
accountCustomer account dashboard/account
articleIndividual article page/article-[slug]
articlesArticles listing page/articles
blogBlog listing page/blog
cartShopping cart page/cart
caseSingle case study detail/portfolio/client-name
checkoutCheckout page/checkout
collectionProduct collection / category page/collection/[category]
contactContact page/contact
faqFrequently asked questions/faq
globalShared across all pages — nav, footer, logos, fonts
indexHomepage / main landing page/
landingCampaign or ads landing page — separate from homepage/promo/raya-sale
legalPrivacy policy, terms, returns policy/privacy, /terms, /returns
loginLogin / magic link page/account/login
ordersOrder history page/account/orders
platformIMA AI platform product and service pages/platform-[product] or /platform-[product]-[service]
portfolioWork / case studies listing/portfolio
postIndividual blog post/blog/[slug]
pricingPricing tiers page/pricing
productIndividual product detail page/product/[slug]
promoSale or promotions page/promo/12-12
resourceSingle resource detail page/resources/the-platform-marketing-playbook
resourcesResources, downloads, guides listing/resources
serviceIndividual service detail page/service/[slug]
socialSocial media post assets — IG, RedNote, Facebook carousels
teamTeam / people page/team
thanksPost-purchase thank you page/thank-you
Listing vs Detail: Some pages come in pairs. They share one image folder but use different prefixes. resources- = listing page. resource- = detail page. Same pattern applies to blog / post, articles / article, and portfolio / case.
Section 4

Type Codes

Use these standardised short codes as the [type] token in the file name.

4.1  Images

Type codeMeaningTypical usageExample
heroFull-width hero/banner image at top of pageAbove the fold, primary visualindex-hero-1.webp
sepSeparator/divider image between sectionsVisual breaks between content blocksindex-sep-1.webp
bgBackground image for a sectionSits behind text or overlaid contentabout-values-bg-1.webp
cardCard or thumbnail imageProduct cards, blog post thumbnailsproduct-main-card-1.webp
galleryGallery or detail imageProduct image gallery (multiple shots)product-main-gallery-1.webp
imgGeneral content image within a sectionPaired with text in a sectionindex-who-we-are-img-1.webp
avatarPerson photo or profile imageTeam bios, founder, testimonialsabout-ceo-avatar-1.webp
ogOpen Graph / social share imageMeta tags for social previewsindex-og-1.webp
thumbThumbnail imageVideo thumbnails, small previewsblog-post-thumb-1.webp
patternDecorative pattern or textureBackground texture fillsglobal-pattern-1.webp
iconIcon file (non-SVG raster fallback)PNG icons when SVG is not possibleproduct-free-shipping-icon-1.png

4.2  Videos

Type codeMeaningTypical usageExample
heroHero/banner video (autoplay, muted)Full-width background video above foldindex-hero-1.mp4
sepSeparator video between sectionsAnimated visual breakindex-sep-1.mp4
demoProduct demo or explainer videoHow it works, product walkthroughproduct-main-demo-1.mp4
bgBackground video for a sectionLooping video behind contentabout-values-bg-1.mp4
storyBrand story or founder videoAbout page, brand valuesabout-brand-story-1.mp4

4.3  Documents & Other

Type codeMeaningExample
brochureDownloadable product or company brochureindex-brochure-1.pdf
certCertificate, award, or accreditationabout-cert-halal-1.pdf
policyLegal document — privacy, terms, returnsglobal-privacy-policy-1.pdf
dataStructured data file (JSON, CSV)global-data-products-1.json
fontCustom web font fileglobal-inter-regular.woff2
Section 5

Full Examples — By Page

Reference file names for the most common page types. Follow these patterns exactly.

5.1  Homepage (index)

File nameWhat it is
index-hero-1.webpMain hero image at the very top of the homepage
index-hero-1.mp4Hero video version (if using video background)
index-sep-1.webpFirst separator image (after hero section)
index-sep-2.webpSecond separator image (further down the page)
index-who-we-are-bg-1.webpBackground image for the Who We Are section
index-who-we-are-img-1.webpContent image inside the Who We Are section
index-features-bg-1.webpBackground for the features/benefits section
index-features-img-1.webpFirst image in the features/benefits section
index-features-img-2.webpSecond image in the features/benefits section
index-og-1.webpOpen Graph image for social sharing (1200×630px)

5.2  About Page (about)

File nameWhat it is
about-hero-1.webpHero banner at top of About page
about-story-img-1.webpImage for the brand story / founding section
about-story-img-2.webpSecond image in brand story section
about-ceo-avatar-1.webpCEO headshot photo
about-coo-avatar-1.webpCOO headshot photo
about-team-img-1.webpTeam group photo
about-sep-1.webpSection separator on About page
about-values-bg-1.webpBackground image for values section
about-halal-cert-1.webpHalal certification image
about-og-1.webpOpen Graph image for About page social sharing

5.3  Product Page (product)

The descriptor is always the product slug — lowercase, hyphens only, no special characters. All products share one folder: images/product/.

File nameWhat it is
product-baju-kurung-moden-gallery-1.webpPrimary photo of Baju Kurung Moden (main image)
product-baju-kurung-moden-gallery-2.webpSecond photo — angle 2
product-baju-kurung-moden-gallery-3.webpThird photo — detail shot
product-baju-kurung-moden-gallery-4.webpFourth photo — lifestyle shot
product-baju-kurung-moden-card-1.webpThumbnail shown on collection/category grid
product-baju-kurung-moden-og-1.webpOpen Graph image for social sharing
product-baju-kurung-moden-demo-1.mp4Product video (if available)
product-tudung-bawal-pleated-gallery-1.webpPrimary photo of Tudung Bawal Pleated
product-tudung-bawal-pleated-card-1.webpThumbnail for Tudung Bawal Pleated

5.4  Service Page (service)

The descriptor is the service slug. All service images share images/service/.

File nameWhat it is
service-web-design-hero-1.webpHero image for Web Design service page
service-web-design-process-img-1.webpFirst image in the process / how it works section
service-web-design-process-img-2.webpSecond image in the process section
service-web-design-card-1.webpCard thumbnail shown on services listing page
service-web-design-og-1.webpOpen Graph image for social sharing
service-seo-audit-hero-1.webpHero image for SEO Audit service page
service-seo-audit-card-1.webpCard thumbnail for SEO Audit on listing page
service-ai-chatbot-demo-1.mp4Demo video for AI Chatbot service

5.5  Global / Shared Files (global)

File nameWhat it is
global-logo-1.svgPrimary full-colour logo (SVG — preferred)
global-logo-1.webpPrimary logo fallback (WebP — for email/OG use)
global-logo-white-1.svgWhite version of logo (dark backgrounds)
global-logo-dark-1.svgDark version of logo (light backgrounds)
global-favicon.icoBrowser tab favicon (32×32)
global-favicon-192.pngPWA icon (192×192) — PNG required by spec
global-favicon-512.pngPWA icon (512×512) — PNG required by spec
global-og-default-1.webpDefault Open Graph image (used if no page-specific OG)
global-pattern-1.webpRepeating decorative background pattern
global-inter-regular.woff2Custom web font — Inter Regular
global-inter-bold.woff2Custom web font — Inter Bold
global-privacy-policy-1.pdfDownloadable privacy policy
global-returns-policy-1.pdfDownloadable returns policy
Favicon generation: Never create favicon files manually one by one. Use RealFaviconGenerator (realfavicongenerator.net): upload one high-resolution square logo (at least 512×512px SVG or PNG). It outputs the full package — global-favicon.ico, global-favicon-192.png, global-favicon-512.png, Apple Touch icon, and the HTML to paste into the site head. Rename the downloaded files to match this naming standard before adding to the repo.

5.6  Social Carousels (social)

IG and RedNote carousels are gallery sequences — same cards, language-tagged. The descriptor is the post slug; all posts share images/social/.

File nameWhat it is
social-platform-marketing-playbook-gallery-en-1.webpIG carousel — cover card (English)
social-platform-marketing-playbook-gallery-en-2.webpIG carousel — card 2
social-platform-marketing-playbook-gallery-zh-1.webpRedNote carousel — cover card (Chinese)
social-platform-marketing-playbook-gallery-zh-2.webpRedNote carousel — card 2
No text on a card? Drop the language suffix — social-[slug]-gallery-1.webp is shared across platforms. In a bilingual set that mixes text and neutral cards, tag every card (-en / -zh) so each platform keeps a complete 1→N sequence.
Section 6

Folder Structure

HTML files sit directly at root. All assets live in their matching subfolder. Maximum folder depth is always 2 subfolders — never create a third level.

/public/

├── index.html                    ← homepage
├── about.html                    ← about page
├── resources.html                ← resources listing page
├── resource-[slug].html          ← each resource detail page
├── articles.html                 ← articles listing page
├── article-[slug].html           ← each article page
├── platform-[product].html       ← platform product overview page
├── platform-[product]-[service].html  ← platform service page
├── service-[slug].html           ← each service page
├── sitemap.xml                   ← always at root
├── robots.txt                    ← always at root
├── site.webmanifest              ← always at root
├── favicon.ico                   ← always at root
├── apple-touch-icon.png          ← always at root
├── web-app-manifest-192x192.png  ← always at root
├── web-app-manifest-512x512.png  ← always at root
├── .gitignore                    ← always at root

├── images/
│   ├── index/        ← homepage images
│   ├── about/        ← about page images
│   ├── resources/    ← resources listing + resource detail images (both share this)
│   ├── service/      ← all service images (all slugs share this folder)
│   ├── product/      ← all product images (all slugs share this folder)
│   ├── articles/     ← articles listing + article detail images (share this folder)
│   ├── platform/     ← all platform product pages (id, ca, ac, cs, etc.)
│   ├── blog/         ← blog images
│   ├── portfolio/    ← portfolio listing images
│   ├── case/         ← case study images
│   ├── landing/      ← campaign landing page images
│   ├── promo/        ← sale / promotions images
│   └── global/       ← logos, OG defaults, patterns

├── videos/
│   ├── index/        ← homepage videos
│   ├── product/      ← product demo videos
│   ├── service/      ← service demo videos
│   ├── landing/      ← campaign landing videos
│   ├── global/       ← shared / brand assets
│   └── social/       ← IG / RedNote / FB post assets (all posts share, grouped by slug)

├── icons/         ← all SVG icon files
├── fonts/         ← web font files (.woff2)
└── docs/          ← downloadable PDFs and documents
resources/ and resource/ share one folder. The prefix tells you which page the file belongs to. resources- (with s) = listing page. resource- (no s) = detail page.
images/resources/
├── resources-hero-1.webp                           ← listing page hero
├── resources-sep-1.webp                            ← listing page separator
├── resource-the-platform-marketing-playbook-hero-1.webp  ← detail page hero
├── resource-the-platform-marketing-playbook-card-1.webp  ← card shown on listing
└── resource-the-platform-marketing-playbook-og-1.webp    ← OG for social sharing
Favicon files must stay at root. favicon.ico, apple-touch-icon.png, web-app-manifest-192x192.png, web-app-manifest-512x512.png, and site.webmanifest must all stay at the root — never move them to a subfolder. Browsers look for favicon.ico at yourdomain.com/favicon.ico automatically. iOS looks for apple-touch-icon.png at root when saving to home screen. Moving them breaks favicons on all browsers and iOS.
sitemap.xml and robots.txt must stay at root. Search engines look for them at yourdomain.com/sitemap.xml and yourdomain.com/robots.txt exactly. If they are in a subfolder, Google cannot find them.
All products share one folder. Do not create a subfolder per product. The product name in the file name is enough to group them. Sorting by name in any file manager will naturally cluster all images for the same product together. The same rule applies to services.

Folder depth rule

LevelExample
Root/public/
Subfolder 1 — asset typeimages/
Subfolder 2 — page codeproduct/
Fileproduct-baju-kurung-moden-gallery-1.webp
Section 7

Image Format & Compression Standard

All images must be exported as WebP. No JPG, PNG, or GIF — with the exceptions listed below.

7.1  Format Rules

FormatWhen to useWhen NOT to use
WebPAll photos, hero images, separators, backgrounds, cards, OG images, thumbnailsNever use for logos, icons, favicons, or fonts
SVGAll icons, logos, and simple illustrations — infinite scale, tiny file sizeNever use for photos or complex images
PNGFavicon (192px, 512px PWA icons) only — required by PWA specDo not use for anything else — use WebP instead
ICOFavicon (.ico browser tab icon) only — generated by RealFaviconGeneratorDo not use for anything else
MP4 (H.264)All videos — hero background, demo, separatorDo not use .MOV, .AVI, or .WEBM as primary format
WOFF2All custom web fontsDo not use .TTF or .OTF on the web
PDFDownloadable documents onlyDo not use as display assets on web pages

7.2  WebP Compression Standard

Use these quality settings when exporting. Lower quality = smaller file = faster page load. Always check visually after compression.

Image typeDimensionsWebP qualityMax file sizeNotes
Hero image1920 × 900pxQ80150KBFocal subject centred — works for desktop and mobile crop
Hero video (poster frame)1920 × 900pxQ75100KBShown before video loads — compress aggressively
Separator image1920 × 400pxQ7580KBWide and short. Decorative — can compress harder.
Background image1920 × 1080pxQ70120KBWill be overlaid with content — compress hard
Product gallery (main)800 × 800pxQ8580KBSquare. Highest quality — customer is evaluating product
Product gallery (additional)800 × 800pxQ8060KBSquare. Slightly lower — supporting shots
Product card / thumbnail600 × 600pxQ7540KBSquare. Shown in grid — many load at once
Feature / section image800 × 600pxQ8060KB4:3 ratio. Pairs with text column.
Avatar / person photo400 × 400pxQ8030KBSquare. Face centred. Compress moderately.
Open Graph image1200 × 630pxQ8080KBUsed for social sharing previews — keep sharp
Pattern / textureTile sizeQ7020KBRepeating tile — tiny file, repeated by CSS
Blog post thumbnail800 × 450pxQ7550KB16:9 ratio for blog listings

7.3  How to Export WebP — Use Squoosh

Squoosh is the primary tool for all manual compression at IMA AI. It is free, runs in the browser, and requires no installation. Go to squoosh.app. Squoosh processes everything locally — your images are never uploaded to any server.

1Open SquooshGo to squoosh.app in any browser — no login, no install
2UploadDrag and drop the image file onto the page, or click to browse
3Select formatClick the format dropdown on the RIGHT panel — choose WebP
4Set qualityDrag the Quality slider to the correct Q value for your image type (see table above)
5Check visuallyUse the centre slider to compare original vs compressed — check for blur or artefacts
6Check file sizeFile size shows below the image — confirm it is within the max size for the image type
7Resize if neededClick Edit → Resize — enter the correct dimensions for your image type before downloading
8DownloadClick the Download button (bottom right) — file saves as .webp automatically
9RenameRename the downloaded file immediately using the correct naming standard

Bulk conversion tools (10+ images)

ToolBest forCommand / method
Squoosh (squoosh.app)Standard tool — all manual one-off conversionsBrowser — no command needed
Sharp (Node.js)Automated bulk conversion in build pipelinesharp('in.jpg').resize(1920,900).webp({quality:80}).toFile('out.webp')
ImageMagick (CLI)Bulk terminal conversionconvert input.jpg -quality 80 -define webp:lossless=false output.webp
Figma exportExporting design assets directly from FigmaSelect frame → Export → WebP → set quality
PhotoshopPhoto retouching workflowFile → Export → Export As → WebP → set quality
Section 8

SVG Icon Naming

SVG icons stored in /icons/ follow a simplified naming convention — no page prefix needed as icons are shared across pages.

File name patternUseExample
icon-[name].svgSingle-colour UI iconicon-cart.svg, icon-user.svg, icon-search.svg
icon-[name]-filled.svgFilled variant of an iconicon-heart-filled.svg
icon-[name]-outline.svgOutline variant of an iconicon-heart-outline.svg
icon-social-[platform].svgSocial media iconicon-social-instagram.svg, icon-social-tiktok.svg
icon-payment-[provider].svgPayment method logoicon-payment-fpx.svg, icon-payment-visa.svg
icon-flag-[country].svgCountry flag iconicon-flag-my.svg, icon-flag-sg.svg
Section 9

What Not To Do

Common mistakes to avoid. Every example below has been seen in real projects.

Wrong ✗Right ✓Rule broken
Hero Image Final v3 USE THIS.jpgindex-hero-1.webpSpaces, uppercase, JPG, no page prefix, version in name
IMG_20240312_093412.jpgabout-ceo-avatar-1.webpCamera auto-name — meaningless, wrong format
hero_banner.jpgindex-hero-1.webpUnderscore, JPG, no page prefix
HomepageBanner.jpgindex-hero-1.webpCamelCase, JPG, no type code
photo1.jpg, photo2.jpgproduct-baju-kurung-moden-gallery-1.webpNo page, no product name, wrong format
logo-FINAL.PNGglobal-logo-1.svgUppercase, PNG instead of SVG
separator-section2.jpgindex-sep-2.webpVerbose, JPG — use type code and WebP
bg_texture_dark.jpgglobal-pattern-1.webpUnderscore, JPG, no page prefix
about-avatar-ceo.webpabout-ceo-avatar-1.webpWrong order — descriptor must come before type
index-bg-who-we-are-1.webpindex-who-we-are-bg-1.webpWrong order — section/descriptor first, then type
Section 10

Code File Naming

For Next.js projects — pages, components, and utilities follow these conventions.

10.1  Pages (App Router — /app)

FileConventionExample path
page.tsxEvery route segment has a page.tsx/app/page.tsx (homepage)
layout.tsxShared layout wrapper for a segment/app/layout.tsx (root layout)
loading.tsxLoading UI for a segment/app/collection/loading.tsx
error.tsxError boundary for a segment/app/product/error.tsx
not-found.tsx404 page/app/not-found.tsx

10.2  Components (/components)

ConventionPatternExample
PascalCase filenamesComponentName.tsxHeroSection.tsx, ProductCard.tsx
Grouped by feature/components/[feature]/ComponentName.tsx/components/product/ProductGallery.tsx
Shared UI components/components/ui/ComponentName.tsx/components/ui/Button.tsx
Layout components/components/layout/ComponentName.tsx/components/layout/Navbar.tsx

10.3  Utilities, Hooks & Types

TypeConventionExample
Utility functionscamelCase.ts in /lib/lib/formatPrice.ts, /lib/getOrders.ts
Custom hooksuseCamelCase.ts in /hooks/hooks/useCart.ts, /hooks/useIdentity.ts
TypeScript typescamelCase.ts in /types/types/order.ts, /types/product.ts
API routes/app/api/[route]/route.ts/app/api/checkout/route.ts
ConstantsSCREAMING_SNAKE_CASE in /constants/constants/PAYMENT_METHODS.ts
Section 11

Quick Reference Cheat Sheet

The most commonly needed file names at a glance.

ScenarioFile name
Homepage hero imageindex-hero-1.webp
Homepage hero videoindex-hero-1.mp4
Homepage first separatorindex-sep-1.webp
Homepage second separatorindex-sep-2.webp
Homepage — Who We Are section image 1index-who-we-are-img-1.webp
Homepage — Who We Are backgroundindex-who-we-are-bg-1.webp
Homepage OG image for social sharingindex-og-1.webp
About hero imageabout-hero-1.webp
About — CEO photoabout-ceo-avatar-1.webp
About — team group photoabout-team-img-1.webp
About — brand story image 1about-story-img-1.webp
About — values section backgroundabout-values-bg-1.webp
Product main gallery photoproduct-baju-kurung-moden-gallery-1.webp
Product third gallery photo (3rd angle)product-baju-kurung-moden-gallery-3.webp
Product card thumbnailproduct-baju-kurung-moden-card-1.webp
Product feature icon (free shipping)icon-free-shipping.svg
Product demo videoproduct-baju-kurung-moden-demo-1.mp4
Service hero imageservice-web-design-hero-1.webp
Service process section imageservice-web-design-process-img-1.webp
Service card thumbnailservice-web-design-card-1.webp
Service demo videoservice-ai-chatbot-demo-1.mp4
FAQ page hero imagefaq-hero-1.webp
Pricing page hero imagepricing-hero-1.webp
Team page — staff phototeam-ahmad-avatar-1.webp
Portfolio listing heroportfolio-hero-1.webp
Case study hero imagecase-bzubzu-hero-1.webp
Campaign landing herolanding-raya-hero-1.webp
Promo / sale page bannerpromo-12-12-hero-1.webp
Contact page hero imagecontact-hero-1.webp
Blog listing hero imageblog-hero-1.webp
Blog post thumbnailblog-post-thumb-1.webp
Platform product overview heroplatform-id-hero-1.webp
Platform CA service heroplatform-ca-livestream-hero-1.webp
Articles listing hero imagearticles-hero-1.webp
Article page hero imagearticle-[slug]-hero-1.webp
Article card thumbnailarticle-[slug]-card-1.webp
Main logo (SVG)global-logo-1.svg
White logo (for dark backgrounds)global-logo-white-1.svg
Favicon (browser tab)global-favicon.ico
Default OG fallback imageglobal-og-default-1.webp
Cart icon SVGicon-cart.svg
IG carousel card (English)social-[post-slug]-gallery-en-1.webp
RedNote carousel card (Chinese)social-[post-slug]-gallery-zh-1.webp
Instagram social icon SVGicon-social-instagram.svg
FPX payment icon SVGicon-payment-fpx.svg
Downloadable privacy policyglobal-privacy-policy-1.pdf

Questions about the standard?

Reach the IMA AI team directly.