使い方
実際のリクエストの公開、デザインプロジェクトのアップロード、提案の提出、構造化レビューとフォークへの参加、プロバイダー身元と協働記録の管理方法を学べます。
Publishing a design request is the starting point for collaboration on LynHub. This guide walks you through filling in the title, area, budget, city, home status, pain points, style preferences, and contact info, and explains what happens after submission.
詳細を読む →02Uploading 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.
詳細を読む →03A proposal is a complete design solution submitted for a design request. This guide explains how to fill in the proposal title, core design strategy, layout approach, circulation and storage, style and materials, budget strategy, risk reminders, and questions to clarify, making your proposal review-ready.
詳細を読む →04A structured review is not just "looks good" or "don't like it". This guide explains how to write evidence-based strengths, issues, and improvement suggestions around dimensions like circulation, storage, daylight, materials, budget, and construction risk, along with a score and fork directions.
詳細を読む →05A forked improvement creates an improved version based on an existing project. This guide explains how to choose a base version, fill in the improvement goal, specific changes, rationale, advantages, and new risks, and when to use a fork versus a structured review.
詳細を読む →06The version tree records the evolution path of a design proposal from the base version through structured reviews and forked improvements. This guide explains how to read the version tree, compare branches, understand change rationales and risks, and why you shouldn't judge versions by renders alone.
詳細を読む →07Essential rules to know before uploading content: what you can upload, what you shouldn't, authorization issues for client projects, handling private information in images, choosing a collaboration mode, and how to contact the platform about infringement or privacy concerns.
詳細を読む →08After logging into your LynHub account, you can publish design requests, upload design projects, submit proposals, participate in structured reviews, and create forked improvements. This guide explains how to log in, common failure reasons, and security reminders.
詳細を読む →09After signing up for a LynHub account, you can publish design requests, upload design projects, participate in reviews, and create forked improvements. This guide explains how to create an account with Google or an email verification code, common failure reasons, and security reminders.
詳細を読む →10The account page brings together sign-in details, submissions, saved items, cooperation records, provider identity, and request status management. This guide explains each area, sign-out, and common questions.
詳細を読む →11The star feature lets you bookmark design projects you're interested in, making them easy to view and manage on your account page. This guide explains how to star and unstar projects, where to view your starred list, and what starring does.
詳細を読む →12Learn how to use the LynHub measurement template to record room dimensions, label walls and openings, fill in utility points and load-bearing wall sources, helping designers understand your spatial conditions more accurately.
詳細を読む →13Cooperation can start in two ways: a provider applies to a requester's request, or a requester invites a provider. The intent enters a pending state for the other party to accept or decline in the account center.
詳細を読む →14After a cooperation is accepted, both parties separately confirm the service content, budget, deliverables, revision counts, and safety boundaries. Contact exchange can only be enabled after both confirm.
詳細を読む →15After the cooperation is accepted and both parties confirm the service scope, the requester can enable contact exchange. Once enabled, both parties can send phone, WeChat, or email details in the conversation.
詳細を読む →16Before a cooperation is accepted and the service scope is confirmed, messages containing phone, WeChat, or email details are blocked. This protects both parties and keeps cooperation traceable; it is not meant to block normal cooperation.
詳細を読む →17A requester can adopt a valuable proposal on the request detail page. Adoption records are shown publicly and count toward the provider's public credit.
詳細を読む →18Distinguishes "confirming the service scope" from "confirming a collaboration record": the former confirms content before cooperation, the latter records the fact of cooperation after it is reached or completed, for public credit.
詳細を読む →19Set up your service provider identity in the account center by choosing a role and accepted task types, and apply for certification. Taste contributors and professional providers each have their own boundaries.
詳細を読む →20As a taste contributor, you can offer style, soft furnishing, color, and aesthetic review suggestions on public projects.
詳細を読む →21LynHub provides cooperation records, contact-detail gating, and safety review, but does not hold funds, does not guarantee transactions, and does not take part in offline payments. Confirm the service scope and qualification boundaries before cooperating.
詳細を読む →22Three cooperation actions send email reminders: receiving a cooperation application or invitation, cooperation being accepted, and contact exchange being enabled. Emails are reminders only; for details, return to LynHub.
詳細を読む →23Items involving construction, safety, electrical, structural, fire, or gas work are high-risk. Online results serve only as design consultation or deepening reference. Before construction, a locally qualified professional must verify on site.
詳細を読む →これらのガイドで解決しない場合は、hello@lynhub.com までお問い合わせください。