[{"data":1,"prerenderedAt":147},["ShallowReactive",2],{"changelog-\u002Fchangelog\u002Fmerge-fields-as-chips":3},{"id":4,"title":5,"body":6,"date":128,"description":129,"emailSummary":130,"extension":131,"highlights":132,"image":138,"imageWidth":138,"meta":139,"navigation":140,"path":141,"seo":142,"stem":143,"tags":144,"__hash__":146},"changelog\u002Fchangelog\u002F0009.merge-fields-as-chips.md","Merge fields land where your cursor is",{"type":7,"value":8,"toc":120},"minimark",[9,13,18,26,29,33,44,47,77,80,84,99,106,110,117],[10,11,12],"p",{},"Merge fields are the parts of an agreement template that fill themselves in from\neach inspection — the client's name, the property address, your fee. Getting one\ninto a template used to be a small chore.",[14,15,17],"h2",{"id":16},"where-youre-actually-typing","Where you're actually typing",[10,19,20,21,25],{},"Clicking a merge field appended it to the ",[22,23,24],"strong",{},"bottom"," of the agreement. Not where\nyour cursor was — the bottom. So the real workflow was: click the field, scroll\nto the end, cut it, scroll back, paste it.",[10,27,28],{},"Now it goes in at the cursor. If you've highlighted some text first, the merge\nfield replaces it.",[14,30,32],{"id":31},"they-look-like-fields-now","They look like fields now",[10,34,35,39,40,43],{},[36,37,38],"code",{},"{{property_address}}"," was indistinguishable from the sentence around it, easy to\ntypo into something that silently never filled in, and easy to half-delete into\n",[36,41,42],{},"{{property_addres}}",".",[10,45,46],{},"Each merge field is now a chip showing its plain-English label:",[48,49,50],"blockquote",{},[10,51,52,53,59,60,65,66,71,72,43],{},"This agreement is made between ",[22,54,55],{},[56,57,58],"span",{},"Inspector name"," of ",[22,61,62],{},[56,63,64],{},"Company name","\n(\"Inspector\") and ",[22,67,68],{},[56,69,70],{},"Client name(s)"," (\"Client\") for the inspection of the\nproperty located at ",[22,73,74],{},[56,75,76],{},"Property address",[10,78,79],{},"You can see at a glance which parts of the document fill themselves in. A chip is\na single object: one backspace removes the whole thing, and you can't\naccidentally break it in half.",[14,81,83],{"id":82},"two-more-ways-to-insert-one","Two more ways to insert one",[10,85,86,87,90,91,94,95,98],{},"The ",[36,88,89],{},"\u002F"," command menu — the one that gives you headings, lists and dividers — now\nhas a ",[22,92,93],{},"Merge fields"," group at the bottom. Type ",[36,96,97],{},"\u002Ffee"," and you get the\ninspection fee.",[10,100,101,102,105],{},"Or type ",[36,103,104],{},"{"," and you get just the merge fields, nothing else.",[14,107,109],{"id":108},"nothing-to-migrate","Nothing to migrate",[10,111,112,113,116],{},"Open any template you already have and its merge fields turn into chips. Save it\nand they go back out as the same ",[36,114,115],{},"{{…}}"," tokens they always were, so the\nagreement your clients read and sign is unchanged.",[10,118,119],{},"One quiet fix came with this: a merge field wrapped in bold or italics used to\nlose that formatting when the template was re-saved, which is why the sample\nagreement's bolded opening paragraph would flatten out over time. It doesn't\nanymore.",{"title":121,"searchDepth":122,"depth":122,"links":123},"",2,[124,125,126,127],{"id":16,"depth":122,"text":17},{"id":31,"depth":122,"text":32},{"id":82,"depth":122,"text":83},{"id":108,"depth":122,"text":109},"2026-08-18","Agreement merge fields now insert at your cursor instead of the bottom of the document, and read as labelled chips rather than raw {{property_address}} text.","Building an agreement template meant clicking a merge field, watching {{property_address}} appear at the very bottom of the document, then scrolling down to cut and paste it where you actually wanted it. Now it goes in at your cursor — or replaces whatever you've highlighted. Merge fields also stop looking like code. Each one renders as a labelled chip reading 'Property address' instead of {{property_address}}, so you can see at a glance which parts of the agreement fill themselves in, and a chip deletes as a single unit rather than leaving a half-broken token behind. Two more ways to reach them: type \u002F in the editor and merge fields now appear at the bottom of the command menu alongside headings and lists, or just type { to get the merge-field list on its own. Existing templates pick all of this up automatically — nothing to migrate, and the agreement your clients see is unchanged.","md",[133,134,135,136,137],"Merge fields insert at your cursor, or replace the text you've selected","Each one shows as a labelled chip — \"Property address\", not {{property_address}}","A chip deletes in one keystroke instead of leaving a broken token","Type \u002F and pick a merge field from the command menu, or type { for the list on its own","Bold and italic formatting on a merge field is now kept when you save",null,{},true,"\u002Fchangelog\u002Fmerge-fields-as-chips",{"title":5,"description":129},"changelog\u002F0009.merge-fields-as-chips",[145],"Agreements","r3eCW8TwCtycHhebVYYMjzCrPdIofoYBfXnmAPi4x0E",1787848600095]