Personal website planning: How can personal contributions be distinguished from a collaborating team’s results?

If you are building a personal website and working with others—a designer, a developer, a copywriter, or even a friend who helps with photos—it can get blurry fast what you actually did versus what someone else produced. This matters most when you later want to show the site as evidence of your own skills, or when you need to explain your role to a potential employer or client. The problem is easier to prevent than to untangle after the fact, so the most useful step is one you take before the collaboration begins.

Before anyone starts working, write down which parts of the site you will personally create or decide. This does not need to be a formal contract. A short note saying "I will write all page text and choose the layout direction; the designer will handle color palette and typography; the developer will handle hosting setup and responsive behavior" gives you a reference point later. If the scope shifts during the project, update that note with a date so you can trace when and why responsibilities changed.

During the project, keep dated drafts of the things you produce yourself. If you write the about page, save each version you wrote before handing it to someone for editing. If you make layout decisions, note the date and the reasoning. These drafts do not need to be polished or public; they are evidence you can point to if someone later asks what your specific input was. Version history in a tool like a document editor or a content management system can serve this purpose automatically if you remember to check it.

When the site is live, a simple credits or acknowledgments section can clarify the division without drawing attention away from your work. Listing roles by name—such as "design by" or "development support by"—tells visitors and reviewers which parts came from collaborators. This is a small addition, but it protects you from the awkward situation of someone assuming you did everything or, conversely, assuming you did nothing.

If you are already past the planning stage and trying to sort out contributions retroactively, start by asking each collaborator to confirm what they handled. Compare their answers against your own memory and any files you still have. Where gaps appear, note them honestly rather than filling them in with assumptions. The goal is not to claim more than you did but to be able to describe your actual role clearly and without overstating or underselling it.