Skip to content

Drag & Drop Elements

You can drag any of the elements inside App Structure. Just select the element you want to move and start dragging it in the tree: When the element which you ar

Use Wappler drag-and-drop editing deliberately so page structure stays clear while you move faster in Design view.

Drag and drop is one of the fastest ways to reshape a page in Wappler, but it is also where structure can quietly get damaged. The goal is not just to move something until it looks right. The goal is to keep parent-child relationships, layout intent, and future editability intact while you work visually.

What to watch
When you drag elements, pay attention to nesting, not just position. A card moved into the wrong parent may still render, but it becomes harder to reason about later.
Modern-safe workflow
Use drag and drop for layout refinement, then confirm the structure in the editor surfaces instead of relying only on appearance.
Move small pieces before moving large page sections.
Watch where containers start and end.
If the structure becomes unclear, pause and reselect the intended parent.
Use drag and drop with Bootstrap layout rules in mind.

These habits keep visual editing fast without making later maintenance harder.

The safest moves are usually within the same parent. Reordering siblings changes flow without changing the structural role of the element.

Low-risk move
Start with sibling reordering when you want visual refinement without structural surprise.

Moving an element into a different row, column, or section changes more than its position. It changes what that element belongs to.

Check the parent
If the destination parent changes, the meaning of the element usually changes too.

After a structural move, briefly check the relevant editor panel or selection context so the new hierarchy is explicit, not accidental.

Trust structure, not appearance
A page can look correct while still being nested in the wrong place.

After you can move elements safely, the next job is controlling styling hooks and spacing without mixing responsibilities.

Browse HTML Editor tours: Quick Overview, Design + Code, and Page Panels.

This menu lists the HTML Editor tours. Use it to jump into a topic (Quick Overview is a good start).

Get a quick overview of Html Editor: Main Toolbar and Design Toolbar.

Use this quick overview to understand how the HTML Editor fits together before you learn any single control in isolation. You will see the main workspace, the view-switching model, and the editing surfaces that form the foundation for page building, inspection, and refinement in Wappler.

The main toolbar contains common page actions and view controls.

The Design toolbar provides design-specific tools and modes.

Browse Design + Code tours: Overview, How To’s, and Reference.

Choose a design or code topic.

Browse Page Panels tours: Overview, How To’s, and Reference.

Choose a page panel topic.

Browse Selection Panels tours: Overview, How To’s, and Reference.

Choose a selection panel topic.

Explore HTML Editor Design Code: key areas and how they work together.

The Design and Code relationship is easier to learn when you treat it as one workflow viewed from two angles. This overview shows how the visual canvas and underlying markup support each other, and why understanding that handoff makes later editing decisions more deliberate.

Use the toolbar to switch between Design, Code, and Split views.

Design View renders the page so you can select and edit elements visually.

Code View lets you edit markup with full code tooling.

Goal-based how-to guides for the HTML Editor, covering common design and code workflows.

Use this menu when your next question is task-based rather than conceptual. It gathers the common Design and Code workflows in one place, so you can start from the job you need to complete and then jump into the focused tour that shows the exact control sequence.

Reference hub for HTML Editor Design + Code topics, linking only to reference tours for Design View and Code View.

Jump to a specific reference topic for Design View or Code View.

Browse Design View tours: Overview, How To’s, and Reference.

Overview, How To’s, and Reference for Design view.

Browse Code View guides for editing HTML directly, navigating markup faster, and using Monaco-powered tools inside the HTML Editor.

Overview, How To’s, and Reference for Code view.

Explore Components: Components picker and Search and browse.

The components workflow makes more sense when you first see where Wappler exposes page structure and insertion tools together. This tour starts by locating that area in context, then explains how component selection and component insertion support the rest of your editing workflow.

We’ll select body as the insertion point. This step matters because Insertion point is part of Page Panels Structure Body, and understanding that context makes the next action easier to repeat in your own project.

We’ll use Insert Child to open the Components picker. This step matters because Components picker is part of Page Panels Structure Body, and understanding that context makes the next action easier to repeat in your own project.

Use search to find components, then select one to insert. This step matters because Search and browse is part of Components Popup Anchor Right, and understanding that context makes the next action easier to repeat in your own project.

Learn what the Design toolbar controls in the HTML Editor, from element actions and responsive helpers to faster canvas editing.

The Design toolbar is where page editing shifts from passive viewing to active manipulation. This tour places the toolbar in context, explains the kinds of actions it centralizes, and helps you see why many design-view tasks begin here before you move into a panel or the canvas.

Learn the HTML Editor code tools for search, formatting, navigation, and repeatable edits while working in Code View.

The code tools area is where editing commands stop being abstract shortcuts and become repeatable page-maintenance actions. This tour shows where those tools live, when you reach for them during normal code editing, and how they support faster changes without leaving the HTML Editor.

Use Code View for fast editing, navigation, and refactoring.

Explore HTML Editor Page Panels: key areas and how they work together.

The page panels are the organizing surfaces that keep the HTML Editor manageable once a project grows. This overview explains what those panels are for, how they support everyday editing and navigation, and why understanding their roles makes the rest of the page workflow easier to follow.

Use Structure to browse, search, and edit your page’s component tree.

Use the AI Assistant to ask questions and apply changes safely to your page. This step matters because AI Assistant is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Use Network to inspect XHR/fetch and asset requests while previewing your page. This step matters because Network is part of the Network panel, and understanding that context makes the next action easier to repeat in your own project.

Goal-based how-to guides for the Page panels, including common tasks and navigation between panels.

Choose a quick walkthrough from the list.

Find your way around HTML Editor Page Panels: Page Panels Reference.

Use this reference tour as a map of the page-panel area before you depend on it for navigation. It points out the main panels and entry points, explains what each one helps you do, and gives you a reliable mental index for later page-management work.

Get oriented in the App Structure panel: key tools, common workflows, and where to look next.

Choose what you’d like to learn about the Structure panel.

Browse AI Assistant tours: Overview, How To’s, and Reference.

Pick an overview, a goal-based How To, or the full reference for the AI panel. This step matters because AI Assistant is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Get oriented in the Network panel: key tools, common workflows, and where to look next.

Start with the wider context in the Page Panels area so the next control makes sense in the full workflow. In the next step, you will focus on Network and see how it fits into this area.

Pick an overview, a goal-based How To, or the full reference for the Network panel. This step matters because Network is part of the Network panel, and understanding that context makes the next action easier to repeat in your own project.

Explore HTML Editor Selection Panels: Selection Panels and Switch panels.

The selection panels are where Wappler turns a chosen element into actionable settings, styles, and data context. This overview explains how those panels work together, why they matter to everyday editing, and how the focused tours build on this same selection-first workflow.

Use the tabs to switch between Properties, Design, Styles, and Data.

Goal-based how-to guides for the Selection panels, focused on switching context and working faster.

Choose a quick walkthrough from the list. This step matters because Selection Panels How To’s is part of Selection Panels, and understanding that context makes the next action easier to repeat in your own project.

Find your way around HTML Editor Selection Panels: Selection Panels Reference.

Treat this reference tour as a map of the selection panels before you rely on them for faster editing. It points out the main panel families, explains what each one is responsible for, and helps you remember where to return when a selected element needs deeper inspection.

Get oriented in the Inspector panel: key tools, common workflows, and where to look next.

Overview, How To’s, and Reference for the Inspector panel.

Browse Design panel guides for layout controls, spacing presets, responsive tweaks, and inspector-driven page adjustments.

Adjust layout and presets with the Design inspector.

Browse Styles panel guides for class management, CSS inspection, rule editing, and jump-to-source workflows in the HTML Editor.

Organise classes and CSS overrides.

Browse Data panel guides for bound datasets, source inspection, picker workflows, and selection-aware data previews.

Preview datasets bound to the current selection.

Find your way around HTML Editor Design View: where to find the main controls and what they do.

Use this reference tour as a map of Design View before you depend on it for faster editing. It highlights the surfaces and controls you revisit most often, explains what each one is for, and helps you remember where to return when a visual selection or preview task comes up.

Use the main toolbar to switch between Design, Code, and Split views.

The Design toolbar provides tools and toggles for working visually.

Select, inspect, and manipulate elements directly on the canvas.

Find your way around HTML Editor Code View: where to find the main controls and what they do.

Treat this reference tour as a map of Code View before you start using it under time pressure. It points out the controls and surfaces you revisit most often, explains what each one is for, and helps you remember where to return when you need direct source editing.

Use the main toolbar to switch views and access editor tools.

Right-click in the editor for common actions.

Use find/replace, go to line, and formatting to work faster.

Explore HTML Editor Design View: key areas and how they work together.

Design View is the live editing surface where page structure becomes something you can inspect and manipulate directly. This overview explains why the view matters, what kind of work belongs here, and how it connects to the toolbar and panels you use for deeper changes.

The Design toolbar contains tools for selecting, inserting, and working with the page.

Click elements on the canvas to select them.

Goal-based how-to guides for Design View, focused on working visually with layout and components.

Choose a walkthrough.

Get oriented in Code View: key tools, common workflows, and where to look next.

Code View is the part of the HTML Editor where you inspect the real source behind the visual page. This overview shows how to reach it, what kinds of tasks belong there, and why understanding its role makes later find, replace, format, and line-navigation commands easier to use well.

Edit markup directly in Code View.

Goal-based how-to guides for Code View, focused on editing, navigation, and productivity.

Choose a walkthrough.

Learn how to find in Structure in the Page panels. Use this tour as a quick refresher.

Finding something in structure is faster once you treat the page tree as a navigation tool instead of a static outline. This how-to starts from that goal, then explains how locating the right node gives you the context you need before editing, inserting, or inspecting anything else.

Switch to the Structure tab.

Use the search box to filter and jump to matching nodes. This step matters because Search is part of the Structure panel, and understanding that context makes the next action easier to repeat in your own project.

Select a matching node in the tree to focus it. This step matters because Pick a result is part of the Structure panel, and understanding that context makes the next action easier to repeat in your own project.

Learn how to use the AI Assistant in the Page panels. Use this tour as a quick refresher.

Using the AI assistant works best when you treat it as a contextual helper tied to the page you are editing. This how-to begins with that framing, then shows how to approach the assistant so its suggestions stay grounded in the current page structure and editing goal.

Switch to the AI Assistant tab. This step matters because Open AI Assistant is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Describe what you want to do. Use the suggested actions to apply changes. This step matters because Write a prompt is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Review the suggested edits and apply them when ready. This step matters because Apply changes is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Learn how to debug with Network in the Page panels. Use this tour as a quick refresher.

Network debugging is easier when you start with the page-level tools that expose request activity in context. This how-to frames the goal before you click anything, then shows how the HTML Editor helps you connect a page action to the network behavior you need to inspect.

Switch to the Network tab. This step matters because Open Network is part of the Network panel, and understanding that context makes the next action easier to repeat in your own project.

Preview the page and look for XHR/fetch and asset requests appearing here. This step matters because Watch requests is part of the Network panel, and understanding that context makes the next action easier to repeat in your own project.

Select a request to inspect its headers and response. This step matters because Inspect a request is part of the Network panel, and understanding that context makes the next action easier to repeat in your own project.

Explore HTML Editor Structure: key areas and how they work together.

Use the Structure panel to navigate the page’s element hierarchy, select elements, and perform element-level operations.

Use the toolbar to adjust what’s shown in the tree, manage frameworks, and quickly search. This step matters because Toolbar is part of the Structure panel, and understanding that context makes the next action easier to repeat in your own project.

The tree reflects your current page. Selecting a node usually selects the element in the editor.

Goal-based how-to guides for the App Structure panel, focused on navigation, selection, and organizing.

Pick a task to learn step-by-step.

HTML Editor: App Structure Panel Reference

Section titled “HTML Editor: App Structure Panel Reference”

Reference tour for the App Structure panel: panel layout, navigation tools, element selection, and how to work through the page DOM hierarchy.

Use this reference tour as a map of the Structure panel before you depend on it for navigation and editing. It highlights the parts of the tree you revisit most often, explains what each area is responsible for, and helps you remember where structural page actions begin.

Show All Elements: include hidden/framework-specific nodes. Manage frameworks: enable/disable framework visibility. Find Elements: search the tree. ?: open Structure panel tours. Menu (⋯): Collapse All, Expand All, Refresh.

Right-click an element in the tree to access Insert Before/After/Child, Move to Separate File, Duplicate, and Delete.

Get oriented in the AI panel: key tools, common workflows, and where to look next.

Use this overview to place the AI area inside the broader HTML Editor workflow before you start asking it for changes. You will see where the panel fits, what kind of help it is designed to provide, and how to treat it as an editing aid instead of a black box.

Your prompts and responses appear here. Use the How To’s to learn common workflows. This step matters because Conversation area is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

AI panel reference for the HTML Editor: modes, toolbar controls, and common text actions.

This reference walks through the AI panel controls and common workflow patterns. This step matters because Reference overview is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Use the toolbar to change modes, start new chats, open history, and pick models. This step matters because Toolbar is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Use text actions to copy, reuse, or refine content as you iterate. This step matters because Text actions is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Use the conversation area to review results, copy content, and iterate. If you’re not seeing options yet, models may still be loading.

Learn how to ask a question in the AI panel. Use this tour as a quick refresher.

Ask mode is best for explanations and guidance without applying changes automatically. This step matters because Goal: Ask a question is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Make sure the assistant is in Ask mode before you submit your question. This step matters because Set mode to Ask is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Be specific and include relevant context (file, component, goal). This step matters because Write your question is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Refine the question or try a different model if needed. This step matters because Done is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Learn how to use Act mode in the AI panel. Use this tour as a quick refresher.

Act mode is best when you want the assistant to propose or perform concrete changes. This step matters because Goal: Use Act mode is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Switch the mode to Act before requesting edits. This step matters because Switch to Act is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Review the proposed changes and apply only what you understand. This step matters because Review the result is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

If needed, start a new chat to reset context. This step matters because Done is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Learn how to choose a model in the AI panel. Use this tour as a quick refresher.

Different models can be better at different tasks (speed vs. quality). This step matters because Goal: Choose a model is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Open the model selector in the AI panel. This step matters because Open the model menu is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Select a model and continue with your prompt. This step matters because Confirm selection is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Try the same prompt with a different model to compare. This step matters because Done is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Learn how to use history in the AI panel. Use this tour as a quick refresher.

History helps you find previous prompts and responses. This step matters because Goal: Use history is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Open the history list to review earlier chats. This step matters because Toggle history is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Reuse a prompt when you want similar results on a new page. This step matters because Reuse a previous prompt is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Use New to start fresh when needed. This step matters because Done is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Learn how to stop generation in the AI panel. Use this tour as a quick refresher.

Stop cancels the current generation if it’s taking too long or going off-track. This step matters because Goal: Stop generation is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Use Stop to cancel output, then adjust your prompt. This step matters because Use Stop is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

You can adjust the prompt and try again. This step matters because Done is part of the Page Panels area, and understanding that context makes the next action easier to repeat in your own project.

Explore HTML Editor Network: Network panel and Requests tree.

Start with the wider context in the Page Panels area so the next control makes sense in the full workflow. In the next step, you will focus on Network panel and see how it fits into this area.

The Network panel shows requests made by the Design view, including XHR and asset loading.

Each request appears as a tree node. Expand nodes to inspect details like headers and payloads.

Goal-based how-to guides for the Network panel, focused on inspecting requests and debugging.

Start with the wider context in the Page Panels area so the next control makes sense in the full workflow. In the next step, you will focus on Network How To’s and see how it fits into this area.

Choose a quick walkthrough from the list. This step matters because Network How To’s is part of the Network panel, and understanding that context makes the next action easier to repeat in your own project.

Reference tour for the Network panel: request and response inspection, timing details, HTTP diagnostics, and how to debug network activity while building.

Start with the wider context in the Page Panels area so the next control makes sense in the full workflow. In the next step, you will focus on Toolbar and see how it fits into this area.

Use the toolbar to filter requests, clear the list, and control what you see. This step matters because Toolbar is part of the Network panel, and understanding that context makes the next action easier to repeat in your own project.

Right-click a request to access actions like copying URLs or opening in a new tab. This step matters because Request context menu is part of the Network panel, and understanding that context makes the next action easier to repeat in your own project.

Expand a request node to inspect request/response headers, body, and timing. This step matters because Tree details is part of the Network panel, and understanding that context makes the next action easier to repeat in your own project.

Learn how to bind a property in the Selection panels. Use this tour as a quick refresher.

Property binding makes more sense when you first see where selection and data-aware editing meet. This how-to starts from that context, then explains why opening the right panel is the key step before you connect an element property to dynamic data.

Find the property you want to bind for the selected element.

Use a dynamic data value so it updates automatically. This step matters because Pick a dynamic value is part of the Properties panel, and understanding that context makes the next action easier to repeat in your own project.

Learn how to adjust layout in the Selection panels. Use this tour as a quick refresher.

Layout adjustments become easier when you begin from the selection surfaces that expose the right controls in context. This how-to starts there, then shows how selecting the right element and opening the correct panel keeps layout changes intentional instead of trial and error.

Use the Design panel controls to tweak layout-related settings for the selected element.

Check the result on the selected element in the editor.

Learn how to apply classes in the Selection panels. Use this tour as a quick refresher.

Applying classes is safer when you start from the selection workflow that makes the target element explicit. This how-to begins with that panel context, then explains how class changes fit into everyday page editing without losing track of which element you are styling.

Add one or more classes to the selected element.

Create overrides to customize styles without leaving the editor. This step matters because Override styles is part of the Styles panel, and understanding that context makes the next action easier to repeat in your own project.

Learn how to inspect data in the Selection panels. Use this tour as a quick refresher.

Inspecting data from a selected element works best when you understand the handoff between the page surface and the data tools. This how-to begins with that opening move, then shows how selection gives the Data Panel the context it needs for meaningful inspection.

Browse datasets and values available for the selected element.

Confirm you are inspecting the correct data for the current selection. This step matters because Verify scope is part of the Data panel, and understanding that context makes the next action easier to repeat in your own project.

Explore HTML Editor Inspector Panel: key areas and how they work together.

The inspector is where the currently selected element exposes its editable settings in a practical, property-driven layout. This overview explains why that matters, where the panel fits in the HTML Editor workflow, and how the focused how-to tours build on this same surface.

Use the toolbar to filter properties, open help, and access panel options.

Edit the selected element’s properties using the controls in the Inspector. This step matters because Inspector controls is part of the Properties panel, and understanding that context makes the next action easier to repeat in your own project.

Goal-based how-to guides for the Inspector panel, including selection and editing common attributes.

Use this menu when the inspector problem you have is specific and repeatable rather than broad and conceptual. It gathers the common inspector tasks in one place, so you can start from the job you need to complete and jump into the focused walkthrough that matches it.

Choose a walkthrough.

Find your way around HTML Editor Inspector Panel: where to find the main controls and what they do.

This setup step selects the page body so the Inspector reference shows populated controls.

Treat this reference tour as a map of the inspector before you rely on it for fast element edits. It highlights the groups and controls you revisit most often, explains what each part is responsible for, and helps you remember where to return when a property needs review.

Use Filter to find controls, Help for guidance, and the menu for more options. This step matters because Toolbar is part of the Properties panel, and understanding that context makes the next action easier to repeat in your own project.

Right-click controls or groups for additional actions. This step matters because Context menu is part of the Properties panel, and understanding that context makes the next action easier to repeat in your own project.

Controls are grouped by category. Changes apply to the currently selected element. This step matters because Inspector body is part of the Properties panel, and understanding that context makes the next action easier to repeat in your own project.

Explore HTML Editor Design Panel: key areas and how they work together.

The Design Panel is where selected elements expose their editable visual properties in a structured way. This overview explains what the panel is for, how it supports everyday page editing, and why later how-to tours build on this surface instead of sending you straight into raw markup.

Use the toolbar to filter, change modes, and access panel actions.

Adjust layout and presets for the current selection. This step matters because Design controls is part of Selection Panels Design Toolbar, and understanding that context makes the next action easier to repeat in your own project.

Goal-based how-to guides for the Design panel, from inserting elements to configuring properties.

Choose a walkthrough.

Find your way around HTML Editor Design Panel: where to find the main controls and what they do.

Treat this reference tour as a map of the Design Panel before you rely on it for fast edits. It points out the areas and controls you revisit most often, explains what each part is responsible for, and helps you remember where to return when a property change is needed.

The toolbar provides filtering, options, and access to help/tours. This step matters because Toolbar is part of Selection Panels Design Toolbar, and understanding that context makes the next action easier to repeat in your own project.

Right-click controls for additional actions. This step matters because Context menu is part of Selection Panels Design Toolbar, and understanding that context makes the next action easier to repeat in your own project.

Controls may change depending on what you select in Design View. This step matters because Panel body is part of Selection Panels Design Toolbar, and understanding that context makes the next action easier to repeat in your own project.

Explore HTML Editor Styles Panel: key areas and how they work together.

The Styles panel is where visual decisions become traceable CSS rules instead of vague design changes. This overview explains what the panel is for, how it supports everyday styling work, and why the focused how-to tours build on it for search, cloning, source jumps, and rule creation.

Search rules, toggle overloaded styles, add new rules, and refresh.

Browse rules affecting the selection and tweak values.

Goal-based how-to guides for the Styles panel, including inspection, rules, and jumping to source.

Choose a walkthrough.

Reference tour for the Styles panel: panel layout, styling controls organization, CSS rules inspection, and how to apply and debug styles.

Treat this reference tour as a map of the Styles panel before you depend on it for faster CSS work. It highlights the areas and controls you revisit most often, explains what each one is responsible for, and helps you remember where to return when styling needs inspection or change.

Search, toggle overloaded styles, add rules, refresh, and open help/tours.

Rule menus let you clone, remove, or jump to source. This step matters because Rule menus is part of the Styles panel, and understanding that context makes the next action easier to repeat in your own project.

Edit values to update the selected element’s styling. This step matters because Rule values is part of the Styles panel, and understanding that context makes the next action easier to repeat in your own project.

Explore HTML Editor Data Panel: key areas and how they work together.

The Data Panel shows the live values flowing through your page while you preview and test it. This overview explains why that matters for understanding bindings, where the panel fits in the HTML Editor, and how it supports the deeper inspection tasks covered in the focused how-to tours.

Refresh the view and access help/tours.

Inspect datasets and values that are available for the current selection.

Goal-based how-to guides for the Data panel, including sources, bindings, and pickers.

Choose a walkthrough.

Find your way around HTML Editor Data Panel: where to find the main controls and what they do.

Use this reference tour as a map of the Data Panel before you depend on it for debugging. It highlights the areas you revisit while inspecting live values, explains what each part is responsible for, and helps you remember where to return when a binding behaves unexpectedly.

Refresh updates the view; Help provides guidance and tours.

Right-click items for additional actions like copy. This step matters because Context menu is part of the Data panel, and understanding that context makes the next action easier to repeat in your own project.

Expand items to inspect nested structures and values. This step matters because Tree and values is part of the Data panel, and understanding that context makes the next action easier to repeat in your own project.

Learn how to select elements in Design View. Use this tour as a quick refresher.

Selection is the basic action that makes every later panel change meaningful. This how-to begins with the click target in Design View, then explains how choosing the right element anchors the rest of the editing workflow and prevents you from changing the wrong part of the page.

Use the Design toolbar to help with selection and editing.

Learn how to insert component in Design View. Use this tour as a quick refresher.

Start with the wider context in the Structure panel so the next control makes sense in the full workflow. In the next step, you will focus on Insertion target and see how it fits into this area.

We’ll select the element you want to insert into (for example body) in the App Structure. This step matters because Insertion target is part of Page Panels Structure Body, and understanding that context makes the next action easier to repeat in your own project.

We’ll open the Structure context menu for the selected element. This step matters because Context menu is part of Page Panels Structure Body, and understanding that context makes the next action easier to repeat in your own project.

We’ll use Insert Child to open the Components picker. This step matters because Insert picker is part of Page Panels Structure Body, and understanding that context makes the next action easier to repeat in your own project.

Search for a component and insert it. This step matters because Search and insert is part of Components Popup Anchor Right, and understanding that context makes the next action easier to repeat in your own project.

Learn how to use Split view in Design View. Use this tour as a quick refresher.

Using Split from Design View is about keeping visual feedback and source context connected while you work. This how-to begins with the switch control itself, then explains how the combined layout helps you verify selections, inspect markup, and move faster between intent and implementation.

Edit in Code and verify the result in Design.

Learn how to toggle App Connect in Design View. Use this tour as a quick refresher.

Toggling the App Connect overlay is useful when you need to change how much reactive information is visible on the canvas. This how-to starts from the toolbar switch, then shows why the toggle helps you move between cleaner visual editing and deeper reactive inspection.

When enabled, App Connect overlays can help visualize bindings.

Learn how to reload in Design View. Use this tour as a quick refresher.

Reloading Design View is useful when the rendered canvas no longer matches the current page state or recent change. This how-to starts from the toolbar control, then explains when a refresh is the right move and how it helps you confirm that the canvas is showing current output.

After reload, verify your canvas and selection.

Learn how to find in Code View. Use this tour as a quick refresher.

Finding text is one of the quickest ways to orient yourself in a large page before making a change. This how-to starts by locating the Find control in Code View, then shows why it matters for navigation, review, and fast corrections inside the HTML Editor.

Step through matches to reach the section you want.

Learn how to replace in Code View. Use this tour as a quick refresher.

Replace becomes powerful when you understand where it lives and when to trust it. This how-to starts from the Code View control itself, then frames the workflow you use for safe repeated edits, quick naming cleanup, and small refactors that should stay inside the current file.

Replace carefully and verify the result.

Learn how to go to line in Code View. Use this tour as a quick refresher.

Go to Line is the quickest bridge between a known location and the exact code you need to inspect. This short how-to places the command in context, then shows why it is useful when an error message, copied reference, or teammate points you to a specific part of the file.

Confirm to move the cursor and focus the editor at that position.

Learn how to format code in Code View. Use this tour as a quick refresher.

Formatting code is not just about aesthetics; it is what makes structure readable before you debug or refactor. This how-to shows where the formatting command lives in Code View and why using it early helps you read hierarchy, attributes, and nested markup more confidently.

Review the changes before saving.

Learn how to use Split view in Code View. Use this tour as a quick refresher.

Split view matters when you need code context and visual feedback at the same time. This how-to shows where to switch into the mixed layout, why it helps you verify edits faster, and how it fits into the normal back-and-forth rhythm of building pages in Wappler.

Make edits in Code and verify them in Design.

Learn how to find an element in the App Structure panel. Use this tour as a quick refresher.

Finding something in Structure matters because fast navigation keeps larger pages manageable. This how-to starts with that goal in mind, then explains how the tree helps you jump to the right element before you inspect it, move it, or change related properties elsewhere in the editor.

Type into the search box to filter the element tree. This step matters because Search the tree is part of the Structure panel, and understanding that context makes the next action easier to repeat in your own project.

Pick the element you want from the filtered tree. This step matters because Select the result is part of the Structure panel, and understanding that context makes the next action easier to repeat in your own project.

You can repeat this anytime to quickly locate elements. This step matters because Done is part of the Structure panel, and understanding that context makes the next action easier to repeat in your own project.

Learn how to insert an element in the App Structure panel. Use this tour as a quick refresher.

Insertion from Structure works best when you first understand the tree as a map of valid placement points. This how-to starts from that idea, then explains how choosing the correct node keeps new content organized and reduces cleanup after the component is added.

Right-click an element to access Insert options. This step matters because Open the context menu is part of the Structure panel, and understanding that context makes the next action easier to repeat in your own project.

Pick Insert Before, Insert After, or Insert Child depending on where you want the new element.

Use Insert Child when you want to nest the new element.

Learn how to duplicate an element in the App Structure panel.

Duplicating from Structure is easiest when you think of the tree as a safe way to act on the exact node you need. This how-to frames that goal first, then shows how duplication fits into normal editing when you want to preserve existing setup and repeat a similar element.

Use the context menu Duplicate action on the selected element. This step matters because Duplicate from the tree is part of the Structure panel, and understanding that context makes the next action easier to repeat in your own project.

Look for the new element in the tree, then rename or adjust it as needed.

If you duplicated the wrong element, use Undo and try again.

Learn how to move content to a separate file in the App Structure panel.

Moving content to a file is easier when you first see the structure tree as the place where reuse decisions begin. This how-to frames the goal in context, then shows why the correct source node matters before you turn a piece of page structure into a reusable file.

Right-click the element and use Move to Separate File. This step matters because Move to Separate File is part of the Structure panel, and understanding that context makes the next action easier to repeat in your own project.

Follow the prompt to name the file and confirm the action.

This is useful for shared sections like headers, footers, or repeated blocks.

Learn how to manage frameworks & visibility in the App Structure panel.

Framework-related structure choices are easier to understand when you first see how the page tree reflects the components Wappler manages for you. This how-to frames that connection, then shows why recognizing framework-aware nodes helps you edit with more confidence.

Use Show All to display elements that might be hidden or filtered by framework rules. This step matters because Show all elements is part of the Structure panel, and understanding that context makes the next action easier to repeat in your own project.

Use Manage frameworks to enable/disable framework-specific features and element sets. This step matters because Manage frameworks is part of the Structure panel, and understanding that context makes the next action easier to repeat in your own project.

If the tree looks incomplete, try Show All first. This step matters because Done is part of the Structure panel, and understanding that context makes the next action easier to repeat in your own project.

Learn how to filter properties in the Inspector panel. Use this tour as a quick refresher.

Filtering the inspector is useful when the available fields are broader than the change you have in mind. This how-to begins with the filter control itself, then explains how narrowing the visible options helps you reach the right setting faster and with less guesswork.

Clear the filter to return to the full list of controls.

Learn how to edit a property in the Inspector panel. Use this tour as a quick refresher.

Editing through the inspector is easier once you see it as the direct-property side of element selection. This how-to starts from the selected element context, then shows how the inspector helps you make precise adjustments without losing track of what part of the page you are changing.

Update the value. Wappler applies it to the current selection.

Learn how to navigate the inspector in the Inspector panel. Use this tour as a quick refresher.

Inspector navigation matters because the panel is only useful if you can quickly reach the right group of settings. This how-to starts with the grouping model itself, then shows how moving between sections helps you understand where each kind of property belongs.

Scroll to find controls. Combine with Filter for faster navigation.

Learn how to refresh the inspector in the Inspector panel. Use this tour as a quick refresher.

Refreshing the inspector is helpful when the current fields no longer match the selected element or recent change. This how-to begins at the refresh action itself and shows why reloading the panel is the fastest way to restore trust in what the inspector is displaying.

Learn how to open Inspector tours in the Inspector panel. Use this tour as a quick refresher.

Knowing how to reopen tours from the inspector keeps help close to the workflow instead of forcing you to break context. This how-to starts with the tours entry point, then explains why using in-place guidance is often faster than hunting through menus when you need a reminder.

Learn how to filter properties in the Design panel. Use this tour as a quick refresher.

Filtering the Design Panel matters once the available controls become too noisy to scan by eye. This how-to starts with the filter field itself, then explains how narrowing the list helps you reach the right property faster when you already know the kind of change you want.

Only matching controls remain visible in the panel. This step matters because Filtered results is part of Selection Panels Design Toolbar, and understanding that context makes the next action easier to repeat in your own project.

Learn how to use a pseudo-state in the Design panel. Use this tour as a quick refresher.

State controls matter because many design changes only make sense in a specific interaction or responsive condition. This how-to starts by locating the state control in context, then shows why changing state is the key to previewing hover, active, or alternate visual conditions safely.

Changes apply to the selected state and help you fine-tune interactions. This step matters because Edit within the state is part of Selection Panels Design Toolbar, and understanding that context makes the next action easier to repeat in your own project.

Learn how to switch the selector in the Design panel. Use this tour as a quick refresher.

The selector helper becomes valuable when you need to understand exactly which rule or target you are editing. This how-to begins in the Design Panel context, then explains how choosing the correct selector changes the scope of your edits and avoids unintended styling drift.

Update values and verify the results in Design View. This step matters because Edit the chosen selector is part of Selection Panels Design Toolbar, and understanding that context makes the next action easier to repeat in your own project.

Learn how to edit a property in the Design panel. Use this tour as a quick refresher.

Editing a property is easier when you first recognize the panel as the place where visual choices become structured settings. This how-to begins by locating the Design Panel in context, then shows how a single property edit influences the selected element in the page workflow.

Edit a property in the Design panel and verify the result.

Learn how to refresh the panel in the Design panel. Use this tour as a quick refresher.

Refreshing the Design Panel is useful when the current property list no longer matches the element or state you expect. This how-to shows where the refresh action lives and why it helps you re-synchronize the panel before you keep editing the selected element.

The panel re-evaluates its controls for the current selection. This step matters because Verify is part of Selection Panels Design Toolbar, and understanding that context makes the next action easier to repeat in your own project.

Learn how to search styles in the Styles panel. Use this tour as a quick refresher.

Searching styles is the quickest way to narrow a large stylesheet down to the rule or selector you care about. This how-to frames that goal first, then shows how the search control helps you move from broad visual intent to a specific rule faster.

Only matching rules remain visible.

Learn how to toggle overloaded styles in the Styles panel. Use this tour as a quick refresher.

Overloaded styles only make sense once you understand that more than one rule can compete to style the same element. This how-to starts from the panel control in context, then explains why toggling that view helps you debug cascade conflicts and inheritance more confidently.

The list updates to hide or show overloaded entries.

Learn how to insert a new rule in the Styles panel. Use this tour as a quick refresher.

Adding a new rule is easier when you first understand where the Styles panel expects structural changes to begin. This how-to starts from that insertion point, then explains how creating a rule in the right place keeps the stylesheet easier to scan and maintain later.

Select an element in Design View to apply the rule to the intended target.

Learn how to jump to CSS source in the Styles panel. Use this tour as a quick refresher.

Jumping to source matters when a visual style decision needs direct code inspection or a broader stylesheet change. This how-to begins with the panel control itself, then shows why tracing a rule back to its source is the fastest way to understand where the styling really lives.

Editing the CSS directly gives you precise control. We’ll open the source so you can make targeted changes.

Learn how to clone a rule in the Styles panel. Use this tour as a quick refresher.

Cloning a style rule is useful when you want to reuse a working pattern without rebuilding it from scratch. This how-to starts with the menu entry in context, then explains why copying a rule is often safer than editing the original when you need a nearby variation.

A new rule appears that you can customize without changing the original.

Learn how to refresh data in the Data panel. Use this tour as a quick refresher.

Refreshing the Data Panel is useful when the current values no longer match what you expect after an interaction. This short how-to shows where the refresh action lives and why it is the fastest way to confirm whether the data source changed or the panel is showing stale state.

The Data panel updates to reflect the latest state.

Learn how to select an element to inspect data in the Data panel.

Selecting the right element or node is what turns the Data Panel from a broad overview into a precise inspection tool. This how-to places that action in context and shows how it helps you connect a specific part of the page to the data it is currently using.

Open the Data panel to see datasets for the new selection.

Learn how to expand datasets in the Data panel. Use this tour as a quick refresher.

Expanding the data tree is the first step to understanding what values are actually available during preview. This how-to shows where that interaction starts in the Data Panel and why opening the right branch is what makes deeper debugging and inspection possible.

Keep expanding until you reach the values you need.

Learn how to explore large arrays in the Data panel. Use this tour as a quick refresher.

Large arrays can feel unreadable until you know how the Data Panel exposes them in manageable pieces. This how-to explains where to start, what to expect when a result set is big, and how chunked inspection helps you debug data without getting lost in volume.

If possible, filter at the source (queries/formatters) to keep results manageable.

Learn how to inspect values in the Data panel. Use this tour as a quick refresher.

Inspecting values is how the Data Panel becomes a debugging tool instead of a tree of labels. This how-to begins with the right place to expand data, then frames how to confirm current values, understand scope, and spot problems in bindings while the page is running.

Copy values or use them for bindings/conditions.