Configuring Project Details: Types, Statuses, Clients, and Notes

Every StretchWire project carries a set of details that make it findable, filterable, and clear to your team. Setting them well is the difference between a tidy workspace and a pile of untitled drafts. This article covers each field and how to use it.

Where project settings live

Project details are set when you create a project and can be edited anytime by reopening the project. They appear across the app — in the Projects table (title, client, type, brand, board count, status, updated) and in the overview counts on the dashboard.

Project type

The type classifies what the project is and drives sensible defaults and labeling. StretchWire recognizes a wide range, grouped by purpose:

• Websites — website, landing page, portfolio, blog
• Apps — mobile app, tablet app, dashboard, admin panel
• Marketing — email, newsletter, marketing site, pricing
• Docs & flows — user flow, sitemap, wireframe kit, component board
• Overlays — popup/overlay, modal

Choosing the right type at creation means the matching template and viewport defaults line up with your intent.

Status

Status tracks where a project stands:

• Draft — the default; early-stage, exploratory, or not yet committed.
• Active — in flight or approved for build; counts toward the Active metric on the dashboard.
• Archived — closed out; excluded from the active count so it doesn't clutter your live totals.

Use status intentionally so the overview's Active vs. Draft split reflects reality.

Client name and brand

• Client name — who the work is for. Set it and the Projects table groups the work by client; leave it blank and the project shows as Internal.
• Brand — the brand the project belongs to, useful when one organization manages multiple brands.

Description and internal notes

• Description — a short summary of the project's purpose, visible to the team.
• Internal notes — private reminders, scope caveats, and open questions that should travel with the project without being part of its public description.

Project key

Each project has a project key — a short, URL-safe slug auto-generated from the title if you don't supply one. It's a stable reference for the project even if the display title changes later.

Keep a tidy workspace

1. Title clearly — Acme Marketing Site, not New Project.
2. Set the type at creation so defaults and templates match.
3. Fill in the client so internal vs. client work is obvious.
4. Promote and archive deliberately — move committed work to active, and archive finished or abandoned projects so your counts stay honest.
5. Use internal notes for the context that would otherwise live in someone's head.

Example

An agency manages three clients. Each engagement is a project with the client name set, the type chosen (Website, Mobile app, Landing page), and a status that reflects its stage. The Projects table now reads like an account list — filterable by client, sortable by last update — and the dashboard's Active count shows exactly how many engagements are live.

Tips

• Standardize a naming convention across your team (Client - Project - Type) so lists stay scannable.
• Revisit draft projects periodically — promote the ones you've committed to and archive the rest.
• Put scope decisions in internal notes so future-you remembers why the structure is the way it is.

FAQ

Can I change a project's type after creating it? Yes. Reopen the project and update the type; the change saves immediately.

What's the difference between description and internal notes? Description summarizes the project for the team; internal notes are for private reminders and caveats.

Does archiving delete a project? No. Archiving just removes it from your active counts; the project and its boards remain.