{"summary":"Wiki 和帮助中心的导航栏、目录、文末引导、页脚和手机上的章节切换，分别怎样安排。","notes":"<p>产品变复杂、官网要写大量 SEO 文章时，一套可靠的 Wiki 既能解答用户疑问，也能带来搜索流量。最常见的问题是手机上找不到目录、读完文章不知道去哪，布局上要处理以下五处：</p>\n        <ol>\n        <li><strong>移动端章节栏</strong>：手机以直板机为主，屏幕窄，放不下侧边目录。在底部常驻一个章节栏，点开后用满屏菜单列出全部章节，一行一项，方便点击，不必滚回顶部。</li>\n        <li><strong>目录</strong>：章节多、超出一屏时，目录用独立高度，和正文分开滚动，超出部分在上下截断。截断的边缘加渐变遮罩，提示上下还有内容，再配一个居中的箭头按钮，方便点击滚动。</li>\n        <li><strong>文末引导</strong>：在解答问题的文章下面放社群和社媒账号的入口，无论读者是人还是 AI，都能带来转化，相当于为转化目标免费投了一则上下文广告。卡片样式贴近正文组件，看起来像文章的一部分。</li>\n        <li><strong>页脚</strong>：用好看的背景图把页脚撑到半屏以上，吸引读者滑到底并停留。页脚里要放真正有用的信息，帮读者解决问题，否则只会招人反感。</li>\n        <li><strong>导航栏</strong>：Logo（返回官网）、关键页面的下拉菜单和核心 CTA 按钮，滚动时吸顶。Safari 等浏览器会按导航栏的颜色给地址栏着色，背景色要和品牌协调。</li>\n        </ol>\n        <p>附带的 Prompt 会找到文档页共用的布局，只调整导航栏、目录、大纲和文末区域的位置、滚动与响应方式，内容、文案、颜色和字体不变；改完后在页面顶部、中间、末尾和手机宽度下各截一张图供你检查。</p>","prompt":"Polish the layout of my docs or help center pages: the header, the page list, the outline and the end of each article. Keep the content, copy, colours and fonts. Change only how these parts sit, scroll and respond.\n\n0. Start from what exists\n- Find the shared docs layout, the site header, the page list (sidebar), the outline (table of contents) and the footer. Change those, so every page inherits the result.\n- Use CSS and a little plain JS. Add no scroll or animation libraries.\n\n1. Think of the page as three layers\n- The article and the footer scroll with the page.\n- The page list and the outline are position: sticky. They stop where they start, so they never jump when scrolling begins, and the end of the layout pushes them up at the bottom.\n- The header becomes position: fixed only after the page's opening (banner or hero) has left the screen. Before that it belongs to the page and scrolls away with it.\n\n2. Header: it scrolls away, then comes back floating\n- At the top it is clear, with no background.\n- Once the reader has scrolled and the banner's bottom edge is at or above the top of the screen (getBoundingClientRect().bottom <= 0), show it as a floating bar: position: fixed; a translucent white background; backdrop-filter: blur(18px); a soft shadow.\n- It enters in 320ms ease-out, from translateY(-24px) with blur(8px) and opacity 0. It leaves in 120ms when the reader scrolls back up to the banner. If the reader scrolls down again during the exit, cancel it and keep the bar.\n- Give headings a scroll-margin-top so anchor links never land under the bar.\n\n3. Page list: it scrolls on its own, and shows where there is more\n- Hide its scrollbar and let it scroll by itself.\n- Fade an edge only while more of the list waits beyond it. Toggle data-more-above and data-more-below on scroll and resize, and drive a mask-image: linear-gradient(...) with them: about 40px at the top and 56px at the bottom, each with a short fully clear strip at the very edge, so a half-cut row never shows as a faint line.\n- Add a small round arrow on each edge that has more. A click scrolls the list by 60% of its visible height, smoothly. Arrows are for the mouse only (tabindex=\"-1\", aria-hidden=\"true\"); keyboard focus already scrolls the list.\n- On load, bring the current page into view. Keep the list's scroll position in sessionStorage, so moving to another page does not reset it.\n- If there is a search box, let \"/\" focus it.\n\n4. Outline: mark the section being read\n- The current section is the last heading above a line 20% down the viewport.\n- Mark its link with aria-current=\"location\" and style that: border-left-color and text in the accent colour.\n- Update it on scroll, at most once per animation frame.\n\n5. End of the article: help first, then the next page\n- If the reader is still stuck, a \"Still need help?\" card with one or two real channels (the issue tracker, the community, a contact).\n- Then previous and next links, with each page's title. The first page links back to the home page.\n- Then the footer.\n\n6. Narrow screens\n- Hide the outline on tablets and the page list on phones. Put both in one bar fixed at the bottom: the page list on its left half, the outline on its right half.\n- The right half shows the name of the section being read, updated by the same 20% line, and truncated with an ellipsis when it is long.\n- A tap on either half opens its list as a sheet from the bottom edge (a dialog opened with showModal()), sliding up 24px as it fades in, with no dimming behind it. Mark the current entry and scroll it into view (scrollIntoView({ block: \"center\" })).\n- A tap on an entry, the close button, outside the sheet or Esc closes it; a section link then scrolls to its heading.\n- Make the tap targets one size up from the desktop list.\n\n7. Motion\n- Under prefers-reduced-motion: reduce, turn off smooth scrolling and the header's enter and exit animations.\n\n8. When done\n- List every file and selector you changed.\n- Check four states on my own pages: the top of a page, the middle, the end, and a phone-width window.\n- Show a screenshot of each.","skill":"/skills/kubai-wiki-layout/SKILL.md","skillText":"# 兼顾PC和移动端的Wiki布局\n\n《999 个小技巧，让你 Vibe 的产品更有质感》第 008 期 · @kubai087\n\n在用户的项目里按下面的要求改造。要求以用户的口吻写成：文中的 I、me、my 指用户；写着要先问的地方，先停下来问用户再继续。\n\n## 改造要求\n\nPolish the layout of my docs or help center pages: the header, the page list, the outline and the end of each article. Keep the content, copy, colours and fonts. Change only how these parts sit, scroll and respond.\n\n0. Start from what exists\n- Find the shared docs layout, the site header, the page list (sidebar), the outline (table of contents) and the footer. Change those, so every page inherits the result.\n- Use CSS and a little plain JS. Add no scroll or animation libraries.\n\n1. Think of the page as three layers\n- The article and the footer scroll with the page.\n- The page list and the outline are position: sticky. They stop where they start, so they never jump when scrolling begins, and the end of the layout pushes them up at the bottom.\n- The header becomes position: fixed only after the page's opening (banner or hero) has left the screen. Before that it belongs to the page and scrolls away with it.\n\n2. Header: it scrolls away, then comes back floating\n- At the top it is clear, with no background.\n- Once the reader has scrolled and the banner's bottom edge is at or above the top of the screen (getBoundingClientRect().bottom <= 0), show it as a floating bar: position: fixed; a translucent white background; backdrop-filter: blur(18px); a soft shadow.\n- It enters in 320ms ease-out, from translateY(-24px) with blur(8px) and opacity 0. It leaves in 120ms when the reader scrolls back up to the banner. If the reader scrolls down again during the exit, cancel it and keep the bar.\n- Give headings a scroll-margin-top so anchor links never land under the bar.\n\n3. Page list: it scrolls on its own, and shows where there is more\n- Hide its scrollbar and let it scroll by itself.\n- Fade an edge only while more of the list waits beyond it. Toggle data-more-above and data-more-below on scroll and resize, and drive a mask-image: linear-gradient(...) with them: about 40px at the top and 56px at the bottom, each with a short fully clear strip at the very edge, so a half-cut row never shows as a faint line.\n- Add a small round arrow on each edge that has more. A click scrolls the list by 60% of its visible height, smoothly. Arrows are for the mouse only (tabindex=\"-1\", aria-hidden=\"true\"); keyboard focus already scrolls the list.\n- On load, bring the current page into view. Keep the list's scroll position in sessionStorage, so moving to another page does not reset it.\n- If there is a search box, let \"/\" focus it.\n\n4. Outline: mark the section being read\n- The current section is the last heading above a line 20% down the viewport.\n- Mark its link with aria-current=\"location\" and style that: border-left-color and text in the accent colour.\n- Update it on scroll, at most once per animation frame.\n\n5. End of the article: help first, then the next page\n- If the reader is still stuck, a \"Still need help?\" card with one or two real channels (the issue tracker, the community, a contact).\n- Then previous and next links, with each page's title. The first page links back to the home page.\n- Then the footer.\n\n6. Narrow screens\n- Hide the outline on tablets and the page list on phones. Put both in one bar fixed at the bottom: the page list on its left half, the outline on its right half.\n- The right half shows the name of the section being read, updated by the same 20% line, and truncated with an ellipsis when it is long.\n- A tap on either half opens its list as a sheet from the bottom edge (a dialog opened with showModal()), sliding up 24px as it fades in, with no dimming behind it. Mark the current entry and scroll it into view (scrollIntoView({ block: \"center\" })).\n- A tap on an entry, the close button, outside the sheet or Esc closes it; a section link then scrolls to its heading.\n- Make the tap targets one size up from the desktop list.\n\n7. Motion\n- Under prefers-reduced-motion: reduce, turn off smooth scrolling and the header's enter and exit animations.\n\n8. When done\n- List every file and selector you changed.\n- Check four states on my own pages: the top of a page, the middle, the end, and a phone-width window.\n- Show a screenshot of each.\n"}