{
  "lang_dir": "ltr",

  "nav_features":      "Features",
  "nav_how":           "How It Works",
  "nav_faq":           "FAQ",
  "nav_usecases":      "Use Cases",
  "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",
  "nav_cmp_gaware":    "What is Git-Aware PM?",
  "nav_cmp_security":  "Security & Trust",
  "nav_cmp_pilot":     "Run a Pilot",
  "btn_login":         "Login",
  "btn_signup":        "Sign Up",
  "landing_cta_start": "Get Started Free",
  "landing_footer_desc": "Vi is Git-aware project management for software teams — with IDE-based task execution, Commit & Close, workflow automation, approvals, time tracking, and real project visibility.",
  "landing_copyright": "© 2026 Vi Project Management. All rights reserved.",

  "ga_badge":  "Guide",
  "ga_h1":     "What is Git-aware project management?",
  "ga_sub":    "Git-aware project management keeps the project board in sync with real development work — commits, pushes, and workflow updates — instead of relying on developers to update tickets by hand.",
  "ga_cta_pricing": "See Pricing",
  "ga_hero_alt": "Diagram explaining what Git-aware project management is",

  "ga_def_h":  "A definition for software teams",
  "ga_def_p":  "Project management tools help teams plan work, assign tasks, and track progress. But for software teams, a big part of the real work happens somewhere else: inside the IDE — in Git branches, commits, pushes, and code changes. Git-aware project management closes that gap. It connects project tracking to real development activity, so tasks, commits, pushes, and workflow updates stay in sync — instead of treating tasks as isolated cards disconnected from the codebase.",

  "ga_prob_h": "The problem with traditional project boards",
  "ga_prob_p": "Most project management tools are built around manual updates. A developer works on a task, writes code, commits and pushes through Git — and then has to switch back to the browser to update the board, if they remember. That one dependency creates most of the pain software teams feel:",
  "ga_prob_1": "The board falls behind the real development work.",
  "ga_prob_2": "Developers lose focus switching between IDE, terminal, Git, and browser.",
  "ga_prob_3": "Managers and team leads see outdated project status.",
  "ga_prob_4": "Code progress and project progress drift apart.",
  "ga_prob_end": "The issue isn't that teams are careless — it's that the board is separated from where development actually happens.",

  "ga_cmp_h":   "Traditional vs Git-aware project management",
  "ga_cmp_p":   "Traditional project management is board-first: it focuses on cards, columns, statuses, and due dates. Git-aware project management is development-first — it keeps the board, but wires it to the software workflow. The difference isn't planning; it's how closely execution stays connected to the codebase.",
  "ga_cmp_img_alt": "Comparison of traditional project management and Git-aware project management",
  "ga_cmp_trad_t": "Traditional project management",
  "ga_cmp_trad_1": "Asks: “Did someone update the task?”",
  "ga_cmp_trad_2": "Status changes are manual and easy to forget",
  "ga_cmp_trad_3": "Board and code live in separate worlds",
  "ga_cmp_gaw_t":  "Git-aware project management",
  "ga_cmp_gaw_1":  "Asks: “What actually happened in the workflow?”",
  "ga_cmp_gaw_2":  "Commits and pushes advance the task automatically",
  "ga_cmp_gaw_3":  "Board reflects real development activity",

  "ga_how_h":   "How Git-aware project management works",
  "ga_how_p":   "A Git-aware tool understands the development workflow instead of treating tasks as isolated cards. It connects tasks to real development actions — so the board stays close to reality without extra busywork.",
  "ga_how_img_alt": "How Git-aware project management works, from IDE to updated board",
  "ga_how_1":   "Start work on a task straight from the IDE",
  "ga_how_2":   "Link commits and pushes to that task",
  "ga_how_3":   "Close the task from the development environment",
  "ga_how_4":   "Move the workflow forward — the board updates from real activity",

  "ga_vi_h":    "How Vi Project Manager approaches this",
  "ga_vi_p":    "Vi is built around Git-aware project management for software teams. Developers manage and complete tasks directly from the IDE, and the core workflow is called Commit & Close — one action that connects the code you just wrote to the task and the board.",
  "ga_vi_flow_learn": "See the full Commit & Close breakdown →",

  "ga_src_h":   "Git-aware doesn't mean reading all your source",
  "ga_src_p":   "A Git-aware tool doesn't need to inspect or store your source code by default. What matters is connecting useful development metadata — commits, pushes, task status, branch and workflow activity — to the task. In Vi, Git commands run locally through the IDE plugin, and Vi never stores or uploads your source. Teams stay in control of how much code context appears on the board.",
  "ga_src_link": "Read more about source code security →",

  "ga_who_h":   "Who is Git-aware project management for?",
  "ga_who_p":   "It's for software teams that want project tracking to stay close to real engineering work — developers, technical founders, engineering managers, team leads, and product teams working closely with engineering. It helps small teams, growing product teams, and larger engineering organizations reduce manual updates and improve visibility into real progress.",

  "ga_faq_h":   "Frequently asked",
  "ga_faq1_q":  "How is Git-aware project management different from a Git host like GitHub?",
  "ga_faq1_a":  "A Git host stores and serves your repository. Git-aware project management doesn't replace it — it connects your task workflow to Git activity (commits, pushes, status) so the board reflects real work. Vi works alongside GitHub, GitLab, Bitbucket, or your own Git server.",
  "ga_faq2_q":  "Does a Git-aware tool read my source code?",
  "ga_faq2_a":  "It doesn't have to. Vi connects task metadata to Git activity; Git commands run locally in your IDE through the plugin, and Vi never stores or uploads your source.",
  "ga_faq3_q":  "Do we have to change how we use Git?",
  "ga_faq3_a":  "No. Developers keep committing and pushing as usual. Vi links that activity to tasks and advances the workflow — so finishing the code also updates the board, without a separate status step.",

  "ga_cta_h":   "Keep project tracking in sync with real work",
  "ga_cta_sub": "Start free in two minutes. No credit card required.",

  "ga_explore_lead": "Keep exploring:",
  "ga_explore_git": "Git project management",
  "ga_explore_cnc": "Commit & Close",
  "ga_explore_ide": "IDE project management",
  "ga_explore_jira": "Vi as a Jira alternative"
}