Creating and Organizing Projects and Boards

Projects and boards are the backbone of StretchWire. A project is the container for a body of work; boards are the screens inside it. This guide covers creating both, the fields that matter, and how to keep everything organized.

Before you start

Decide the scope of your project first. One website = one project. One mobile app = one project. A client with two separate sites = two projects. Each screen or page becomes a board inside that project. Getting this boundary right keeps your Boards list readable as the work grows.

Create a project

1. From the dashboard, click the Project quick-create tile, or open Projects and choose New project (or press C).
2. Enter a title — this is required (for example Acme Marketing Site).
3. Choose a project type — for example Website, Landing page, Mobile app, or Dashboard. The type drives sensible defaults and how the project is labeled.
4. Optionally set the client name (leave blank for internal work — it shows as Internal), a brand, a description, and internal notes.
5. Confirm. Your project is created and appears in the Projects list and Recent wireframes.

Project fields explained

• Title — the human name; required.
• Project key — a short slug (auto-generated from the title if you don't set one) used to reference the project.
• Type — website, landing page, portfolio, blog, mobile app, tablet app, dashboard, admin panel, email, newsletter, marketing site, pricing, user flow, sitemap, and more.
• Status — draft by default; move to active when it's in flight.
• Client name — who the work is for; blank = Internal.
• Brand — the brand this project belongs to.
• Description / internal notes — context for your team; internal notes are for private reminders.

Add boards to a project

1. Open the project, or go to the Boards view and choose New board.
2. Select the parent project.
3. Name the board after the screen — Home, Pricing, Checkout, Onboarding.
4. Pick a viewport mode (responsive, mobile, tablet, email, or canvas) — see Board settings and viewport modes.
5. Create. The board arrives preloaded with Desktop, Tablet, and Mobile frames and a starter hero block, ready for the canvas.

Board fields explained

• Title — the screen name; required.
• Board key — auto-generated slug for reference.
• Viewport mode — how the board is planned (responsive by default).
• Status — draft by default.
• Thumbnail — an optional preview image shown in lists.

Organize as work grows

• Name boards like a sitemap. Home, Features, Pricing, Contact reads clearly in the Boards list.
• Use status deliberately. Keep exploratory projects in draft; promote to active when the team commits.
• Fill in the client name. It turns a flat list into a filterable, client-organized workspace.
• Lean on Recent. The last board you edited stays at the top of Recent wireframes for a fast return.

Edit a project or board later

Projects and boards are fully editable. Reopen a project to change its title, type, status, client, or notes; reopen a board to change its title, viewport mode, status, or thumbnail. Changes save through the StretchWire service and update the last-updated timestamps that drive Recent and the overview.

Example

You're planning a site for a client named Acme. You create a project titled Acme Marketing Site, type Website, client Acme, status draft. Inside it you add four boards — Home, Features, Pricing, Contact — each on responsive. As you finalize scope, you switch the project to active. The Projects list now shows Acme Marketing Site · Acme · Website · 4 boards · Active.

Tips

• Set the project type at creation — it drives labels and downstream template choices.
• Don't over-split: keep one screen per board rather than cramming several pages onto one canvas.
• Use internal notes for scope reminders and open questions so context travels with the project.

Troubleshooting

"Project title is required." The title field is empty — every project needs a title before it can be created.

Create button is locked / says "Authorizing." You're on a gated surface. On the workspace surface, creating requires an active Pro entitlement; on admin, it needs step-up confirmation. See Access, entitlements, and organization scoping.

My new board has no frames. Every new board is seeded with Desktop, Tablet, and Mobile frames automatically — if you imported a document instead, its frames come from the imported JSON.