[
  {
    "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": "08A Turning an Observation into a Clear Request",
    "titleTranslate": "第08课A｜提出修改并给反馈",
    "text": "Useful feedback connects an observation to a requested change, so that the person doing the work knows what to improve.\nInstead of saying that the page feels wrong, I explain which part is difficult to read, understand, or use.\nI might say that the header is too large on mobile and ask for a smaller title with slightly less padding.\nIf I want an existing pattern preserved, I include that request rather than assume that the other person will notice it.\nFor example, I can ask them to replace the icon while keeping its size and alignment consistent with the navigation.\nI separate necessary changes from optional ideas, because a long list can make every small suggestion appear equally urgent.\nWhen the task is clear, the next preview should show a specific improvement that we can compare with the previous version.\nI review that result using the same content and screen size so that unrelated differences do not confuse the comparison.\nIf the problem remains, I describe what is still visible and ask for another focused adjustment instead of restarting the entire design.\nThis approach makes feedback easier to act on and helps the conversation move from personal impressions to concrete decisions.",
    "textTranslate": "有用反馈把观察与修改请求连接起来，让执行者知道改哪里。\n我会说明哪部分难读、难理解或难用，而不只说页面不对劲。\n我可能说移动端页头太大，请求缩小标题并稍减内边距。\n想保留现有模式时，我会明确提出，不假定对方会注意。\n例如请求更换图标，同时保持尺寸和对齐方式与导航一致。\n我区分必要修改与可选想法，因为长清单容易让所有小建议都显得紧急。\n任务明确时，下版预览应显示可与上一版比较的具体改进。\n我用相同内容和屏幕尺寸检查，避免无关差异干扰比较。\n问题仍在时，我说明仍可见的现象，并要求针对调整，不重启整个设计。\n这样反馈更可执行，对话也能从个人印象转为具体决定。"
  },
  {
    "title": "08B Giving Feedback After a Preview",
    "titleTranslate": "第08课B｜提出修改并给反馈",
    "text": "After a preview is ready, I take a moment to compare the result with the original request before suggesting anything new.\nThis protects the work from an endless cycle in which every improvement immediately creates a different and unrelated direction.\nI begin by identifying what is now correct, such as the smaller header or the better alignment between neighboring navigation items.\nThen I describe any remaining issue in a way that someone can observe, rather than asking them to guess my preference.\nFor example, the dropdown may still look different from the avatar menu, even though both controls perform a similar kind of action.\nI can ask for the same border, background, and spacing while allowing the content inside each menu to remain different.\nIf the result already meets the requirement, I say so clearly and choose whether to continue with the remaining pages.\nApproval should identify the version or example being accepted, especially if several alternatives have appeared during the conversation.\nA simple instruction such as proceed with the second option is more useful when everyone can see which option it refers to.\nClear feedback includes an ending as well as a beginning, so that completed work can remain complete while the next task starts.",
    "textTranslate": "预览完成后，我先与原要求比较，再提出新建议。\n这可避免陷入每次改进后又立即提出无关新方向的循环。\n我先确认已正确的地方，比如页头缩小或相邻导航对齐改善。\n再以可观察方式描述剩余问题，而不让对方猜偏好。\n例如两个控件执行类似操作，但下拉菜单仍与头像菜单风格不同。\n我可要求相同边框、背景和间距，同时允许菜单内容不同。\n结果已满足需求时，我明确确认，并决定是否继续其他页面。\n尤其谈过多个备选时，应说明批准的是哪个版本或例子。\n大家能看到第二方案具体指什么时，按第二方案推进才有用。\n清晰反馈既要能开始也要能结束，让已完成工作结束、下一任务开始。"
  },
  {
    "title": "08C Working Conversation",
    "titleTranslate": "第08课C｜提出修改并给反馈",
    "text": "Me: The mobile header is still too large, and the menu icon looks slightly higher than the text next to it.\nDesigner: Would you like me to make the title smaller and align the icon with the label while preserving the current colors?\nMe: Yes, and please make the dropdown look consistent with the avatar menu, including its border, background, and spacing between items.\nDesigner: Should I apply these changes to every page immediately, or show you one example before changing the rest of the site?\nMe: Show me one complete example first, using a long title and the same content that we used in the previous preview.\nDesigner: The new preview is ready; the header is smaller, the icon is aligned, and both menus now use the same style.\nMe: This meets the request; go ahead with this version and update the remaining pages without introducing additional changes to their content.\nDesigner: Understood; I will use this approved example as the reference and report any page where the same approach does not fit.",
    "textTranslate": "我：移动端页头仍太大，菜单图标比旁边文字略高。\n设计者：要缩小标题并对齐图标与文字，同时保留当前颜色吗？\n我：是的，下拉菜单也要与头像菜单一致，包括边框、背景和项目间距。\n设计者：立即应用所有页面，还是先展示一个例子？\n我：先用长标题和上版相同内容展示一个完整例子。\n设计者：新预览好了，页头变小、图标对齐，两个菜单风格一致。\n我：这符合要求，按这版更新其余页面，内容不作额外修改。\n设计者：明白，以批准例子作参考，并报告不适用的页面。"
  },
  {
    "title": "08D Sentence Review",
    "titleTranslate": "第08课D｜提出修改并给反馈",
    "text": "Useful feedback connects an observation to a requested change, so that the person doing the work knows what to improve.\nI might say that the header is too large on mobile and ask for a smaller title with slightly less padding.\nFor example, I can ask them to replace the icon while keeping its size and alignment consistent with the navigation.\nI review that result using the same content and screen size so that unrelated differences do not confuse the comparison.\nAfter a preview is ready, I take a moment to compare the result with the original request before suggesting anything new.\nI begin by identifying what is now correct, such as the smaller header or the better alignment between neighboring navigation items.\nI can ask for the same border, background, and spacing while allowing the content inside each menu to remain different.\nA simple instruction such as proceed with the second option is more useful when everyone can see which option it refers to.\nThe mobile header is still too large, and the menu icon looks slightly higher than the text next to it.\nYes, and please make the dropdown look consistent with the avatar menu, including its border, background, and spacing between items.\nShow me one complete example first, using a long title and the same content that we used in the previous preview.\nThis meets the request; go ahead with this version and update the remaining pages without introducing additional changes to their content.",
    "textTranslate": "有用反馈把观察与修改请求连接起来，让执行者知道改哪里。\n我可能说移动端页头太大，请求缩小标题并稍减内边距。\n例如请求更换图标，同时保持尺寸和对齐方式与导航一致。\n我用相同内容和屏幕尺寸检查，避免无关差异干扰比较。\n预览完成后，我先与原要求比较，再提出新建议。\n我先确认已正确的地方，比如页头缩小或相邻导航对齐改善。\n我可要求相同边框、背景和间距，同时允许菜单内容不同。\n大家能看到第二方案具体指什么时，按第二方案推进才有用。\n我：移动端页头仍太大，菜单图标比旁边文字略高。\n我：是的，下拉菜单也要与头像菜单一致，包括边框、背景和项目间距。\n我：先用长标题和上版相同内容展示一个完整例子。\n我：这符合要求，按这版更新其余页面，内容不作额外修改。"
  },
  {
    "title": "08E Vocabulary in Context",
    "titleTranslate": "第08课E｜提出修改并给反馈",
    "text": "The preview looks great, but please mark the change that fixes the original issue rather than highlighting every small difference.\nThe critique includes practical comments about spacing, and each comment connects an observation with a requested improvement.\nThe reviewer outlined the main concerns and used highlights to show where the spacing still looked inconsistent.\nThe revised version looks clearer, but a small alignment mistake remains on the side of the menu.\nWe missed that detail earlier, so the next revision should correct it before introducing more changes.\nA useful response treats mistakes as information, rather than making the person receiving feedback feel foolish.\nThe design has been revamped, but I would still like to refine the grouping of related items.\nAn impeccable screenshot does not guarantee that the actual page works well with long content or ordinary user input.\nA successful change improves the user's experience while keeping the agreed scope firmly in view.",
    "textTranslate": "预览很好，但请标出解决原问题的修改，不必高亮每个小差别。\n评析含实用间距评论，每条把观察与修改相连。\n评审者概述关注点，用高亮标出间距仍不一致处。\n修订版更清晰，但菜单一侧仍有小对齐错误。\n我们先前遗漏细节，下次修订应先纠正再加修改。\n有用回应把错误当信息，不让收到反馈者觉得愚蠢。\n设计已改版，但我仍想细化相关项分组。\n无可挑剔的截图不保证真实页面在长内容或普通输入下正常。\n成功改动改善体验，同时牢牢把握约定范围。"
  }
]