Organizing a Personal Project Website with Three Project Logs

When you are working on several personal creative projects at once, keeping their progress notes separate and clear becomes a practical organizational challenge. This article uses three hypothetical projects to explore how structured project logs can help you track where each one stands without mixing up decisions, drafts, and next steps.

Three Hypothetical Projects at Different Stages

Suppose you are managing three personal creative projects simultaneously. The first is a collection of five short stories, currently in the drafting stage for the third piece. The second is a photo essay series about neighborhood markets, where you have shot most of the images but have not yet settled on a final sequence. The third is a small web tool that converts color palettes between formats, where the core logic works but the interface layout remains unfinished. Each project sits at a different point in its own development, and each has a different kind of next action waiting for you.

For the short story collection, your current goal might be to finish a rough draft of the third story by the end of the month. Your written progress so far includes two completed drafts and a partial outline for the fourth piece. Your undecided question is whether the fourth story should share a character with the second one or stand alone. Your next-step note says to write the opening scene of story three before revisiting the structure question.

For the photo essay, your current goal is to select and order twelve images from a pool of roughly forty. Your written progress includes a contact sheet with rough ratings and two candidate sequences you sketched last week. Your undecided question is whether to include one wide establishing shot at the beginning or start directly with a close-up of a vendor's hands. Your next-step note says to print the two sequences at small size and compare them side by side.

Recording by Project Versus Recording by Phase

One common approach is to keep all notes for a single project together in one log. Under this arrangement, the short story collection would have its own file or section containing every entry from initial idea through current drafting notes. The photo essay would have a separate log with its own timeline. This makes it straightforward to review where one project stands without scanning unrelated material. The trade-off is that when you want to compare progress across projects or plan a week of mixed work, you must open each log separately and mentally assemble an overview.

The alternative is to organize notes by phase or activity type. In this arrangement, all drafting notes for every project live in one place, all selection or review notes live in another, and all technical implementation notes live in a third. This can be useful if you think in terms of what kind of work you want to do on a given day rather than which project you want to advance. The trade-off is that each project's full history becomes scattered, and reconstructing the sequence of decisions for one project requires searching across multiple sections.

In this hypothetical scenario, the by-project approach fits better because the three projects involve genuinely different activities and different kinds of decisions. A drafting note for a short story has little in common with a sequencing decision for a photo essay, so grouping them by phase would not create meaningful comparisons. However, if you were working on three projects that all involved the same type of activity at similar stages, a phase-based arrangement might reveal useful patterns. The choice depends on whether your projects share enough structure to benefit from cross-project comparison within a single phase.

Preparing a Public Address for Your Project Logs

Once your three project logs have a consistent structure and each entry stays within its own scope, you may want to share them with collaborators or publish them for a wider audience. If you plan to make these logs accessible at a public web address, one optional preparatory step is to secure a domain name. This is not required to complete the organizing work described above, nor does registering a domain by itself make your content available online. It simply reserves a custom address that you can later point to wherever you choose to host your pages. The table below compares the initial availability-check step at two registrars.

¹²

Writing Entries That Stay Within One Project's Scope

A frequent source of confusion in multi-project notes is an entry that refers to two projects at once or that describes a decision in terms that could apply to either. For example, writing a note that says finish the opening before choosing the layout is ambiguous if both the short story collection and the web tool have openings and layouts. A clearer entry names the specific project and the specific element: finish the opening scene of short story three before deciding whether to revise the story collection's table of contents.

Check each entry you write for whether it would still make sense if you read it three weeks later without remembering the context. If the entry says something like move the second item to the top, ask yourself which project and which list you meant. Rewriting it as move the market entrance photo to the first position in photo essay sequence B removes the ambiguity. This habit takes only a few extra seconds per entry but prevents the slow accumulation of notes that become impossible to interpret.

Another useful practice is to give each undecided question its own entry rather than embedding it inside a progress note. When you write finished editing image seven, still unsure about the wide shot at the beginning, the decision is easy to overlook because it is attached to a completed action. Separating it into its own entry, such as undecided: whether to open the photo essay with the wide establishing shot or the vendor hands close-up, makes the open question visible the next time you review the project log.

Building a Consistent Entry Structure for Each Log

Record each project log entry with four fields: current goal, written progress, undecided questions, and next step. The current goal states what you are trying to accomplish in the near term for this project, phrased as a concrete outcome rather than a vague intention. Written progress lists what you have actually completed since the last entry, using specific references to the work itself. Undecided questions captures anything you have noticed but not yet resolved. The next step names the single action you plan to take before writing the next entry.

Write the current goal as a sentence that includes a measurable or observable endpoint. Instead of a goal like work on the web tool interface, write a goal like place the color preview panel above the format selector and verify it displays correctly at a minimum window width of 640 pixels. This phrasing tells you exactly when the goal is met and prevents the entry from remaining open indefinitely because you are unsure whether enough progress counts.

List undecided questions with enough detail that you can evaluate them without reopening the original work. For the short story collection, rather than writing just story structure question, write whether the fourth story should share the character Elena from story two or introduce a new perspective. This level of specificity means that when you return to the question days or weeks later, you can think about it directly rather than spending time reconstructing what you meant.

Step 1

Open the log file or section for the project you are about to work on and read the most recent entry from top to bottom, noting the current goal and any undecided questions.

Step 2

Write a new entry below the previous one, starting with the current goal field. State the goal as a specific outcome with an observable endpoint, then fill in written progress with what you have completed since the last entry.

Step 3

Add any undecided questions as separate lines within the entry, each phrased with enough context that the question is self-contained. End the entry with a next-step note naming the single action you will take before writing again.

Handling Undecided Questions Without Stalling Progress

Undecided questions are a natural part of any creative project, and recording them honestly prevents false confidence in your log. When you note that you have not yet chosen between two options, you preserve the actual state of the project rather than pretending a decision has been made. This matters because the next time you open the log, you will see immediately that the question is still open and can allocate time or attention to it rather than assuming it was already resolved.

One practical approach is to set a condition for when you will revisit an undecided question rather than leaving it open indefinitely. For example, you might write that you will decide between the two photo essay sequences after printing them and viewing them in daylight, or that you will decide whether story four shares a character with story two after finishing the draft of story three. Attaching a condition to the question gives you a clear trigger for returning to it and prevents the question from floating through multiple entries without resolution.

If a question remains undecided across several entries, consider whether it is actually blocking your progress or whether you are continuing to work on other aspects of the project without needing the answer. In the web tool example, the interface layout question might not prevent you from refining the color conversion logic. Noting this explicitly in the log, such as layout decision does not block current work on conversion accuracy, helps you avoid the feeling that an open question is holding up the entire project when in fact you can continue advancing other parts.

Frequently asked questions

Should I use the same four fields for every project log entry even when a project is in a very early or very late stage?

You can keep the same four fields throughout, but their content will naturally shift. In an early stage, written progress might be very brief and undecided questions might dominate. In a late stage, undecided questions might shrink to one or two final choices while written progress becomes a longer list. The structure stays consistent so you can scan any entry quickly regardless of where the project stands.

What should I do when I realize an earlier entry contains an ambiguous note that I can no longer interpret?

Add a new entry acknowledging that the earlier note is unclear and write down whatever you can reconstruct about what you might have meant. If you cannot reconstruct it, note that explicitly and move forward with your current understanding. The log is a working record, not a perfect archive, so marking an entry as unclear is more honest and more useful than deleting it or guessing.

Is it better to update all three project logs on the same day or only update a log when I actually work on that project?

Updating a log only when you work on that project keeps the entries tied to real activity and avoids writing filler notes just to maintain a schedule. However, if you find that long gaps make it hard to remember what you were doing, a brief check-in entry noting that no work happened and restating the current goal can help you resume more easily. The choice depends on whether your memory degrades enough over gaps to justify the extra effort.