Textile Trading Group / Website delivery showcase
A more considered
digital showroom.
The visual experience and customer content,
built around the way a rug becomes a room.
Delivered frontend & content · September 2026
01 / Creative direction
Same character.
A clearer expression.
TTG’s identity carries through: handcrafted texture, considered interiors and a confident editorial voice.
Original mark. Warm ivory and ink. Restrained bronze. Playfair Display paired with DM Sans.
02 / The opening
A room begins
with a rug.
One clear statement. An editorial room scene. A direct invitation to explore collections, feel the materials and shape a project.
Open the homepage ↗03 / Collection discovery
Find a point
of view.
A considered edit of 21 rugs, with search, filters and sorting that make construction, fiber and color easier to compare.
Current scope: the 21-piece Collection Edit—not the full supplier catalog.
Explore the collection ↗04 / Product storytelling
Every rug has
its own story.
Individual narratives, authentic imagery, room guidance and care descriptions turn a product page into a more useful decision.
05 / Custom & trade
Your vision.
Our common thread.
Dedicated pages bring palette, proportions and professional project needs into the conversation.
06 / Useful content
Help customers
picture the possibility.
A consistent voice across craft, sourcing, inspiration, journal stories, sizing, care and common questions.
07 / The customer path
Keep
the thread.
Discover a piece. Choose intended dimensions. Save a selection. Prepare a project request with the details already together.
The request experience is complete as a frontend. Details remain in the browser; nothing is sent to TTG yet.
Open saved selection ↗08 / Feedback incorporated
Less distraction.
More purpose.
A simpler navigation and a clearer finish: after preparing a request, customers can return to the collection, their selection or contact information.
Customer-focused actions, with a clear local-only notice at the point of use.
09 / Mobile experience
Considered
at every width.
Readable content, deliberate image composition and practical customer actions—not a desktop page squeezed smaller.
No horizontal overflow in the recorded 165 route/viewport checks. Chromium emulation; not physical-device certification.
10 / Delivered scope
A complete content layer.
A coherent customer experience.
Fixed routes
34 pages and states, plus 21 individual product pages.
Request frontends
Quote, sample, catalog, contact, consultation and trade.
Consistent voice
Brand, product, editorial and customer guidance brought together.
Version complete: the approved visual frontend and rewritten content. Customer requests and illustrative checkout are not connected business operations.
11 / Evidence behind the finish
Designed with intention.
Checked in detail.
The hosted release was also checked across 55 desktop and 55 mobile routes, 90 unique anchors and 34 query variants. Counts describe separate checks, not a performance or accessibility score.
See the complete visual review and methodology ↗12 / Open evidence
The details,
in full.
Every route. Desktop and mobile. Full-scroll images, customer-state evidence and the measurements behind the release.
Use the page selector, compare widths, open full-resolution images and inspect the complete results.
Pixel-level review means real browser rendering and measurable layout checks—not a claim of manually reviewing every physical pixel.
Open complete visual review ↗13 / The next phase
Connect
the experience.
Feeding Frenzy integration follows the completed frontend and content.
Agree the handoff
Confirm request owners, routing and approved commercial rules.
Connect the flow
Link the approved customer paths to the business systems.
Prove the receipt
Validate accepted end-to-end delivery before activating real operations.
Today: local-only requests and illustrative checkout. No real email, payment, order or stock reservation is claimed.
Textile Trading Group / Version complete
A considered foundation.
A clearer next step.
Website frontend and content delivered.
Feeding Frenzy integration next.
Review questions: Which collections and projects should lead? Who will own incoming requests in the next phase?