[{"data":1,"prerenderedAt":606},["ShallowReactive",2],{"docs-navigation":3,"docs-\u002Fbuilding\u002Fa-board-of-work":264,"surround-\u002Fbuilding\u002Fa-board-of-work":603},[4,33,96,124,183,222,241],{"title":5,"path":6,"stem":7,"children":8},"Start","\u002Fstart","1.start",[9,13,18,23,28],{"title":10,"path":6,"stem":11,"description":12},"Start here","1.start\u002Findex","What Desifex is, and how to get an application of your own running.",{"title":14,"path":15,"stem":16,"description":17},"What Desifex is","\u002Fstart\u002Fwhat-desifex-is","1.start\u002F1.what-desifex-is","An application factory where conversation is the interface — and the handful of things it deliberately will not do.",{"title":19,"path":20,"stem":21,"description":22},"Your first application","\u002Fstart\u002Fyour-first-application","1.start\u002F2.your-first-application","From a sentence to something running, in about twenty minutes, with nothing to install.",{"title":24,"path":25,"stem":26,"description":27},"The workbench","\u002Fstart\u002Fthe-workbench","1.start\u002F3.the-workbench","A tour of the screen you will spend your time on — the conversation, the seven tabs, and the menu.",{"title":29,"path":30,"stem":31,"description":32},"What to expect","\u002Fstart\u002Fwhat-to-expect","1.start\u002F4.what-to-expect","How long things take, what a good working rhythm looks like, and the parts that genuinely go wrong.",{"title":34,"path":35,"stem":36,"children":37},"Building","\u002Fbuilding","2.building",[38,41,46,51,56,61,66,71,76,81,86,91],{"title":34,"path":35,"stem":39,"description":40},"2.building\u002Findex","Getting what you actually wanted out of the conversation.",{"title":42,"path":43,"stem":44,"description":45},"Describing what you need","\u002Fbuilding\u002Fdescribing-what-you-need","2.building\u002F01.describing-what-you-need","How to phrase a request so that what comes back is what you meant.",{"title":47,"path":48,"stem":49,"description":50},"Watching a build","\u002Fbuilding\u002Fwatching-a-build","2.building\u002F02.watching-a-build","What the steps mean, what is happening underneath, and why you are not shown a log.",{"title":52,"path":53,"stem":54,"description":55},"Changing your mind","\u002Fbuilding\u002Fchanging-your-mind","2.building\u002F03.changing-your-mind","Interrupting a build, correcting a misunderstanding, and undoing something you asked for.",{"title":57,"path":58,"stem":59,"description":60},"More than one conversation","\u002Fbuilding\u002Fmore-than-one-conversation","2.building\u002F04.more-than-one-conversation","Putting a piece of work down and starting the next one cleanly — what the builder keeps, what it forgets, and when a fresh conversation is the right move.",{"title":62,"path":63,"stem":64,"description":65},"A board of work","\u002Fbuilding\u002Fa-board-of-work","2.building\u002F05.a-board-of-work","The Work tab — writing down everything you have thought of, deciding what is ready, and letting the builder take them one at a time.",{"title":67,"path":68,"stem":69,"description":70},"When a build fails","\u002Fbuilding\u002Fwhen-a-build-fails","2.building\u002F06.when-a-build-fails","What a failure actually means, what to try, and when to ask us.",{"title":72,"path":73,"stem":74,"description":75},"Showing it a file","\u002Fbuilding\u002Fshowing-it-files","2.building\u002F07.showing-it-files","Attaching a screenshot, a spreadsheet or a document to the conversation — often faster than describing it.",{"title":77,"path":78,"stem":79,"description":80},"Choosing a design system","\u002Fbuilding\u002Fchoosing-a-design-system","2.building\u002F08.choosing-a-design-system","What a design system decides, how to pick one, and what changing it later does.",{"title":82,"path":83,"stem":84,"description":85},"Asking for settings","\u002Fbuilding\u002Fasking-for-settings","2.building\u002F09.asking-for-settings","The conversation reaches the whole platform — addresses, icons, redirects, users, integrations and shipping. If you do not know where a setting is, ask.",{"title":87,"path":88,"stem":89,"description":90},"When it asks you","\u002Fbuilding\u002Fwhen-it-asks-you","2.building\u002F10.when-it-asks-you","Some decisions arrive as a screen rather than a message — a table to correct, a list to choose from — and the build waits for your answer.",{"title":92,"path":93,"stem":94,"description":95},"Starting from what you have","\u002Fbuilding\u002Fstarting-from-what-you-have","2.building\u002F11.starting-from-what-you-have","A spreadsheet, a document, a picture or a page of your own site — attached, read, and built from.",{"title":97,"path":98,"stem":99,"children":100},"Shipping","\u002Fshipping","3.shipping",[101,104,109,114,119],{"title":97,"path":98,"stem":102,"description":103},"3.shipping\u002Findex","Getting what you built in front of people, and getting back to an earlier version.",{"title":105,"path":106,"stem":107,"description":108},"Versions","\u002Fshipping\u002Fversions","3.shipping\u002F1.versions","Every build is kept, named after what was asked for, and can be compared and restored.",{"title":110,"path":111,"stem":112,"description":113},"Environments","\u002Fshipping\u002Fenvironments","3.shipping\u002F2.environments","Preview, test and live — what each one is, who can reach it, and why their data is separate.",{"title":115,"path":116,"stem":117,"description":118},"Deploying","\u002Fshipping\u002Fdeploying","3.shipping\u002F3.deploying","Putting a version into test or live, what happens while it deploys, and what happens if it fails.",{"title":120,"path":121,"stem":122,"description":123},"Going back","\u002Fshipping\u002Fgoing-back","3.shipping\u002F4.going-back","Restoring an earlier version when a change turned out to be wrong.",{"title":125,"path":126,"stem":127,"children":128},"Running","\u002Frunning","4.running",[129,133,138,143,148,153,158,163,168,173,178],{"title":130,"path":126,"stem":131,"description":132},"Running it","4.running\u002Findex","Everything in Settings — addresses, access, people, files, integrations and what crawlers are told.",{"title":134,"path":135,"stem":136,"description":137},"Addresses and domains","\u002Frunning\u002Faddresses-and-domains","4.running\u002F01.addresses-and-domains","The address an application gets, and how to put it on a domain you own.",{"title":139,"path":140,"stem":141,"description":142},"Who can reach it","\u002Frunning\u002Fwho-can-reach-it","4.running\u002F02.who-can-reach-it","Open, behind one shared password, or accounts — and why the choice is enforced in front of the application.",{"title":144,"path":145,"stem":146,"description":147},"People who sign in","\u002Frunning\u002Fpeople-who-sign-in","4.running\u002F03.people-who-sign-in","The workspace's user directory — adding the people who use your applications, which ones each may open, what you can keep about them, and two-step sign-in.",{"title":149,"path":150,"stem":151,"description":152},"Published files","\u002Frunning\u002Fpublished-files","4.running\u002F04.published-files","Documents your application hands to its users — a price list, a brochure, a form — with a stable address and no build to change them.",{"title":154,"path":155,"stem":156,"description":157},"Integrations","\u002Frunning\u002Fintegrations","4.running\u002F05.integrations","Email, SMS and Google — connected once, used by the application without it ever holding a credential.",{"title":159,"path":160,"stem":161,"description":162},"Appearance","\u002Frunning\u002Fappearance","4.running\u002F06.appearance","The browser tab, the icon, what a link looks like when somebody pastes it, and adding it to a phone's home screen.",{"title":164,"path":165,"stem":166,"description":167},"Redirects and search engines","\u002Frunning\u002Fredirects-and-search-engines","4.running\u002F07.redirects-and-search-engines","Old addresses that still get visited, and what crawlers are told about each environment.",{"title":169,"path":170,"stem":171,"description":172},"Configuration values","\u002Frunning\u002Fconfiguration-values","4.running\u002F08.configuration-values","Named values the application needs but must not contain — API keys, account numbers, thresholds.",{"title":174,"path":175,"stem":176,"description":177},"Your data","\u002Frunning\u002Fyour-data","4.running\u002F09.your-data","The Data tab — reading, correcting, adding to and clearing out what your application has stored, one environment at a time.",{"title":179,"path":180,"stem":181,"description":182},"Visitors","\u002Frunning\u002Fvisitors","4.running\u002F10.visitors","Who is using the application, counted without identifying anybody and with nothing to set up.",{"title":184,"path":185,"stem":186,"children":187},"Workspace","\u002Fworkspace","5.workspace",[188,192,197,202,207,212,217],{"title":189,"path":185,"stem":190,"description":191},"Your workspace","5.workspace\u002Findex","What every application in it shares — the domain, the design systems, the people, the user directory and, if you want it, one set of records — and how to be in more than one.",{"title":193,"path":194,"stem":195,"description":196},"People and roles","\u002Fworkspace\u002Fpeople-and-roles","5.workspace\u002F1.people-and-roles","Three roles, what each can do, how they apply to the builder as well as to the buttons, and why they belong to a workspace rather than to an account.",{"title":198,"path":199,"stem":200,"description":201},"More than one workspace","\u002Fworkspace\u002Fmore-than-one-workspace","5.workspace\u002F2.more-than-one-workspace","Belonging to several, switching between them, the role you hold in each, and why nothing crosses over.",{"title":203,"path":204,"stem":205,"description":206},"Organising applications","\u002Fworkspace\u002Ffolders-and-organising","5.workspace\u002F3.folders-and-organising","Folders on the dashboard, and how to keep a growing list navigable.",{"title":208,"path":209,"stem":210,"description":211},"Your own design systems","\u002Fworkspace\u002Fyour-own-design-systems","5.workspace\u002F4.your-own-design-systems","Authoring a design system for your brand, or a client's, by importing guidelines, a website or a Figma library.",{"title":213,"path":214,"stem":215,"description":216},"Your profile","\u002Fworkspace\u002Fyour-profile","5.workspace\u002F5.your-profile","Your name and how you are addressed, your password, your picture, two-step sign-in by email or text, and the theme.",{"title":218,"path":219,"stem":220,"description":221},"Where records live","\u002Fworkspace\u002Fwhere-records-live","5.workspace\u002F6.where-records-live","One store per environment, one across an application's environments, or one the whole workspace shares — what each costs you, and how to change it.",{"title":223,"path":224,"stem":225,"children":226},"Developers","\u002Fdevelopers","6.developers",[227,231,236],{"title":228,"path":224,"stem":229,"description":230},"For developers","6.developers\u002Findex","What is actually generated, and what to do when you inherit one.",{"title":232,"path":233,"stem":234,"description":235},"What gets built","\u002Fdevelopers\u002Fwhat-gets-built","6.developers\u002F1.what-gets-built","The stack, the shape of the repository, and the parts the platform provides rather than the application.",{"title":237,"path":238,"stem":239,"description":240},"Taking one over","\u002Fdevelopers\u002Ftaking-it-over","6.developers\u002F2.taking-it-over","For the developer who has just been handed an application built here.",{"title":242,"path":243,"stem":244,"children":245},"Reference","\u002Freference","7.reference",[246,249,254,259],{"title":242,"path":243,"stem":247,"description":248},"7.reference\u002Findex","Terms, limits, and what to do when something specific has gone wrong.",{"title":250,"path":251,"stem":252,"description":253},"Glossary","\u002Freference\u002Fglossary","7.reference\u002F1.glossary","Every term this documentation uses, in one place.",{"title":255,"path":256,"stem":257,"description":258},"Limits","\u002Freference\u002Flimits","7.reference\u002F2.limits","The boundaries that are real, so you do not discover them at an inconvenient moment.",{"title":260,"path":261,"stem":262,"description":263},"Troubleshooting","\u002Freference\u002Ftroubleshooting","7.reference\u002F3.troubleshooting","Specific symptoms, and what each one usually means.",{"id":265,"title":62,"body":266,"description":65,"extension":596,"hidden":597,"meta":598,"navTitle":599,"navigation":600,"path":63,"seo":601,"stem":64,"__hash__":602},"docs\u002F2.building\u002F05.a-board-of-work.md",{"type":267,"value":268,"toc":583},"minimark",[269,277,283,288,348,366,375,379,391,398,406,421,425,434,437,443,447,450,453,457,470,474,494,525,534,543,546,551,555,558,565,569],[270,271,272,276],"p",{},[273,274,275],"strong",{},"The Work tab."," A place to put everything you have thought of, so that asking\nfor things one at a time in the conversation is not the only way to work.",[278,279],"shot",{"alt":280,"caption":281,"name":282},"The Work tab: four columns — Backlog, To do, Doing and Done. Four cards wait in the backlog and two finished ones sit in Done, each offering to be done again.","Backlog and To do are yours; Doing and Done are the builder's. The two in Done here were picked up and built while the rest waited.","work-board",[284,285,287],"h2",{"id":286},"four-columns-and-two-of-them-are-yours","Four columns, and two of them are yours",[289,290,291,304],"table",{},[292,293,294],"thead",{},[295,296,297,301],"tr",{},[298,299,300],"th",{},"Column",[298,302,303],{},"Whose",[305,306,307,318,328,338],"tbody",{},[295,308,309,315],{},[310,311,312],"td",{},[273,313,314],{},"Backlog",[310,316,317],{},"Yours. Everything you have thought of.",[295,319,320,325],{},[310,321,322],{},[273,323,324],{},"To do",[310,326,327],{},"Yours. What is ready to be built.",[295,329,330,335],{},[310,331,332],{},[273,333,334],{},"Doing",[310,336,337],{},"The builder's. One card at a time.",[295,339,340,345],{},[310,341,342],{},[273,343,344],{},"Done",[310,346,347],{},"The builder's. What it finished, and what failed.",[270,349,350,351,353,354,356,357,359,360,362,363,365],{},"You move cards between ",[273,352,314],{}," and ",[273,355,324],{},". The builder takes the top card\nof ",[273,358,324],{},", moves it to ",[273,361,334],{}," while it works, and puts it in ",[273,364,344],{}," when\nthe build has finished.",[270,367,368,369,371,372,374],{},"Neither side reaches into the other's columns. That is what makes the board\nworth having rather than a list of instructions in a chat: when a card is in\n",[273,370,334],{}," it has been handed over, and when it is in ",[273,373,314],{}," nothing is\ngoing to happen to it until you say so.",[284,376,378],{"id":377},"writing-a-card-down","Writing a card down",[270,380,381,382,385,386,390],{},"At the bottom of the backlog: ",[273,383,384],{},"Add a card",". Type what needs doing and press\n",[387,388,389],"kbd",{},"Enter",".",[270,392,393,394,397],{},"The composer stays open. A board is filled in a burst of six thoughts, and\nhaving to reopen something between them is where the fourth one gets lost. Press\n",[387,395,396],{},"Esc"," when you are done.",[270,399,400,401,405],{},"A card asks for a title and nothing else. Open it afterwards to add the detail —\nwhat it is for, what it must not change, what ",[402,403,404],"em",{},"finished"," looks like. That detail\nis what the builder is given when it picks the card up, so it is worth writing\nfor anything that is not obvious.",[407,408,410],"note",{"type":409},"tip",[270,411,412,413,416,417,420],{},"Write cards the way you would brief a colleague, not the way you would write a\nticket. ",[402,414,415],{},"Customers can reset their own password — a link on the sign-in page\nthat emails them a one-time link, expiring after an hour"," is a card that gets\nbuilt correctly. ",[402,418,419],{},"Password reset"," is a card that gets built three times.",[284,422,424],{"id":423},"deciding-something-is-ready","Deciding something is ready",[270,426,427,428,431,432,390],{},"Press ",[273,429,430],{},"Ready →"," on a card, or drag it into ",[273,433,324],{},[270,435,436],{},"This is a separate act from writing the card down, deliberately. Everything\nstarts in the backlog — including a card you added meaning it to be next —\nbecause collapsing the two is how a half-written thought gets built.",[270,438,439,440,442],{},"Once a card is in ",[273,441,324],{}," the builder will get to it on its own. Nothing else\nis needed from you.",[284,444,446],{"id":445},"one-at-a-time","One at a time",[270,448,449],{},"The builder takes one card, finishes it, and takes the next.",[270,451,452],{},"This is not a queue waiting to be made faster. Two builds in one application\nshare the same files on disk and the same running copy; the second would be\nreading files the first is halfway through writing. The result is not two\nchanges in half the time, it is two half-finished changes and no way to tell\nwhich one broke what.",[284,454,456],{"id":455},"when-one-fails","When one fails",[270,458,459,460,462,463,466,467,390],{},"It goes to ",[273,461,344],{},", marked, with what went wrong on the card. Press ",[273,464,465],{},"Do it\nagain"," to put it back in the backlog — where you can edit it first, which is\nusually what a failed card needs. See\n",[468,469,67],"a",{"href":68},[284,471,473],{"id":472},"bringing-in-a-spreadsheet-you-already-have","Bringing in a spreadsheet you already have",[270,475,476,477,480,481,485,486,489,490,493],{},"Most teams arrive with the list already written down somewhere. Press ",[273,478,479],{},"Import\nfrom a spreadsheet"," at the top of the board and drop in a ",[482,483,484],"code",{},".csv",", ",[482,487,488],{},".xlsx"," or\n",[482,491,492],{},".ods"," file.",[270,495,496,497,500,501,504,505,485,508,485,511,485,514,485,517,520,521,524],{},"It looks for a ",[273,498,499],{},"Title"," column and a ",[273,502,503],{},"Detail"," column. Any heading that means\nthe same thing works — ",[402,506,507],{},"Task",[402,509,510],{},"Name",[402,512,513],{},"Summary",[402,515,516],{},"Description",[402,518,519],{},"Notes",",\n",[402,522,523],{},"Acceptance criteria",". If it cannot find a heading it recognises, it reads the\nfirst column as the tasks, so a bare one-column list works as it is.",[270,526,527,528,530,531,533],{},"The dialog has an example ",[482,529,488],{}," and an example ",[482,532,484],{}," to download if you would\nrather start from the shape it expects.",[270,535,536,539,540,542],{},[273,537,538],{},"Everything lands in the backlog",", whatever a status column in the file says.\nCards in ",[273,541,324],{}," are picked up and built without anybody pressing anything,\nand an import that landed there would start a build for every row of a file\nnobody had read line by line.",[270,544,545],{},"Importing the same file twice adds nothing: a title already on the board is\nskipped. So fixing three rows and uploading again gives you three cards, not a\nsecond copy of everything. Afterwards the dialog tells you what it did — how\nmany were added, how many were already there, and which columns it read.",[407,547,548],{},[270,549,550],{},"One file brings in at most 200 rows. A planning spreadsheet with four thousand\nin it is not a board, and turning it into one would not help anybody. Bring in\nthe part you are actually going to build.",[284,552,554],{"id":553},"when-to-use-the-board-and-when-to-use-the-conversation","When to use the board and when to use the conversation",[270,556,557],{},"The conversation is better for anything you want to watch, correct and steer —\nwhich is most of building an application.",[270,559,560,561,564],{},"The board is better when you already know a handful of things that need doing\nand do not want to sit with each one: write them down, mark two of them ready,\nand come back later. It is also the honest answer to ",[402,562,563],{},"what is left",", which a\nconversation is not.",[284,566,568],{"id":567},"next","Next",[570,571,572,578],"ul",{},[573,574,575,577],"li",{},[468,576,47],{"href":48}," — what happens once a card is\npicked up.",[573,579,580,582],{},[468,581,52],{"href":53}," — correcting something that\nwas built.",{"title":584,"searchDepth":585,"depth":585,"links":586},"",3,[587,589,590,591,592,593,594,595],{"id":286,"depth":588,"text":287},2,{"id":377,"depth":588,"text":378},{"id":423,"depth":588,"text":424},{"id":445,"depth":588,"text":446},{"id":455,"depth":588,"text":456},{"id":472,"depth":588,"text":473},{"id":553,"depth":588,"text":554},{"id":567,"depth":588,"text":568},"md",false,{},null,true,{"title":62,"description":65},"9jlpMF0YbRZ1QguaNiPqXb0MXuIbFQCU5GHR_Vx95EA",[604,605],{"title":57,"path":58,"stem":59,"description":60,"children":-1},{"title":67,"path":68,"stem":69,"description":70,"children":-1},1793657361791]