Site inspiration & templates / Creative-work gallery
Wellmade
Compare polished creative work across UI, branding and product presentation.
Understand the resource
What it is.
Wellmade is a visual gallery of creative work organized into categories such as app icons, UI, branding, websites and launch videos. Public category pages support browsing, while save controls and X sign-in introduce separate account workflows that were not used here.
When it is useful
You need examples that show how visual identity carries across a product and its launch materials.
A proposed application
Put it to work.
This example illustrates a possible use. The proposed workflow and expected result are separate from the bounded checks recorded below.
Try this
Browse the UI and app-icon categories, choose two useful references, and explain the hierarchy or recognition problem each helps solve.
Result to aim for
A focused visual brief with specific observations and original-source checks.
Before you start
What you need.
- A browser for public browsing.
- Original assets and item-level permission checks when turning inspiration into finished work.
The practical boundaries
What to watch for.
- Gallery inclusion does not establish commercial reuse rights.
- Saving and account data handling were not tested; the public browse result does not cover those features.
Review record
What we could establish.
- The public UI category opened successfully and rendered image and video examples. Save, submission and X sign-in controls were left unused.
The source-review notes describe documentation and identity. The account-free evaluation below records exactly which public interaction or local fixture was checked, what happened, and what remains untested.
Check current access, terms, licensing and data handling before using a resource with your own material.
Runtime and security evaluation
What the evaluation covers.
The UI category opened with visual examples in a fresh browser. Public browsing works in this sample; account and submission features remain untested.
Methods: Public HTTP response · Public browser sample · Source review. A completed check covers the stated sample; it is not a safety certification.
- Target
- https://wellmade.fyi/
- Version or capture
- Unversioned public page observed 2026-10-19
- Integrity scope
- SHA-256 6cdd51d14dee65c93c1c855766997bb2eab6e69d8ab38151c576040fed3d4a12 of one initial HTML response (10423 bytes). This does not fingerprint the entire application or its dependencies.
Test conditions
- Windows; Chrome 155.0.8059.82 headless via Playwright, fresh isolated contexts with a 1365 × 900 viewport.
- Reduced motion requested. GET/HEAD requests allowed; other methods and WebSocket connections blocked.
- No owner browser profile, account, credentials, purchase, upload, private fixture or service write.
Individual checks and observations
Category navigation
passPublic browser sample: Select UI from the public gallery.
Observed: The browser reached /t/ui with the UI · Wellmade title; the sampled DOM contained 82 images and 14 videos.
Save and authentication
not-runPublic browser sample: Use save, submission or X sign-in controls.
Observed: These account-related controls were visible but not activated.
Security findings and boundaries
One public category path, response headers and passive request destinations.
Observed · info
Protective headers on sampled responses
The response included HSTS, frame-ancestors none, X-Frame-Options DENY and nosniff. These are useful response-level controls, not evidence about account authorization or stored data.
Practical advice · caution
Check the source before reuse
Follow the specific work back to its creator and establish permission before reusing visuals or branding.
Practical caveats
- Images and videos in a gallery do not show keyboard behavior or small-screen layout of the original product.
- A public browse pass does not cover saving or publishing work through an account.
What remains untested
- One category was sampled; no sign-in, save, submission or asset download.
- No full media, accessibility, permission or backend audit.
Security limits
- Passive public-page observations and the stated bounded sample only; no exploitation, authenticated authorization, backend, retention or comprehensive dependency audit.
- Request blocking changes application behavior; no secure/safe certification is implied.
Evaluation sources
Follow the evidence
Sources and further reading.
Keep exploring