{
  "lang_dir": "ltr",

  "nav_features":      "Features",
  "nav_how":           "How It Works",
  "nav_faq":           "FAQ",
  "nav_pricing":       "Pricing",
  "nav_terms":         "Terms of Service",
  "nav_privacy":       "Privacy Policy",
  "nav_refund":        "Refund Policy",
  "nav_cmp_jira":      "Vi vs Jira",
  "nav_cmp_linear":    "Vi vs Linear",
  "nav_cmp_git":       "Git Project Management",
  "nav_cmp_vscode":    "VS Code Project Management",
  "nav_cmp_gantt":     "Gantt Charts",
  "nav_cmp_cnc":       "Commit & Close",
  "nav_cmp_ide":       "IDE Project Management",
  "nav_cmp_rad":       "RAD Studio Project Management",
  "nav_cmp_vs":        "Visual Studio Project Management",
  "btn_login":         "Login",
  "btn_signup":        "Sign Up",
  "landing_cta_start": "Get Started Free",
  "landing_footer_desc": "Git-aware project execution for software teams — where tasks, workflows, and Git stay in sync.",
  "landing_copyright": "© 2026 Vi Project Manager. All rights reserved.",

  "vst_badge":        "Visual Studio",
  "vst_h1":           "Project management for Visual Studio teams",
  "vst_sub":          "Vi connects Visual Studio workflows with tasks, Git, and project boards — so developers finish work in the IDE and the board updates itself.",
  "vst_status_badge": "Visual Studio extension — In Testing",
  "vst_cta_pricing":  "See Pricing",

  "vst_problem_h": "Why Visual Studio teams need project management closer to the IDE",
  "vst_problem_p": "Visual Studio developers live in solutions, branches, and debug sessions — not in a browser tab. Every ticket update means leaving the IDE, finding the right work item, and clicking through forms. That's why boards drift out of date and standups turn into status interviews. Vi moves the task workflow to where the work happens, and keeps the board in sync with Git.",

  "vst_cnc_h":     "The Commit & Close workflow",
  "vst_cnc_p":     "With Commit & Close, a developer marks a task Done from the IDE and Vi stages the changes, creates a task-aware commit, pushes to Git, closes the task, and updates the project board automatically. The Visual Studio extension — a task panel plus Commit & Close — is built and currently in testing before general release.",
  "vst_cnc_learn": "See how Commit & Close works →",

  "vst_today_h":   "What Visual Studio teams can use today",
  "vst_today_sub": "The full Vi web app is available now — no extension required:",
  "vst_today_1t":  "Tasks, projects & boards",
  "vst_today_1d":  "Web-based task and project management with List, Kanban, Gantt, and Portfolio views.",
  "vst_today_2t":  "Custom workflows & approvals",
  "vst_today_2d":  "Custom workflow steps with per-step approval chains — nothing ships without sign-off.",
  "vst_today_3t":  "AutoAssign & time tracking",
  "vst_today_3d":  "Workload-based auto-assignment plus a built-in timer, so estimates and reality stay connected.",
  "vst_today_4t":  "One active task per developer",
  "vst_today_4d":  "Vi's focus rule keeps each developer on one In Progress task at a time — the board always shows real work.",

  "vst_roadmap_h": "Current status: In Testing",
  "vst_roadmap_p": "The Vi extension for Visual Studio is feature-complete and in testing before general release. Teams can start with the web app today; the in-IDE experience follows once testing wraps up. We publish honest statuses — Available means available.",

  "vst_sec_h": "Your source code stays yours",
  "vst_sec_p": "When using Vi IDE integrations, all Git operations run locally on the developer's machine. Vi never accesses, stores, or uploads source code — it orchestrates the task workflow, nothing more.",

  "vst_faq_h":  "Frequently asked",
  "vst_faq1_q": "Is the Visual Studio extension available?",
  "vst_faq1_a": "The Vi extension for Visual Studio is currently In Testing — built, functional, and being validated before general release. Teams can use the full Vi web app today.",
  "vst_faq2_q": "What does In Testing mean?",
  "vst_faq2_a": "The extension is feature-complete — task panel plus Commit & Close — and is going through testing before it's declared generally available. We publish honest statuses: Available means available.",
  "vst_faq3_q": "Can Visual Studio teams use Vi today?",
  "vst_faq3_a": "Yes. The full Vi web app is available now: task and project management, custom workflows with approval chains, AutoAssign, time tracking, and Git-aware execution.",
  "vst_faq4_q": "Does Commit & Close update the project board?",
  "vst_faq4_a": "Yes. When a developer marks a task Done, Vi creates a task-aware commit, pushes to Git, closes the task, and the project board updates automatically.",
  "vst_faq5_q": "Does Vi store source code?",
  "vst_faq5_a": "No. When using Vi IDE integrations, Git operations run locally on the developer's machine. Vi never accesses, stores, or uploads source code.",

  "vst_explore_lead": "Keep exploring:",
  "vst_explore_cnc":  "Commit & Close",
  "vst_explore_ide":  "IDE project management",
  "vst_explore_git":  "Git-aware project management",
  "vst_explore_jira": "Vi as a Jira alternative",

  "vst_cta_h":   "Keep your board as current as your code",
  "vst_cta_sub": "Start free in the web app today — the Visual Studio extension follows once testing completes."
}