{ "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.", "cnc_badge": "Commit & Close", "cnc_h1": "Commit & Close: finish tasks without leaving your IDE", "cnc_sub": "Finish work in the IDE. Vi commits the code and updates the board — one action replaces the whole \"update the ticket\" ritual.", "cnc_cta_start": "Start Free", "cnc_cta_pricing": "See Pricing", "cnc_video_cap": "Done in VS Code. Board updated automatically — the 40-second Commit & Close demo.", "cnc_problem_h": "The code is done. The board doesn't know.", "cnc_problem_p": "Developers finish the code, but the project board stays outdated — because updating the ticket is a separate, manual step in a browser tab. Someone has to find the ticket, change its status, write a note, and get back to the editor. Multiply that by every task, every developer, every day, and the tracker becomes a fiction that managers chase in standups.", "cnc_how_h": "How Commit & Close works", "cnc_how_1": "The developer selects a task in the IDE — their one active In Progress task.", "cnc_how_2": "When the code is ready, they mark the task as Done — still inside the IDE.", "cnc_how_3": "Vi stages the changes and creates a task-aware commit like \"[#142] Fix auth bug\".", "cnc_how_4": "Vi pushes to Git — locally, with the developer's own credentials.", "cnc_how_5": "Vi closes the task and moves it through the workflow — into Review, approval, or Done.", "cnc_how_6": "The project board updates automatically. Managers see real status — no chasing.", "cnc_why_h": "Why it matters", "cnc_why_1t": "Developers stay in the IDE", "cnc_why_1d": "No tab switching, no hunting for tickets. The whole task lifecycle happens where the code is written.", "cnc_why_2t": "Managers see real status", "cnc_why_2d": "The board reflects what actually shipped, because updating it is part of shipping — not a favor someone remembers to do.", "cnc_why_3t": "Git and workflow stay connected", "cnc_why_3d": "Every commit is linked to its task, so history, reviews, and tickets always line up.", "cnc_why_4t": "Less context switching", "cnc_why_4d": "Fewer manual ticket updates means more uninterrupted coding time — every day, for every developer.", "cnc_focus_h": "One active task per developer", "cnc_focus_p": "Vi enforces a focused execution model: each developer can have only one task In Progress at a time. Commit & Close completes that task and frees the slot for the next one. The result is less parallel unfinished work, an accurate workload picture, and a board where \"In Progress\" actually means in progress.", "cnc_sec_h": "Your code never leaves your machine", "cnc_sec_p": "All Git operations — stage, commit, push — run locally on the developer's machine through the Vi IDE extension. Vi never accesses, stores, or uploads source code. It orchestrates the task workflow; your repository stays yours.", "cnc_ide_h": "Where you can use Commit & Close", "cnc_ide_vscode": "VS Code — Available", "cnc_ide_rad": "RAD Studio — Under Review", "cnc_ide_vs": "Visual Studio — In Testing", "cnc_ide_lazarus": "Lazarus — In Testing", "cnc_ide_jetbrains": "JetBrains IDEs — Planned", "cnc_faq_h": "Frequently asked", "cnc_faq1_q": "What is Commit & Close?", "cnc_faq1_a": "Commit & Close is Vi's branded workflow action: a developer marks a task as 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.", "cnc_faq2_q": "Does Vi access my source code?", "cnc_faq2_a": "No. All Git operations run locally on the developer's machine through the Vi IDE extension. Vi never accesses, stores, or uploads source code — it only orchestrates the task workflow.", "cnc_faq3_q": "Does Commit & Close work with Git?", "cnc_faq3_a": "Yes. Commit & Close is built on Git: it stages your changes, writes a task-aware commit message like \"[#142] Fix auth bug\", and pushes to your remote — using your local Git configuration and credentials.", "cnc_faq4_q": "Can a developer have multiple tasks in progress?", "cnc_faq4_a": "No. Vi enforces one active In Progress task per developer. This focus rule prevents parallel unfinished work and keeps the board an accurate picture of what is actually being worked on.", "cnc_faq5_q": "What happens after a task is marked Done?", "cnc_faq5_a": "Vi stages the changed files, creates a task-aware commit, pushes to Git, closes the task, and advances it through the workflow — for example into a Review step with its approval chain, if your workflow defines one.", "cnc_faq6_q": "Does Commit & Close update the project board?", "cnc_faq6_a": "Yes. The task is moved to Done (or the next workflow step) and the project board updates automatically — managers see real project status without anyone editing tickets in a browser.", "cnc_explore_lead": "Keep exploring:", "cnc_explore_git": "Git-aware project management", "cnc_explore_vscode": "project management in VS Code", "cnc_explore_ide": "IDE project management", "cnc_cta_h": "Close your next task from your IDE", "cnc_cta_sub": "Start free in two minutes. No credit card required." }