[
  {
    "notice": "只有 title 和 text 字段是必填，其他字段可删除不填。填写时，请从第三条数据开始填写，第二条数据是示例，填写完成之后，不要删除前面两条",
    "notice1": "只有 title 和 text 字段是必填，其他字段可删除不填。填写时，请从第三条数据开始填写，第二条数据是示例，填写完成之后，不要删除前面两条",
    "notice2": "只有 title 和 text 字段是必填，其他字段可删除不填。填写时，请从第三条数据开始填写，第二条数据是示例，填写完成之后，不要删除前面两条",
    "title": "这里填标题，必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填",
    "titleTranslate": "这里填标题翻译",
    "text": "这里填原文，一句一个换行符，一段两个换行符，必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填必填",
    "textTranslate": "这里填原文翻译，一句一个换行符，一段两个换行符",
    "audioSrc": "这里填音频的url/在线地址"
  },
  {
    "title": "How are you today?",
    "titleTranslate": "今天好吗？",
    "text": "STEVEN:Hello, HELEN.\n\nHELEN:Hi, Steven.\n\nSTEVEN:How are you today?\n\nHELEN:I'm very well, thank you. And you?\n\nSTEVEN:I'm fine, thanks.\n\nSTEVEN:How is Tony?\n\nHELEN:He's fine, thanks. How's Emma?\n\nSTEVEN:She's very well, too, Helen.\n\nSTEVEN:Goodbye, Helen.Nice to see you.\n\nHELEN:Nice to see you, too, Steven. Goodbye.",
    "textTranslate": "史蒂文：你好，海伦 \n\n海 伦：你好，史蒂文 \n\n史蒂文：你今天好吗？ \n\n海 伦：很好，谢谢你。你好吗？ \n\n史蒂文：很好，谢谢。 \n\n史蒂文：托尼好吗？ \n\n海 伦：他很好，谢谢。埃玛好吗？ \n\n史蒂文：她也很好，海伦。 \n\n史蒂文：再见，海伦。见到你真高兴。 \n\n海 伦：我见到你也很高兴，史蒂文。再见。",
    "audioSrc": "/sound/article/nce1/009&010－How Are You Today.mp3"
  },
  {
    "title": "16A Reporting Progress Without Mixing Up the Stages",
    "titleTranslate": "第16课A｜汇报进度与发布更新",
    "text": "A progress report should explain what has changed and what remains, rather than use one broad word to describe several different stages.\nI may have finished editing the page without committing the changes, and a successful commit does not mean that the update is already online.\nAfter the commit, the changes may still need to be pushed to the remote repository before an automatic build can begin.\nIn some projects, a push to the production branch starts deployment; in others, publishing requires a separate action or approval.\nI name the actual stage so that the person reading the report knows which result they can expect to observe now.\nFor example, I can say that the changes have been pushed but the production deployment is still running and has not completed yet.\nIf a build fails, I report where it failed and which evidence is available, instead of implying that the entire update has disappeared.\nThe remaining work may involve correcting a configuration, retrying a build, or checking the published page after the deployment succeeds.\nThis separation also makes it easier to choose the next action without repeating steps that have already finished successfully.\nA useful report ends with the current result, the remaining uncertainty, and the concrete step that will resolve it for this project.",
    "textTranslate": "进度报告应说明已改与剩余内容，不用一个宽泛词概括不同阶段。\n页面编辑完成可能尚未提交，而提交成功不等于已上线。\n提交后可能还需推送远端，自动构建才会开始。\n有些项目推生产分支即部署，其他则需独立操作或批准。\n我指出实际阶段，让报告读者知道现在能观察什么结果。\n例如可以说改动已推送，但生产部署仍在运行，尚未结束。\n构建失败时，我报告失败阶段和证据，不暗示整个更新消失。\n剩余可能是修配置、重试构建，或部署成功后检查页面。\n分清阶段也更易选择下一动作，不重复已成功步骤。\n有用报告以当前结果、剩余疑点及解决它的具体步骤结尾。"
  },
  {
    "title": "16B Following an Update into Production",
    "titleTranslate": "第16课B｜汇报进度与发布更新",
    "text": "Before an update goes live, I review what will be published and confirm that the release contains the changes we actually intend to share.\nThe source files should not accidentally include private configuration, unrelated experiments, or generated material that does not belong in the repository.\nThen I follow the deployment process that the project already uses, rather than assume that every application publishes in the same way.\nA preview helps us inspect the result before publication, but it may use a different environment from the one that serves ordinary visitors.\nOnce the production deployment is complete, I open the actual site and check the pages affected by the update.\nI look for the intended content and confirm that the main links lead to the correct destinations under the production domain.\nIf the new version does not appear, I investigate the current deployment and delivery behavior instead of editing the same content again immediately.\nThe report should distinguish a successful deployment from the particular pages and actions that have actually been checked afterward.\nAfter sharing the production link, I record any remaining follow-up work so that a completed release does not hide an unfinished requirement.\nA release is easier to understand when every stage has a clear outcome and the final result can be connected to the intended source changes.",
    "textTranslate": "更新上线前，我检查将发布什么，确认版本包含确实想分享的改动。\n源文件不应误含私人配置、无关实验，或不应入仓库的生成材料。\n接着沿用项目既定部署流程，不假设所有应用相同。\n预览有助发布前检查，但环境可能不同于普通访客访问环境。\n生产部署完成后，我打开实际站点，检查受更新影响的页面。\n我查找预期内容，确认主要链接在生产域名下指向正确位置。\n新版未出现时，我先查部署与分发，而不立即重改内容。\n报告应区分部署成功，与之后真正检查过的页面和操作。\n分享线上链接后，记录待跟进工作，避免已发版掩盖未完需求。\n每阶段有清晰结果且最终效果对应源改动时，版本发布更易理解。"
  },
  {
    "title": "16C Working Conversation",
    "titleTranslate": "第16课C｜汇报进度与发布更新",
    "text": "Me: Have the latest changes been committed and pushed, or are they still only available in the local working directory on this machine?\nDeveloper: They have been committed and pushed, and the automatic build has started, but the production deployment is not complete yet.\nMe: Please distinguish those stages in the report and let me know which step is running before you say that the update is online.\nDeveloper: The build has now passed; the deployment is running, and I will check the updated pages once it finishes successfully.\nMe: Before sharing the link, confirm that the production site shows the intended content and that the main navigation still works as expected.\nDeveloper: The updated pages are visible, and the reviewed links work; I will report the exact pages checked and any remaining limitations.\nMe: Good; include the production URL and summarize what changed, without treating an unchecked part of the application as verified by this release.\nDeveloper: I will provide that summary and record the remaining follow-up tasks so that the next session starts from the actual release state.",
    "textTranslate": "我：最新改动提交推送了吗，还是仅在本机工作目录？\n开发者：已提交推送，自动构建已开始，但生产部署未完成。\n我：报告中区分这些阶段，称已上线前先说明哪步正在运行。\n开发者：构建现已通过，正在部署，成功后会检查更新页面。\n我：发链接前，确认生产站显示预期内容，主导航仍按预期工作。\n开发者：更新页已可见，检查过的链接正常，会报告具体页面和限制。\n我：好，附线上网址并总结改动，别把未检查部分也当作已验证。\n开发者：会提供总结并记待跟进任务，让下次从真实发布状态开始。"
  },
  {
    "title": "16D Sentence Review",
    "titleTranslate": "第16课D｜汇报进度与发布更新",
    "text": "A progress report should explain what has changed and what remains, rather than use one broad word to describe several different stages.\nAfter the commit, the changes may still need to be pushed to the remote repository before an automatic build can begin.\nI name the actual stage so that the person reading the report knows which result they can expect to observe now.\nThe remaining work may involve correcting a configuration, retrying a build, or checking the published page after the deployment succeeds.\nBefore an update goes live, I review what will be published and confirm that the release contains the changes we actually intend to share.\nThen I follow the deployment process that the project already uses, rather than assume that every application publishes in the same way.\nI look for the intended content and confirm that the main links lead to the correct destinations under the production domain.\nAfter sharing the production link, I record any remaining follow-up work so that a completed release does not hide an unfinished requirement.\nHave the latest changes been committed and pushed, or are they still only available in the local working directory on this machine?\nPlease distinguish those stages in the report and let me know which step is running before you say that the update is online.\nBefore sharing the link, confirm that the production site shows the intended content and that the main navigation still works as expected.\nGood; include the production URL and summarize what changed, without treating an unchecked part of the application as verified by this release.",
    "textTranslate": "进度报告应说明已改与剩余内容，不用一个宽泛词概括不同阶段。\n提交后可能还需推送远端，自动构建才会开始。\n我指出实际阶段，让报告读者知道现在能观察什么结果。\n剩余可能是修配置、重试构建，或部署成功后检查页面。\n更新上线前，我检查将发布什么，确认版本包含确实想分享的改动。\n接着沿用项目既定部署流程，不假设所有应用相同。\n我查找预期内容，确认主要链接在生产域名下指向正确位置。\n分享线上链接后，记录待跟进工作，避免已发版掩盖未完需求。\n我：最新改动提交推送了吗，还是仅在本机工作目录？\n我：报告中区分这些阶段，称已上线前先说明哪步正在运行。\n我：发链接前，确认生产站显示预期内容，主导航仍按预期工作。\n我：好，附线上网址并总结改动，别把未检查部分也当作已验证。"
  },
  {
    "title": "16E Vocabulary in Context",
    "titleTranslate": "第16课E｜汇报进度与发布更新",
    "text": "The build system generates staging builds, and a successful build can be reviewed before the production release is published.\nWe will deploy the approved changes after the preview is ready, then check the live webpage under the production domain.\nThe release notes mention the patched behavior, the current version, and the follow-up tasks that remain open.\nThe builder reports completion after the output is created, but publication still depends on the separate deployment stage.\nA rebuild uses the updated source, while a retry may repeat the previous attempt without changing the input.\nThe deployment command was called from the terminal, and its output was captured in the report for later review.\nThe configuration was restored to the previous revision, and the update was withdrawn while the team investigated the failure.\nA working release can remain available while a new variant is reviewed in a separate environment.",
    "textTranslate": "构建系统生成预发布版本，成功后可在正式发布前检查。\n预览就绪后部署批准改动，再检查生产域名下页面。\n发布说明提到修补行为、当前版本和待跟进任务。\n构建器产物完成后报结束，但公开仍依赖部署阶段。\n重建使用新源，重试可能不改输入重复上次尝试。\n部署命令从终端调用，输出被记录供后查。\n配置恢复上版，更新撤回供团队调查。\n新变体在独立环境审阅时，正常版本仍可用。"
  }
]