When you are building a personal website and the project is still in progress, files and pages pile up fast. Without a simple labeling system, you may open a file and not know whether it contains your latest thinking or an abandoned idea from two weeks ago. A straightforward approach is to add a short status tag to each file name or document title, such as "draft," "in review," or "on hold." The tag should reflect what you actually intend to do next with that piece, not just how old it is.

One common problem is that people use version numbers like v1, v2, v3 without noting what changed between them. If you come back after a break, the numbers alone tell you nothing. A more useful practice is to pair the version number with a brief note, either in the file name or in a short comment at the top of the document, describing the main difference from the previous version. For example, "draft-v3-nav-rework" tells you both the sequence and what that iteration focused on.

For pages or sections that you have started but decided not to finish right now, avoid simply leaving them unlabeled or burying them in a folder called "misc." Give them a label that captures why they are paused, such as "on hold – waiting for photos" or "on hold – needs content rewrite." This way, when you are ready to resume, you can quickly see what each piece is blocked on and whether the blocker still exists.

It also helps to keep a single short note, separate from the files themselves, that lists what is currently in progress and what is parked. This note does not need to be detailed. A few lines recording which sections are active, which are waiting on something, and what your next step is will save you from reopening every file to figure out where you left off. Update it only when something actually changes status, not on a fixed schedule.

Finally, resist the urge to delete drafts that feel outdated. Instead, move them to a clearly labeled archive folder. You may find that a paragraph or a layout idea you set aside fits better later. The key is that archived material is separated from active material so you do not accidentally publish or build on something you already decided to replace.