> ## Documentation Index > Fetch the complete documentation index at: https://docs.node-pad.com/llms.txt > Use this file to discover all available pages before exploring further. # Writing > Keep drafting, fact-checking, and editing in separate branches so the voice of the piece stays intact. export const EdgeChip = ({type = 'continuation', children}) => {children}; Writing often breaks when drafting and research happen in the same thread. NodePad gives those jobs separate branches so the voice of the piece does not get washed out by fact-finding, outlining, or critique. A reference brings one fact back into the draft; a merge brings several at once. ## A strong workflow Use a main branch for the actual prose so the branch history stays about tone, structure, and revisions. When you need facts, examples, or citations, branch from the draft instead of asking inside it. Use an `@` reference when one fact should come back into the draft. Use merge sources when the next turn needs several findings or alternate versions at once. If you want structural criticism or an alternate tone pass, make that a separate branch instead of muddying the main draft history. ## Why this works The draft branch stays about the piece itself, not about every research side trip. You can reference the exact message that found the fact instead of paraphrasing it from memory. Alternate openings, structural edits, and critique passes can each get their own branch. For long pieces, use one branch per section and one text note that records the target audience, publication, and tone constraints. ## Continue Branch for research, branch for critique. Cite a single finding without dragging the whole research branch.