[{"data":1,"prerenderedAt":541},["ShallowReactive",2],{"docs-navigation":3,"docs-\u002Freference\u002Ftroubleshooting":254,"surround-\u002Freference\u002Ftroubleshooting":539},[4,33,86,114,173,212,231],{"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 six 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],{"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\u002F1.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\u002F2.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\u002F3.changing-your-mind","Interrupting a build, correcting a misunderstanding, and undoing something you asked for.",{"title":57,"path":58,"stem":59,"description":60},"When a build fails","\u002Fbuilding\u002Fwhen-a-build-fails","2.building\u002F4.when-a-build-fails","What a failure actually means, what to try, and when to ask us.",{"title":62,"path":63,"stem":64,"description":65},"Showing it a file","\u002Fbuilding\u002Fshowing-it-files","2.building\u002F5.showing-it-files","Attaching a screenshot, a spreadsheet or a document to the conversation — often faster than describing it.",{"title":67,"path":68,"stem":69,"description":70},"Choosing a design system","\u002Fbuilding\u002Fchoosing-a-design-system","2.building\u002F6.choosing-a-design-system","What a design system decides, how to pick one, and what changing it later does.",{"title":72,"path":73,"stem":74,"description":75},"Asking for settings","\u002Fbuilding\u002Fasking-for-settings","2.building\u002F7.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":77,"path":78,"stem":79,"description":80},"When it asks you","\u002Fbuilding\u002Fwhen-it-asks-you","2.building\u002F8.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":82,"path":83,"stem":84,"description":85},"Starting from what you have","\u002Fbuilding\u002Fstarting-from-what-you-have","2.building\u002F9.starting-from-what-you-have","A spreadsheet, a document, a picture or a page of your own site — attached, read, and built from.",{"title":87,"path":88,"stem":89,"children":90},"Shipping","\u002Fshipping","3.shipping",[91,94,99,104,109],{"title":87,"path":88,"stem":92,"description":93},"3.shipping\u002Findex","Getting what you built in front of people, and getting back to an earlier version.",{"title":95,"path":96,"stem":97,"description":98},"Versions","\u002Fshipping\u002Fversions","3.shipping\u002F1.versions","Every build is kept, named after what was asked for, and can be compared and restored.",{"title":100,"path":101,"stem":102,"description":103},"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":105,"path":106,"stem":107,"description":108},"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":110,"path":111,"stem":112,"description":113},"Going back","\u002Fshipping\u002Fgoing-back","3.shipping\u002F4.going-back","Restoring an earlier version when a change turned out to be wrong.",{"title":115,"path":116,"stem":117,"children":118},"Running","\u002Frunning","4.running",[119,123,128,133,138,143,148,153,158,163,168],{"title":120,"path":116,"stem":121,"description":122},"Running it","4.running\u002Findex","Everything in Settings — addresses, access, people, files, integrations and what crawlers are told.",{"title":124,"path":125,"stem":126,"description":127},"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":129,"path":130,"stem":131,"description":132},"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":134,"path":135,"stem":136,"description":137},"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":139,"path":140,"stem":141,"description":142},"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":144,"path":145,"stem":146,"description":147},"Integrations","\u002Frunning\u002Fintegrations","4.running\u002F05.integrations","Email, SMS and Google — connected once, used by the application without it ever holding a credential.",{"title":149,"path":150,"stem":151,"description":152},"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":154,"path":155,"stem":156,"description":157},"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":159,"path":160,"stem":161,"description":162},"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":164,"path":165,"stem":166,"description":167},"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":169,"path":170,"stem":171,"description":172},"Visitors","\u002Frunning\u002Fvisitors","4.running\u002F10.visitors","Who is using the application, counted without identifying anybody and with nothing to set up.",{"title":174,"path":175,"stem":176,"children":177},"Workspace","\u002Fworkspace","5.workspace",[178,182,187,192,197,202,207],{"title":179,"path":175,"stem":180,"description":181},"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":183,"path":184,"stem":185,"description":186},"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":188,"path":189,"stem":190,"description":191},"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":193,"path":194,"stem":195,"description":196},"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":198,"path":199,"stem":200,"description":201},"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":203,"path":204,"stem":205,"description":206},"Your profile","\u002Fworkspace\u002Fyour-profile","5.workspace\u002F5.your-profile","Your name, your password, your picture, and the theme.",{"title":208,"path":209,"stem":210,"description":211},"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":213,"path":214,"stem":215,"children":216},"Developers","\u002Fdevelopers","6.developers",[217,221,226],{"title":218,"path":214,"stem":219,"description":220},"For developers","6.developers\u002Findex","What is actually generated, and what to do when you inherit one.",{"title":222,"path":223,"stem":224,"description":225},"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":227,"path":228,"stem":229,"description":230},"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":232,"path":233,"stem":234,"children":235},"Reference","\u002Freference","7.reference",[236,239,244,249],{"title":232,"path":233,"stem":237,"description":238},"7.reference\u002Findex","Terms, limits, and what to do when something specific has gone wrong.",{"title":240,"path":241,"stem":242,"description":243},"Glossary","\u002Freference\u002Fglossary","7.reference\u002F1.glossary","Every term this documentation uses, in one place.",{"title":245,"path":246,"stem":247,"description":248},"Limits","\u002Freference\u002Flimits","7.reference\u002F2.limits","The boundaries that are real, so you do not discover them at an inconvenient moment.",{"title":250,"path":251,"stem":252,"description":253},"Troubleshooting","\u002Freference\u002Ftroubleshooting","7.reference\u002F3.troubleshooting","Specific symptoms, and what each one usually means.",{"id":255,"title":250,"body":256,"description":253,"extension":532,"hidden":533,"meta":534,"navTitle":535,"navigation":536,"path":251,"seo":537,"stem":252,"__hash__":538},"docs\u002F7.reference\u002F3.troubleshooting.md",{"type":257,"value":258,"toc":511},"minimark",[259,264,273,280,284,295,299,302,308,312,315,318,321,325,328,342,346,351,355,381,385,392,395,399,415,419,422,426,445,449,458,462,471,475,481,487,491,504,508],[260,261,263],"h2",{"id":262},"the-preview-is-blank-or-will-not-load","The preview is blank or will not load",[265,266,267,268,272],"p",{},"The application's container may have been stopped. ",[269,270,271],"strong",{},"Start application"," in the\napplication menu, and give it a few seconds.",[265,274,275,276],{},"If it was already running, ask the builder: ",[277,278,279],"em",{},"the preview is blank — have a look\nat why.",[260,281,283],{"id":282},"a-build-failed","A build failed",[265,285,286,287,290,291,294],{},"Say ",[269,288,289],{},"continue",". That resolves most of them. See\n",[292,293,57],"a",{"href":58},".",[260,296,298],{"id":297},"a-build-seems-to-be-taking-forever","A build seems to be taking forever",[265,300,301],{},"Watch the steps, not the clock. A build that is working keeps narrating itself\n— new steps keep appearing — and a large first build legitimately takes a\nwhile.",[265,303,304,305,307],{},"If no new step has appeared for several minutes, that build is no longer\nrunning. Within a few minutes it says so and the application comes back to you,\nready to be started again from the application menu. Nothing it had already\nwritten is lost. Say ",[269,306,289],{}," to carry on from where it stopped.",[260,309,311],{"id":310},"the-build-finished-but-nothing-changed-on-the-preview","The build finished but nothing changed on the preview",[265,313,314],{},"Two possibilities, in order of likelihood.",[265,316,317],{},"Your browser is showing a cached copy — reload with the button above the\npreview.",[265,319,320],{},"Or the change was genuinely not made, because the request was read differently\nfrom how you meant it. Read the steps back: they say what it did.",[260,322,324],{"id":323},"test-or-live-is-showing-an-old-version","Test or live is showing an old version",[265,326,327],{},"Building does not deploy. A build changes the preview only.",[265,329,330,331,333,334,337,338,341],{},"Go to ",[269,332,95],{}," and press ",[269,335,336],{},"Put the latest on Test",", or ",[269,339,340],{},"Put what is on\nTest live",". Each card tells you whether it is showing your latest work.",[260,343,345],{"id":344},"the-data-i-entered-in-test-is-not-in-live","The data I entered in test is not in live",[265,347,348,349,294],{},"That is the design. Each environment has its own database, so a version being\ntested cannot write to what the business is running on. See\n",[292,350,100],{"href":101},[260,352,354],{"id":353},"my-custom-domain-is-not-working","My custom domain is not working",[356,357,358],"steps",{},[359,360,361,365,375,378],"ol",{},[362,363,364],"li",{},"Check both DNS records exist — the one pointing the address here, and the\nTXT record proving ownership.",[362,366,367,368,371,372,294],{},"Press ",[269,369,370],{},"Verify"," in ",[269,373,374],{},"Settings › Domain",[362,376,377],{},"Wait. DNS propagation takes minutes to an hour and cannot be hurried.",[362,379,380],{},"Try the platform address. If that works, it is DNS; if it does not, the\napplication is not deployed.",[260,382,384],{"id":383},"visitors-are-not-being-counted","Visitors are not being counted",[265,386,387,388,391],{},"They are only counted for ",[269,389,390],{},"deployed"," environments. The preview is not counted,\nbecause it is your team looking at it.",[265,393,394],{},"If a deployment is serving and the number is still zero after a day, tell us.",[260,396,398],{"id":397},"somebody-cannot-sign-in-to-my-application","Somebody cannot sign in to my application",[400,401,402,409,412],"ul",{},[362,403,404,405,408],{},"Check they are on the list in ",[269,406,407],{},"Settings › Access",", and not suspended.",[362,410,411],{},"If they are in the workspace but not this application, either grant them this\napplication or turn on one login for every application.",[362,413,414],{},"Reset their password. It is generated, shown once, and emailed if the\napplication has email connected.",[260,416,418],{"id":417},"the-shared-password-is-not-being-asked-for","The shared password is not being asked for",[265,420,421],{},"Check which environment you are on. The password is per environment — turning it\non for test does not turn it on for live.",[260,423,425],{"id":424},"an-email-is-not-arriving","An email is not arriving",[356,427,428],{},[359,429,430,436,439,442],{},[362,431,432,435],{},[269,433,434],{},"Settings › Integrations"," — is email connected?",[362,437,438],{},"Press the test. It is a real send to an address that discards it, so a pass\nmeans the credentials work.",[362,440,441],{},"If the test passes and the application's email does not arrive, the problem\nis in what the application does, not in the connection. Ask the builder to\nlook at it.",[362,443,444],{},"Check the recipient's spam folder, and whether your sending domain is\nverified with the provider.",[260,446,448],{"id":447},"the-tab-title-is-wrong-or-a-shared-link-has-no-picture","The tab title is wrong, or a shared link has no picture",[265,450,451,452,455,456,294],{},"Those are settings, not code: ",[269,453,454],{},"Settings › Appearance",". They apply on the next\ndeployment. See ",[292,457,149],{"href":150},[260,459,461],{"id":460},"an-old-address-stopped-working","An old address stopped working",[265,463,464,467,468,294],{},[269,465,466],{},"Settings › Redirects",". Add the old path and where it should now go. Served in\nfront of the application, so it works even while the application does not. See\n",[292,469,470],{"href":155},"Redirects",[260,472,474],{"id":473},"the-test-copy-is-appearing-in-search-results","The test copy is appearing in search results",[265,476,477,480],{},[269,478,479],{},"Settings › Search engines"," — test is closed by default, so it has been\nopened. Close it.",[265,482,483,484,294],{},"Note that this asks crawlers not to index it; it is not access control. If it\nmust not be readable, use ",[292,485,486],{"href":130},"Access",[260,488,490],{"id":489},"i-cannot-find-a-setting","I cannot find a setting",[265,492,493,494,497,498,501,502,294],{},"Ask for it. The conversation reaches everything in Settings, so ",[277,495,496],{},"where do I turn\non the shared password"," and ",[277,499,500],{},"turn on the shared password"," both work. See\n",[292,503,72],{"href":73},[260,505,507],{"id":506},"still-stuck","Still stuck",[265,509,510],{},"Tell us the application's name and roughly when it happened. We can see the\nwhole build, including the parts the interface deliberately does not show.",{"title":512,"searchDepth":513,"depth":513,"links":514},"",3,[515,517,518,519,520,521,522,523,524,525,526,527,528,529,530,531],{"id":262,"depth":516,"text":263},2,{"id":282,"depth":516,"text":283},{"id":297,"depth":516,"text":298},{"id":310,"depth":516,"text":311},{"id":323,"depth":516,"text":324},{"id":344,"depth":516,"text":345},{"id":353,"depth":516,"text":354},{"id":383,"depth":516,"text":384},{"id":397,"depth":516,"text":398},{"id":417,"depth":516,"text":418},{"id":424,"depth":516,"text":425},{"id":447,"depth":516,"text":448},{"id":460,"depth":516,"text":461},{"id":473,"depth":516,"text":474},{"id":489,"depth":516,"text":490},{"id":506,"depth":516,"text":507},"md",false,{},null,true,{"title":250,"description":253},"EgKGy4j-JDJloU1brEUK0La1WgG1xXMl88lpjmBDD-w",[540,535],{"title":245,"path":246,"stem":247,"description":248,"children":-1},1790202296897]