Docs: Vibe project tags (VIBE-205)

[haleyserrano]

JIRA

https://vendasta.jira.com/browse/VIBE-205 — "Project tags: create/edit tags and tag-filtered project list" (Story, Done)

Classification

Feature behavior change / UI change — end users can now add free-form tags to a Vibe project and find tagged projects via the existing search box.

Repo targeted

Business App (this repo only). Vibe is a Business App feature; the Partner Center repo's docs/ai/vibe.md is a stub that only points readers to this Help Center, so no Partner Center update was needed.

Rollout check (Step 1.5)

VIBE-205 has no parent epic in JIRA — it's a standalone story, not linked under an Epic Link/parent field. The story itself is resolved Done, and its own JIRA comment thread confirms all six linked PRs (vendastaapis #9781; vibe #481, #482, #483; galaxy #33926, #33927) are merged, with the last comment (2026-08-20) describing the final, shipped behavior. No gating/rollout tickets were found to check against, since there's no epic. Proceeding was reasonable given the above, but there was no way from this repo's scope to independently confirm production deploy status of vibe#482/#483 (their own PR descriptions reportedly gate on a post-deploy verification step) — noted as an assumption below.

What changed

Updated two existing pages under docusaurus/docs/business-app/ai/vibe/ — no new page created, since this is a small addition to an already-documented settings/search surface:

• getting-started.md — added a "Tags" subsection under "Understanding the Interface": how to add tags (Project Settings → Overview section), the lowercase/hyphenated normalization, and that the projects-list search box matches tags too.
• index.md — added a "Tags" entry to the Key Features list, linking to the new subsection above.

Placement reasoning

Tags are edited from the same Project Settings "Overview" area where the project name/description already live (per the existing connectors/index.md and guides/business-knowledge.md docs, which already describe that panel as "Project Settings" with a "Configure" entry point and an "Overview" card). Adding a short subsection there — rather than a new page — keeps this consolidated with where users already learn about that panel, per the "prioritize updating existing docs" step.

Acceptance criteria coverage

Based on the JIRA description and the final revision comment:

• ✅ Tags editable per-project, autosaved like name/description → documented (Project Settings → Overview)
• ✅ Tags normalized to lowercase, spaces → hyphens → documented, with the ticket's own example ("Client Work" → client-work)
• ✅ Tags searchable from the projects list → documented (existing search box now also matches tags)
• ➖ Not documented: the server-side ListProjects tags filter (ES7-backed) — per the ticket's final revision comment, this shipped as API capability only, with no UI consumer in v1 (the standalone tag-filter control was dropped for v1). Since it isn't reachable from the product, it isn't documented as an end-user feature.
• ➖ Not documented: setting tags at project-creation time — the JIRA notes say this is possible at the proto/API level, but neither the ticket nor its comments describe a tags field being added to the create-project dialog UI, so no such claim was made.

Figma / images

None were provided on the ticket. No new screenshot was added — the existing img/project-settings.png (used in connectors/index.md) predates this feature and doesn't show the tags field, so it wasn't reused for this change.

Skills used

None of the repo's generation skills applied directly (this was a small update to existing pages rather than new-article generation), so this followed pre-push-validation and the style-review scan script (scan-style.sh) manually before pushing — both passed with no new critical/build-safety issues; the only warnings are pre-existing patterns already used throughout both files (em dashes, missing sidebar_label/description).

Assumptions / limitations

• Reviewer: this session's GitHub access is scoped to vendasta/businessapp-docs and vendasta/partnercenter-docs only, so the linked PRs (in vendastaapis, vibe, and galaxy) could not be opened to positively identify the authoring developer's GitHub handle for a reviewer request. JIRA shows Leo Melnyk as the story's sole assignee/reporter/commenter throughout implementation — recommend adding them as reviewer manually.
• The UI label for the tags editor's parent section is inferred as "Overview" (matching this repo's existing screenshot caption/terminology for that panel) rather than the ticket's internal dev term "General section" — no new screenshot was available to confirm the shipped label.

cc @ahnikakuse @haleyserrano @maryam6samadi

---

Generated by Claude Code