How to Use Deep Woods Studio

Studio is Deep Woods' visual editor. It's where you build and update everything visitors see on your site — text, images, links, colors, fonts, and page layout — without writing code or waiting on a developer. You edit directly on a live preview of your page; when you're happy with a change, you publish it and it goes live.

Deep Woods Studio visual editor

1. Understanding your plan tier

Your Deep Woods plan is based on how many pages your site has:

Tier Pages What it means Landing Pages 1 A single, focused page — a landing page, announcement, or launch page. Microsites 2–5 A small multi-page site with shared navigation and branding. Managed Apps 6+ A full, growing web presence with many pages and sections.

Growing from a Landing Page into a Microsite happens automatically as you add pages — there's no migration step and nothing to rebuild. Growing past the Microsite limit into Managed Apps keeps your project exactly as it is, but does require switching to a Managed Apps plan, since that tier is priced and supported differently for a larger site. Either way, everything you've already built in Studio carries forward as-is.

2. Getting into Studio

Log in to your Deep Woods account.
Open your site from your dashboard.
Select Studio to enter the visual editor.

Studio shows your site's live preview alongside an editing panel. Click anything highlighted in the preview to edit it — the panel updates with the fields available for that section.

3. How a page is built

A page in Studio is a stack of sections. Each section is a self-contained, pre-designed piece of the page — a hero banner, a feature grid, a pricing table, an FAQ accordion, and so on — that you fill in with your own content. You never design a section from scratch; you only supply the words, links, images, and colors.

Building a page from sections

When you add a section, Studio groups the options into three sets so they're easier to find:

Group What it's for Starter Blocks The building blocks you'll reach for constantly: a general-purpose section, a hero, and a standalone button. Page Blocks Structural, content-rich sections built for full pages: hero banners, stats, feature/testimonial cards, logo strips, call-to-action bands, and layout helpers for custom multi-column pages. Marketing Blocks Sections aimed at marketing/landing pages: pricing tables, FAQ accordions, testimonials, and footer variants.

A few sections worth knowing by name as you build:

Hero — your page's opening banner: headline, supporting line, and one or more buttons, with an optional badge, logo, and image.
Page CTA — a full-width call-to-action band, usually placed near the bottom of a page.
Feature Grid / Stats / Testimonials — grids of cards, numbers, or quotes, each built from a simple list you fill in.
Pricing Plans — one or more pricing cards side by side.
FAQ — a question/answer accordion, just like this page.
Logos strip — a row of partner or customer logos, optionally scrolling.

Two things live outside a page's section stack, and are edited separately:

Settings — brand-wide values (site name, logo, colors, fonts, navigation, footer, social links) that apply to every page at once. See section 9.
Media — your uploaded images and files. See section 8.

4. Editing an existing section

In the preview, click the section you want to change. It will highlight to show it's selected.
The editing panel opens on the side with that section's fields (e.g. headline, subtitle, button label, button link, icon).
Update the fields — the preview updates instantly so you can see exactly how it will look.
Save your changes.

Common things you can edit on any section:

Headlines, body copy, and captions
Button labels and destinations (another page, an anchor on the same page, or an external link)
Icons and images
Colors and layout options specific to that section (e.g. left/right orientation)

Prefer writing Markdown or a CMS view?

Most edits happen through Studio's visual fields, but longer-form content — a blog post, a detailed guide, a documentation page — can also be written directly as Markdown, or edited through a CMS-style content view if you prefer that to filling in individual fields. A section's raw content view is also where a handful of advanced, fine-grained style tweaks live — things like an unusual text size or spacing that don't have their own visual field yet. You won't need this for day-to-day editing, but it's there if you want finer control on a specific section. Either way, your content publishes through the same staged review flow as everything else in Studio.

5. Adding, removing, and reordering sections

Pages are built from a stack of sections. You can customize that stack per page:

Open the page you want to change in Studio.
Use Add Section to insert a new section from the component library (see section 3).
Drag a section up or down to reorder it on the page.
Use Remove on a section to delete it from the page.

Every section you add is already fully designed and on-brand — you only need to fill in your content, not design it from scratch.

One common point of confusion: your site's footer — the copyright line, legal links, and social icons at the bottom of every page — always comes from Settings (see section 11), not from a section on the page. The Footer section you'll see in the component library is a different thing: a footer-shaped block of content you can drop into the middle of a page (handy for a standalone page with the header and footer hidden — see section 7). If your site has its normal header and footer showing, you generally won't need it.

6. Creating a new page

From your site's page list in Studio, select New Page.
Give it a title and a URL path (e.g. /about, /pricing).
Build the page by adding sections, just like any other page (see section 5).
Review the page's own settings (see section 7) — most pages can leave these as-is, but a standalone landing page often wants a couple changed.
Publish the page when it's ready.

Reminder: adding pages within your current tier's limit is automatic. If a project needs to grow past the Microsite limit (currently 5 pages), publishing further pages requires upgrading it to Managed Apps first.

7. Every page's settings

Separately from its sections, every page has its own settings panel:

Setting What it does Title Used as the page heading and, unless overridden by Description, the browser tab / search result title. Description Used for search results and social share previews. Hide header Removes the site's shared header/navigation from this page. Hide footer Removes the site's shared footer from this page. Hide both this and Hide header for a full, chrome-free page — useful for a campaign page or one-off page that shouldn't look like the rest of the site. Page background A background (and optionally text) color for the whole page. Leave blank to follow your brand's theme. Heading font / Body font Overrides your site-wide fonts (see section 9) for this one page only. Draft Hides the page from visitors without deleting it — use this while a page is still being built.

8. Adding media: images, logos, and your favicon

Studio has a dedicated Media tab for anything you upload — hero images, logos, testimonial photos, and your favicon (the small icon shown in a browser tab).

Open the Media tab in Studio.
Upload an image file. Once uploaded, it appears in your media list and can be referenced from any image field on any section.
To use an uploaded image, select it from an image field's picker, or copy its path and paste it into the field directly.

A few things worth knowing:

You can also use a fully external image URL directly in any image field — you don't have to upload it to Media first.
Icons are text, not uploads. Fields like a button's icon or a feature card's icon use icon names, not image files. Wherever an icon field appears, look for a “Browse icons” link to find the exact name for the icon you want.
Favicon: replace your favicon directly from Media. Use a .png or .svg file rather than .ico — an .ico file still works correctly as the actual browser-tab icon, but Studio's Media list can't generate a thumbnail preview for that format, so it'll look broken in the list even though it's working everywhere else.
Once you reference an uploaded file from a section, it's part of that section's saved content, the same as any text field — no separate step needed to “attach” it.

9. Customizing your brand

Brand settings apply site-wide, across every page and every section, so you only set them once:

In Studio, open Settings.
Update:
- Site name — shown in your header and footer.
- Site description — used for search engines and link previews.
- Logo icon — shown next to your site name in the header.
- Primary color — your main brand accent color, used on buttons and highlights.
- Neutral color — your background/text gray scale.
- Heading font and body font — applied across all text on your site.
Save. Every page updates automatically — no need to touch each page individually.

10. Managing navigation

Your site's header menu is fully editable:

In Settings, find Navigation.
Add, remove, or reorder menu items. Each item needs:
- A label (what visitors see).
- A link, which can be:
  - An anchor on the current page (e.g. #features)
  - A path to another page on your site (e.g. /about)
  - A full external URL (e.g. https://example.com) — turn on Open in new tab for these.
Save. The menu updates in both the desktop and mobile navigation automatically.

Still under Settings:

Footer links adds a row of legal/quick links (Privacy Policy, Terms, etc.) next to the copyright line.
Social links — add each profile with a label, a URL, and an icon. These appear automatically as icons in your site's footer.

12. Reviewing and publishing changes

Changes you make in Studio are staged first, so nothing goes live by accident:

Publishing workflow: staged review to live

Make your edits across any pages or settings.
Use the preview to confirm everything looks right.
Select Publish to push your changes live.

Until you publish, your live site keeps showing the previous, published version — so you can take your time and make multiple edits before going live.

13. Before you launch

Every new Deep Woods site starts from the same demo homepage and settings, so it's fast to see a real page working right away. Before you send visitors to it, walk through this checklist so nothing placeholder is still showing:

Site name, description, logo, colors, and fonts (Settings) match your brand, not the starting template.
Navigation (Settings) points at your real pages/sections, not the demo links.
Your homepage hero has your own headline and photography, not the starting copy and stock image.
Stats, testimonials, and pricing sections show your own numbers and quotes, not sample placeholders.
Footer text, footer links, and social links (Settings) point at your real profiles.
Favicon (Media) is your own icon.
Any extra demo/test pages are deleted or marked Draft.

None of this is required to use Studio — a fresh site is fully functional the moment you get access. It's only worth checking before you send visitors to it.

14. Troubleshooting

Preview looks stale after an edit → do a hard refresh of the Studio tab itself, not just the preview pane.
Header, footer, or background looks wrong on one specific page, but not the others → check that page's own settings (section 7) before assuming it's a site-wide (Settings) problem, or vice versa — this is the most common source of “it changed on one page but not the others” confusion.
A field I just added doesn't show up → some structural changes need a moment to propagate; if it still doesn't appear after a refresh, contact your Deep Woods contact.

15. Frequently asked questions

Do I need any technical or design skills to use Studio? No. Every field is a simple form input — text boxes, dropdowns, color pickers, and icon pickers. Sections are already designed; you only supply the content.

Can I break my live site by editing in Studio? No. Edits are staged and previewed before you publish, so you can review any change before it's visible to visitors.

What happens when I add more pages than my current tier allows? Growing from a Landing Page into a Microsite happens automatically. Growing past the Microsite limit into Managed Apps keeps your project and content exactly as they are, but requires upgrading to a Managed Apps plan first — see Managed Apps.

Can I make one page look completely different from the rest of my site? Yes. Use that page's own settings (section 7) to hide the header and footer, set a different background, or override the fonts — without affecting any other page.

Who manages hosting, uptime, and security? Deep Woods does, entirely. There's nothing for you to configure or maintain outside of Studio.

Can multiple people on my team use Studio? Yes — your team edits the same site collaboratively through Studio, with changes staged before publishing.

I'd rather write my own application code — is that an option? Yes. Servers is for teams who want to bring their own code instead of building visually in Studio — connect a repository in a supported framework and Deep Woods handles hosting it.