Site inspiration & templates / Creative reference
Umanmade
Look beyond interface screens for a visual direction.
Understand the resource
What it is.
Umanmade describes a curated directory of human-made digital work across UI, motion, branding, illustration and related fields. It can help teams articulate an identity without treating every reference as an implementation example.
When it is useful
A brand-led project needs a broader creative vocabulary.
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
Compare a motion and a typography reference, then write the visual qualities that suit your own product.
Result to aim for
A cross-disciplinary moodboard with clear intent.
Before you start
What you need.
- A brand brief and owned assets for implementation.
The practical boundaries
What to watch for.
- A creative demonstration may not be a shipped or tested product interface.
- Credit the original creator and confirm rights before using any artwork or media.
Review record
What we could establish.
- Public primary documentation reviewed. See the account-free evaluation for executed checks and remaining workflow limits.
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 public creative-work feed loaded, and one gallery video played muted with its playback time advancing. This is a real media-preview result, not a test of the depicted interface.
Methods: Public HTTP response · Public browser sample. A completed check covers the stated sample; it is not a safety certification.
- Target
- https://www.umanmade.com/
- Version or capture
- Unversioned public page observed on 2026-10-19
- Integrity scope
- sha256:314386739d68c61387950fa71372cb21b53d3da7c78bc109408ff11ba8037386 — initial HTTP 200 response body only; not whole-application integrity.
Test conditions
- Chromium 155.0.8059.82, 1365×900 desktop viewport.
- Separate fresh, ephemeral browser contexts for entry and interaction; no owner profile, credentials or stored session.
- Only GET/HEAD network requests allowed; forms, downloads, WebSockets and service workers blocked. Some analytics endpoints also blocked.
- Short bounded waits; no mobile, assistive-technology, cross-browser or performance certification.
Individual checks and observations
Public HTTP response
passPublic HTTP response: Anonymous GET with redirects followed, response-body SHA-256 and selected security-header summaries; no cookies retained.
Observed: The standalone client received 200 at https://www.umanmade.com/. This establishes response delivery only.
Fresh browser entry
passPublic browser sample: Open the catalog URL in a new anonymous Chromium context with read-only network guards and no inherited profile.
Observed: The document returned 200 and identified itself as “Umanmade”. 88 image elements were present; no account was used.
Observed public sample or navigation
passPublic browser sample: Bring one gallery video into view, play it muted for 1.5 seconds, verify time advances, then pause.
Observed: The 670.328125×482 sample reached readyState 4; playback time advanced.
Security findings and boundaries
Passive inspection of the initial public document’s response headers and anonymous browser request hostnames, with read-only guards. No source exploitation, account access, dependency audit or private data.
Observed · info
Public response protections
The initial browser page used HTTPS. Its response included HSTS. No enforcing Content-Security-Policy response header was observed. This records the sampled response only; meta policies, backend authorization and exploit resistance were not assessed.
Observed · info
Request surface in the anonymous visit
Umanmade attempted requests to 6 additional hosts, including events.framer.com, framerusercontent.com, framer.com, app.framerstatic.com. Host counts include requests stopped by the test guard; they do not establish what data a service retained.
Practical advice · caution
Before using this reference
Follow creator attribution and ask whether a reference is a motion study or a shipped product before adapting its behavior.
Practical caveats
- Follow creator attribution and ask whether a reference is a motion study or a shipped product before adapting its behavior.
- A creative demonstration may not be a shipped or tested product interface.
What remains untested
- No likes, submissions or subscription requests were sent. Creator sites, reproduction rights and the functionality depicted in the video were not tested.
- Results describe the observed public pages and a bounded action, not the entire product or the referenced designs.
Security limits
- No authentication, authorization, tenant separation, data retention or backend handling was tested.
- Header presence or absence is a sampled configuration observation, not a security certification or an exploit finding.
- 2 blocked-request records were retained across entry and interaction checks. Guards may alter normal page behavior; the logs do not represent unrestricted traffic.
Evaluation sources
Follow the evidence
Sources and further reading.
Keep exploring