High-end frontend
Core navigation remains focused: product catalog, supplier trust, buyer education, sourcing library, and RFQ. The homepage should not carry thousands of links.
Sooye Studio keeps the public brand experience clean while organizing a deeper B2B knowledge base underneath. The library is not a link dump. It is a governed entry point for supplier verification, RFQ preparation, samples, documentation, packaging, quality checks, buyer workflows, and product-family research.
Core navigation remains focused: product catalog, supplier trust, buyer education, sourcing library, and RFQ. The homepage should not carry thousands of links.
Guides, checklists, templates, buyer workflows, and future verified SKU pages are organized through hubs, clusters, sitemap, and JSON indexes.
Every link should have a buyer reason, a topical reason, or a machine-index reason. Random links, footer link dumps, and fake external links are blocked.
Future scale should live in governed clusters. The visible page stays selective; deeper inventory is handled through library pages, sitemap index, site-index.json, structured-data-index.json, and future verified product data.
Proof-safe supplier checking before buyers rely on claims.
Templates and guides that turn product interest into a useful inquiry.
Model-specific questions for documents, labels, plug standards, and destination markets.
Sample-first paths for verifying product fit, finish, packaging, and bulk-order readiness.
Packaging, labels, private label, and buyer-channel requirements.
Product-family entry points before verified SKU data is published.
Different buyer groups need different sourcing questions.
Project, regional, hotel, fit-out, and market-specific sourcing paths.
Proof-safe supplier checking before buyers rely on claims. This library shows curated entry points first; deeper content can live in sitemap, JSON index, and cluster pages without crowding the brand frontend.
Templates and guides that turn product interest into a useful inquiry. This library shows curated entry points first; deeper content can live in sitemap, JSON index, and cluster pages without crowding the brand frontend.
Model-specific questions for documents, labels, plug standards, and destination markets. This library shows curated entry points first; deeper content can live in sitemap, JSON index, and cluster pages without crowding the brand frontend.
Sample-first paths for verifying product fit, finish, packaging, and bulk-order readiness. This library shows curated entry points first; deeper content can live in sitemap, JSON index, and cluster pages without crowding the brand frontend.
Packaging, labels, private label, and buyer-channel requirements. This library shows curated entry points first; deeper content can live in sitemap, JSON index, and cluster pages without crowding the brand frontend.
Product-family entry points before verified SKU data is published. This library shows curated entry points first; deeper content can live in sitemap, JSON index, and cluster pages without crowding the brand frontend.
Different buyer groups need different sourcing questions. This library shows curated entry points first; deeper content can live in sitemap, JSON index, and cluster pages without crowding the brand frontend.
Project, regional, hotel, fit-out, and market-specific sourcing paths. This library shows curated entry points first; deeper content can live in sitemap, JSON index, and cluster pages without crowding the brand frontend.
Curated hub and cluster links for real buyers. The page remains readable and premium.
link-governance.json and sourcing-library-index.json document the content model and future link rules.
sitemap.xml, llms.txt, site-index.json, and structured-data-index.json expose the architecture to search and AI systems.
Proof-safe rule: the library organizes sourcing education. It does not publish unverified SKU parameters, certificates, load ratings, MOQ, factory scale, customer cases, or test data.