How to publish well

• Upload projects you made, or projects you genuinely worked on as part of a team.
• For a team project, tick 'group project' and add every teammate. It appears on all of their profiles, which is fairer than one person taking the credit.
• If a tutor, fabricator or photographer contributed something substantial, say so in the description.
• Don't upload someone else's project, precedent images you didn't make, or renders you bought.

• A cover image does most of the work. Pick your strongest single drawing or render rather than a title slide.
• Upload the full presentation as a PDF. Every page gets rendered on the project page at full resolution, so a reader can zoom into your line work.
• Use the description for the thinking: the site, the brief, what you were testing, what you'd change.
• File it under the right course. That's what makes the gallery navigable by studio rather than a single endless feed.

Real sites have neighbours, clients and residents. If your project documents a real place, be careful with photographs of people, private addresses, and anything a client shared with you in confidence.

Nothing hateful, harassing, or explicit. Nothing that reveals another person's private information. Work that breaks this comes down.

Some schools have rules about publishing coursework before it is marked, and a few treat published work as a plagiarism risk for the people who see it. Check your programme handbook before posting anything from a live studio. When in doubt, wait until the module is marked.

If you find your work published by somebody else, or anything here that breaks these guidelines, contact us and it will be taken down while we look into it. Being able to prove authorship is usually easy with source files, so keep yours.