Explore the weave.
Request the sample.
We gave the textile collection room for texture-led imagery and colourways, then built a planning route around a physical sample request.
The detail page helps the visitor narrow the direction rather than pretending to reproduce the material exactly.
Explore the work ↓- PROJECT TYPE
- Website design & front-end development
- DOMAIN
- Textile design and weaving studio
- DESIGN FOCUS
- Connecting textile browsing to a physical sample request
A screen cannot settle a material choice.
We kept intended use and sample preferences together in the enquiry. That gives the next step a purpose: examining a material beyond the screen. The textile records and imagery are illustrative, and the local planner does not dispatch a sample.
The pages we designed.
The build brings home, textile library, heath, build a sample request and request samples into one website.
Textile library
View the screen ↓Heath
View the screen ↓Build a sample request
View the screen ↓Request samples
View the screen ↓Project scope.
We designed and built 9 pages for this self-initiated project, including the layouts, responsive behaviour and front-end interactions. The interface uses sample business records.
The shortlist and planning notes stay within the browser session. Enquiries produce a local preview; no request, payment or booking is sent.
The gallery shows our rendered pages with identifying details masked.
A closer look.
Page by page.
Start with the home page, then explore the details. These are screenshots of the original website, with names, contact details and identifying information blurred for privacy.
5 views Select any view to exploreHave a similar project?
Let’s discuss the work.
Tell us what your customers or team need to do. We can help define the pages, records and interactions around that task.




