Contents
A project page can become another place where I collect everything I already collected elsewhere. The source list appears again, the plan is copied from a task note and several attractive headings wait for information. I would rather make an index do one small job: point me toward the work I can resume. It should tell me what this project is, which record is current and what question deserves attention next, without becoming a second version of every document it links to.
I will build an index for an imaginary short booklet about a neighborhood's public spaces. The project, contributors and records are constructed examples, not a claim that I have researched a particular neighborhood. Its materials include a draft, source notes, possible illustrations and a few decisions. I will use the index to distinguish these materials, then test it from the position of both a returning writer and a new reviewer. The same approach can be adapted to a much smaller personal project.
Give the page one reader and a present purpose
My first question is who opens the page and why. The writer returning after a break needs a current starting point. A reviewer needs the version being reviewed and the kind of response requested. A future reader of the completed booklet needs the final artifact and its context. One page can support more than one audience, but I would name the main one before adding sections. Otherwise I may build a convincing-looking dashboard that makes none of those arrivals especially easy.
For the demonstration, I would choose the returning writer as the main reader and give reviewers a clearly marked separate entry. The page's opening would explain that the booklet is still in development, that factual claims require their source checks and that the immediate task concerns one section. It would not announce a publication date or confirmed contributors unless those were actual project facts. The index can describe intent without making the project seem more complete or public than it is.
I would also define what the index is not responsible for storing. It is not the full research archive, the place to preserve every draft or a substitute for a decision record. Those boundaries allow it to remain short. If a new item has no role in navigation, it can stay in its appropriate collection. The index does not need to display every material to prove the material exists. A useful doorway can be selective because the rooms beyond it retain the detail.
List the few destinations that carry the work
I would begin with an inventory of destinations rather than a set of decorative categories. The project currently has a working draft, a source register, a decision about scope, an illustration register and an open-question note. Each destination has a reason to exist. I would describe that reason beside its link. Working draft tells me where to write; source register tells me where to inspect support; scope decision explains what the booklet deliberately leaves out. The names should not require a private vocabulary.
The destinations can be ordinary files or application notes. Obsidian documents internal links, including links to headings when a long note contains several distinct parts. Zotero collections can group relevant source items without creating another underlying record for each collection membership. Those are optional implementation choices. The navigation principle is independent: the index points to the location whose job is clear. I would avoid copying a whole source register into the index simply because one tool makes a link less visually prominent than a table.
An unexplained destination deserves scrutiny. If I have notes called general, other and important, I would open them to identify whether they hold work that needs naming. Sometimes the right response is a clearer title. Sometimes the material is mixed and needs a small local division. I would not reorganize the entire archive just to make the first index perfect. The immediate goal is an accurate map of this project's useful destinations, including honest notice when one of those destinations still needs attention.
Put the current state above the archive
The opening state should be brief enough to read before following a link. For the imaginary booklet, I would write that the first draft exists, its section about shared gardens still needs source inspection and no final illustration list is approved. That describes work rather than a vague percentage complete. A progress number may look precise while leaving the reader unable to identify what they can actually do. I would prefer three specific statements whose meaning a contributor can assess.
The current draft needs a clear identity. If the draft link opens an actively edited file, I would say so. A dated review copy belongs under a different label. Calling both latest invites a reviewer to annotate the wrong artifact or a writer to continue in a frozen copy. The index is useful precisely because it can explain the relationship in plain language. I would not ask the filename alone to communicate the whole editing process, especially once files are downloaded or forwarded.
Below the current work I would keep the small amount of history that helps interpret it. An earlier scope decision may matter because a familiar topic was intentionally excluded. Old draft links can live in a separate history section if people need them. They should not compete visually with the current starting point. A page becomes harder to use when every past destination looks equally active. The index can preserve access to history while showing which record supplies today's instruction.
Project: Public spaces booklet — illustrative working project Purpose: Prepare a short, sourced booklet with a limited selection of examples. Current state: Draft in development; garden section's sources still need inspection. Start writing: Working draft — edit the live text here. Inspect support: Source register — records what supports each factual passage. Understand the boundary: Scope decision — explains the selection and exclusions. Check illustrations: Image register — origin, permission and intended use; not a list of approved images yet. Next question: Does the garden passage distinguish a historical description from current access arrangements? Next action: Inspect the two source notes linked from that passage, then narrow the wording if needed. For a reviewer: Use the dated review copy; comment on clarity and source traceability, not final layout. History: Earlier drafts and superseded scope notes are reference, not the current editing location.
Write the next action where it belongs
I would keep the full question in its appropriate note, then summarize the next action on the index. In the example, the garden passage needs a check that distinguishes historical descriptions from current arrangements. The action is to inspect the relevant sources and revise the passage accordingly. It is not research gardens, which could expand without limit. The index should give enough context to begin and a link to the material needed, rather than require the returning writer to reconstruct the missing question.
This summary creates a maintenance choice. If the action changes, the index must change too. I would keep it short enough that updating it remains worthwhile. A large copied task list can drift from the actual task system, especially when several people edit independently. One current priority and a link to the canonical plan may be enough. I would resist making the index display every open item if doing so creates a second list whose status nobody reliably maintains.
An action can end in several ways. The source may support the narrow wording, require a qualification or fail to support the passage. The index should not assume the only successful outcome is retaining more text. I would close the action when the decision is resolved and the draft reflects it. Then I would choose the next relevant question or leave the current state without an active task if work is paused. A project map can describe a pause without creating a false sense of motion.
Give a reviewer a different route through the same material
A reviewer does not need the writer's entire workspace to answer a bounded question. I would provide a dated copy and identify the requested response: can the reader follow the argument and locate support for its factual points? Layout and proofreading might be outside that review stage. Naming the task keeps comments useful and prevents reviewers spending effort on a design that is still provisional. It also makes clear that a request to read is not an invitation to edit the live draft freely.
The review route should contain the information the reviewer is allowed and able to inspect. Some source material may be public; another record may contain private contributor details. I would not share the whole archive simply to make navigation convenient. The index can point to an appropriate source register or permitted excerpt while identifying any access limit. If the review genuinely requires material the reader cannot access, that is a scope problem to resolve, not something a confident link label can fix.
I would keep feedback and authorship distinct. A reviewer's suggestion does not automatically become an accepted project decision, and their access to the pack does not establish permission to publish their words. The index can identify where responses belong and who decides the next revision. Once the review is complete, I would record the relevant changes in the working project rather than leave several competing comment copies as equally authoritative instructions. The reviewer gets a manageable task; the writer retains a coherent place to continue.
Test the map after a gap
The returning-writer test begins before I open the draft. Can I explain the immediate task from the index alone? If the page says continue research, I would improve it. If it gives a precise source question and the relevant destinations, I can begin without replaying the original planning session. This is an inspection of the page's information, not a promise that an index will improve productivity. The useful outcome is visible: less guessing about which artifact and decision the page is pointing toward.
A second test follows the links in the order the page suggests. The current draft should be current, the source register should be the register and the scope note should explain the stated boundary. If a destination exists but no longer serves its label, I would repair the description or target. Technical link validity is not the same as useful navigation. A page can contain no broken links while sending every reader to a different, outdated stage of the project.
I would include an awkward case. Suppose the next action was completed, but the index still advertises it as urgent. The returning writer might repeat a check or overwrite a considered revision. The repair is not necessarily a more elaborate dashboard. It may be a short habit of updating the current-state paragraph when a consequential task closes. I would connect that update to the work's existing boundary rather than invent a separate maintenance process that itself needs an index and reminders.
Let the index change as the project changes
The booklet may become an essay, or its public-space examples may narrow to a single subject. I would update the purpose and destinations accordingly. The old scope note can explain the development if the history matters. I would not retain obsolete headings merely because they made the original page look balanced. A project index is a local map, and a map should reflect the work that actually exists. Its structure can become simpler as the project becomes more specific.
If the source register grows, I would consider whether the index should link to a particular subset or overview. It does not need to reproduce every addition. A larger archive can remain behind a small number of well-described entry points. The test is whether the main reader can reach the material required for the current choice. I would add a destination when a recurring navigation problem gives it a purpose, rather than promote every file or note to the top level.
The page can also change audience. Once a final booklet exists, the primary reader may be someone trying to understand what was published and where its materials are stored. Start writing no longer belongs at the top. I would make a clean transition instead of leaving an old to-do list above the final artifact. The same project can have a working index and a final collection note, each reflecting a different stage. Their relationship should remain clear so a future editor knows which one to consult.
Close a project without sealing away its context
At completion, I would identify the final artifact and its date or version, the source register used for it and any ongoing limits on illustrations or contributor material. This is more useful than a celebratory done label attached to a folder. A future reader may need to distinguish what was actually published from a later experiment or an unfinished supplementary section. The closure note can make that distinction without requiring them to inspect every draft and infer which one the project eventually used.
I would remove active-looking instructions that no longer apply, while preserving useful unresolved questions as reference. A question omitted from the booklet is not necessarily answered. If the project stopped because time or scope changed, the note should say so. Marking every source checked to clear the page would create false assurance. A closed project can contain incomplete research as long as the final artifact's relationship to it is understandable. Closure describes the work's disposition, not universal certainty about everything collected.
My final index check would be small: can another reader find the final output, understand its scope and locate its relevant context without my private explanation? If so, the page has finished its job. I would leave it stable until a real revision gives it a new role. The index should help a project start, resume and end. It does not need to keep the project permanently active just because the collection of notes remains available after the work is done.
Frequently Asked Questions
Q: How many links should a project index contain?
A: As many as its intended reader needs to navigate the current work. I would begin with a few clear destinations and add links when a real retrieval problem appears. A small page with accurate descriptions is preferable to a complete inventory that obscures the starting point.
Q: Should the index duplicate my task list?
A: Usually a short current priority and a link to the canonical plan are easier to maintain. If you copy tasks, decide who keeps both versions aligned. The index should clarify where work lives rather than create a competing operational list by accident.
Q: Can one page serve writers and reviewers?
A: Yes, if their entry points and permissions are distinct. Identify the live working file, the dated review copy and the response requested. Do not assume a reviewer needs access to private notes or every version merely because those materials are useful to the writer.
Q: What happens when the project changes direction?
A: Revise the current purpose and destinations. Preserve a short link to earlier scope decisions if they help explain the change. An index can be adapted or simplified; it is not an obligation to keep creating material for headings that no longer match the project.
Q: Does a finished project still need an index?
A: A brief collection note may remain useful for finding the final artifact and its context. Remove misleading active tasks, identify what was published and retain relevant limits. You need not keep reviewing a stable finished collection unless an actual use or change calls for it.
One thing to take forward
I would judge the next project index by one arrival: a person returning after a gap. Can they identify the present work, find the right artifact and understand the next choice? If they can, the page is doing enough. I would deepen the notes behind it when the project requires detail and keep the doorway clear enough that those notes remain reachable without becoming another layer of duplicated work.
Sources & further reading
Something needs correcting? Write to the editors with the article link.



