Weardrobe
street fashion website
Weardrobe is an online street fashion community for both novice and established bloggers that allows members to share their outfits and comment on others' photographs.
History
The concept originated in September 2004, when Weardrobe co-founders Suzanne Xie Rich Tong realized that there were no online applications available to organize clothing. To address the issue, their discussions led to the concept for Weardrobe, and the website officially went online in January 2008.
In 2009, Weardrobe was named one of 20 winners of Facebook's fbFund Competition for startups and nonprofit companies, and invited to participate in Facebook's Summer Incubator Program in Palo Alto, California. There, Xie and Tong worked on integrating Facebook Connect with the online fashion network expanding the feature set to Facebook-connected users through friend activity tracking.
In 2012, the founders entered a partnership with Urban Outfitters, where select styles would be sent to users who would then post their created outfit on the Weardrobe site.
On November 18, 2009, the community was acquired by Like.com. Subsequently, Like.com was acquired by Google on August 20, 2010 for a rumored price of $100,000.
Features
Weardrobe provides members with the opportunity to create their own user profiles and post photographs of themselves. Members can create and view a virtual representation of their real-life closet by manually tagging clothing in the images uploaded to the site.
Begin with the source’s own compact description: “Weardrobe” is street fashion website. The dossier treats that line as a proposition to test through Weardrobe, street and fashion, not as a finished interpretation.
Why this record matters
The phrase “street fashion website” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
The strongest evidence will usually combine a dated visual record with documents produced by the authority responsible for the place. The source revision retrieved here is dated Sep 22, 2026. The linked authority identifier is Q7978142. 2 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2004, 2008, 2009 and 2012.
Architectural summaries often privilege surviving fabric and can understate demolished phases, contested use or displaced communities. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “Weardrobe”, its source revision and the description used here.
- Expand the search: follow Weardrobe primary sources, Weardrobe archive and Weardrobe research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Weardrobe”?
- What physical evidence or contemporary plan supports the description?
- Which authority defined the place, boundary or structure at the relevant date?
Search terms from this dossier
This entry incorporates text from “Weardrobe” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.