Loading
Uploading a design project is more than posting a few renders. This guide explains how to fill in the project title, space type, design goal, summary, highlights, areas for improvement, and complete the cover upload and authorization confirmation, making your project a reviewable and forkable design asset.
Use this when you have a completed or in-progress design proposal and want to showcase it to the community, receive reviews, or allow others to create forked improvements based on your work. Suitable scenarios include: - Original design work seeking peer feedback. - Academic exercises to demonstrate design thinking and receive guidance. - Client-commissioned projects that are publicly shareable, with client authorization. - Improved versions based on public projects (forked improvements). If you just want to post a space problem and wait for proposals, use "Publish a Design Request" instead.
Before uploading a design project, prepare the following: 1. Basic project info: title, project stage (concept/developed design/built project/academic exercise/forked improvement), space type (residential apartment, commercial, book cafe, office, etc.), area, city. 2. Author info: author or team name, contact email. Contact email is not publicly displayed by default. 3. Project source: original work, academic exercise, client commission (publicly shareable), based on public project, etc. For client-commissioned projects, ensure you have client authorization. 4. Design content: design goal (what problem this project solves), summary (design logic, key circulation, spatial strategy), highlights (one per line), areas for improvement (what you'd like the community to help optimize). 5. Project cover: you can upload one project cover image. Supports JPG, PNG, WEBP, max 5MB per image. 6. License: public projects are currently displayed under CC BY-SA 4.0. This form no longer stores separate "allow forks" or "license choice" fields. Important: if images contain phone numbers, unit numbers, contracts, invoices, ID cards, license plates, or client names, crop, blur, or replace them first. Client-commissioned projects must have client private and commercially sensitive information removed.
The upload project page has five steps: Basic Information, Author and Source, Design Content, Collaboration and License, Images and Publishing Confirmation. Step 1 "Basic Information": - Title (required): e.g. "89㎡ family-of-three storage renovation", "Community book cafe counter flow optimization". - Project Stage: select from dropdown. Choose "built project" for completed client work, "academic exercise" for student work. - Space Type (required): e.g. "residential apartment", "commercial", "book cafe", "office". - Area: e.g. "89㎡". - City: e.g. "Shanghai". Step 2 "Author and Source": - Author or team name: e.g. "Zhang Design Studio". - Contact email: for platform review and communication only, not publicly displayed. - Project source: select from dropdown. Note "client commission (publicly shareable)" means you have client authorization. - Accept collaboration inquiries: yes or no. Step 3 "Design Content": - Design goal (required): the core problem this project solves. E.g. "achieve efficient storage and smooth circulation for a family of three within 89㎡". - Summary (required): briefly describe design logic, key circulation, and spatial strategy. E.g. "replaced the wall between kitchen and dining with a semi-open bar counter, adding prep space and interaction; added 600mm deep storage cabinet on the right side of the entry, integrating shoe cabinet, coat hanging, and seating". - Highlights: one per line, e.g. "semi-open kitchen increases family interaction", "children's room uses adaptable layout". - Areas for improvement: what you'd like the community to help optimize, e.g. "the transition between living room and balcony could be better", "master bedroom storage can be further optimized". Step 4 "Collaboration and License": - Public projects are currently displayed under CC BY-SA 4.0 and support structured review and forks. - This form no longer stores separate "allow forks" or "license dropdown" fields; authorization is subject to the confirmation completed at publishing time. Step 5 "Images and Publishing Confirmation": - Upload project cover: via file upload, supports JPG, PNG, WEBP, max 5MB per image. - The cover enters platform review after submission and is shown on the public project page only after approval. Covers that are not reviewed, rejected, or blocked are not public; the project page shows a default cover image. - Before publishing you only need to complete the authorization confirmation shown on the current page; authorization is governed by the authorization confirmation displayed on the page.
After clicking submit, the system sends your design project to the backend and enters the content review process. Upon successful submission, the page displays a "Submitted for review" screen listing your title, space type, area, city, author name, design goal, and summary. After submission, confirm the following: 1. Are the title and space type accurate? 2. Does the design goal clearly state the core problem being solved? 3. Does the summary include key circulation and spatial strategy, not just visual description? 4. Have you completed the authorization confirmation shown on the page? 5. Have private information been removed from uploaded images? You can check your submission status on your account page (/zh/account or /en/account). Once approved, the project will be displayed on the public projects page and support structured reviews and forks. Note: project covers are uploaded as files and enter platform review after submission; they are shown on the public project page only after approval. Covers that are not reviewed, rejected, or blocked are not public; the project page shows a default cover image.
Here are the most common mistakes when uploading a design project: 1. Only posting images without design description: uploading lots of renders but leaving design goal, summary, and highlights empty or with just a sentence or two. The core value of a project page is the design reasoning process — images are supplementary. 2. Client projects not de-identified: renders or floor plans containing client names, unit numbers, contract numbers, etc. Client-commissioned projects must be checked item by item before uploading. 3. Forgetting the authorization confirmation: not ticking the authorization confirmation box shown on the page before publishing prevents submission. Please read and confirm the "collaboration mode" (display only / open collaboration) note before submitting. 4. Cover upload issues: uploading an image larger than 5MB or in a format other than JPG/PNG/WEBP, or a cover that contains un-redacted client private information. Covers must pass platform review before being shown publicly. 5. Wrong project stage: selecting "concept" for a built project misleads reviewers about the project's maturity. 6. Areas for improvement left blank or written as "none": if you want meaningful feedback, suggest at least one or two aspects you're aware of but unsure how to improve. This guides more valuable reviews than leaving it blank. 7. Highlights written as advertising: writing "best design" or "top-tier proposal" instead of specifically describing what the design does well. Good highlight descriptions should be verifiable, e.g. "by changing the kitchen door direction, reduced walking distance from kitchen to dining from 8m to 3m".
Uploading a project means you confirm you have the right to publish this content or have obtained necessary authorization. If uploading a client-commissioned project, ensure the client has agreed to public display and licensed collaboration. Public projects are published under the "collaboration mode" you choose: - Display only: others can view and review your project, but cannot create forks from it on LynHub. - Open collaboration: others can create forks of this project on LynHub and continue improving it; fork derivatives also stay open collaboration. Historical authorizations users explicitly made before this rule took effect are not rewritten by this product change; history records serve existing authorization relationships and audit only, and new publications and subsequent platform operations uniformly apply the current "display only / open collaboration" product settings. If you discover unauthorized client private information in images, immediately delete the project or contact legal@lynhub.com.