Edit in Depth
How to get a precise change out of MeDo: when to chat, when to use Edit mode, when a screenshot is faster, when to open the code, and how to recover from a bad change.
Editing your app introduces each tool. This page is about judgement: which tool gets a specific change done in one go, and what to do when a change goes wrong.
Match the tool to the change
Writing a change request that lands
MeDo reads your message the way a developer would read a ticket. The requests that come back right share three traits:
- Location. Page, then section, then element: "Contact page, the form, the Submit button".
- Current state and desired state. "The button is grey; make it the same green as the header."
- One thing. If you have five changes, send five messages, or group only the ones that belong together ("tighten the spacing across the whole Menu section").
If MeDo asks a question, answer it in the next message. Re-sending the original request starts the interpretation over.
Edit mode for copy and styling
Open Edit above the preview, click the element, and use the Edit element panel for text, font, colours, spacing, corners, and links. When the panel does not offer the property you need, use the Tell Medo your needs field under the element: the element stays attached to your instruction, so "make this card the same height as the others" refers to that card and nothing else.
Edit mode is limited to what is already on the page. To add something new, switch to chat.
Screenshots for anything positional
"Move the badge to the top-right corner of the image" is easy to say and easy to misread. A rectangle drawn with the Screenshot tool plus "move the badge here" is not. Use it whenever your instruction contains words like here, this one, between, or next to. Full examples: Edit with Screenshots.
Reference images and files
Attach a reference with the + button (Upload or Add from asset library) and describe how it should be used: "match this colour palette", "use this as the hero photo", "the layout of the pricing table should follow this screenshot". A picture of what you want is worth several paragraphs of description — MeDo can copy a look far more reliably than it can infer it.
Code view for the last mile
Open the Code view from the left rail to browse the project tree and edit any file. This is the right place for:
- a constant, label, or URL you can see in the source and want to change precisely;
- a small style tweak in a component;
- checking what MeDo actually did before you ask for something else.
Save and the preview refreshes. After editing the source, publish before you download the code so the package matches the live app.
Change the plan, not the result
For a new app or a large feature, MeDo first writes a requirements document (tabs: Requirements, Style, Backend). Fixing a wrong assumption there with Edit before you click Generate App is far cheaper than reworking a finished app. See Writing better prompts.
Recover from a bad change
- Undo — in Edit mode, use the undo arrow next to the Edit button.
- Ask MeDo to revert — "undo the last change" in chat brings back the previous state.
- Restore a version — open the version button in the top bar and pick the version you want; see Version rollback & trash.
- Refresh the preview — the refresh icon in the preview toolbar clears stale rendering.
And remember: none of this reaches visitors until you click Update.