Projects are the strongest signal in Archade. They are the “atomic unit of work” that connects people, companies, products, and tools.

Where it lives

• Create project: /create
• Manage projects: /dashboard/profile?tab=projects
• Edit a project: /dashboard/profile?tab=projects → open the project
• Manage contributors: the same Projects tab → open the project → Credits
• Public project pages: /p/[typology]/[category]/[slug]

Create / Edit / Delete (CRUD)

Create (recommended workflow)

1. Create the project: /create
2. Add media (images/videos)
3. Fill: title, description, location, typology/category, year (if known)
4. Add credits (contributors) with roles
5. (Optional) Link products used and software used

Edit

Update the project and its relationships:

• core details: /dashboard/profile?tab=projects → open the project
• credits/team: the same editor → Credits

Delete

Project deletion or unpublishing depends on visibility rules and current product state. If deletion isn’t available, set visibility to a safer mode (unlisted/private) and contact support if needed.

Credits (contributors) — how to do it right

Credits are the fastest path to trust.

Best practice:

• add real people (platform users) when possible
• specify role (Lead Architect, PM, Visualization, etc.)
• add contribution notes (short, factual)

When contributors accept/verify credits, the project becomes much stronger in the graph.

Linking products to projects (brands + proof)

If a product was used in a project, link it. This creates:

• better discovery (“projects using X”)
• stronger vendor credibility (“proof, not ads”)

See products: /help/products

Project visibility

Choose visibility based on what you want:

• public: indexed + discoverable
• unlisted: shareable link, less discoverable
• private: for drafts and internal work

How projects power the graph

Projects connect:

• users (credits)
• companies (creator + team context)
• products (materials/variants used)
• software (tools used)

Deep dive: /help/attribution-graph