Week 8 · Overleaf & HTML Slides

Your paper is basically written. Over the last few weeks you wrote the parts — the question, how you did it, what you found, and what it means. Today you don't write new paper content. You do two tool jobs: turn what you wrote into a clean PDF, and build the slides you'll present with.

Job one is Overleaf — a website that turns your writing into a proper, academic-looking PDF. Nothing to install; it all runs in your browser. Job two is HTML slides — use the Guizang PPT Skill with Cursor or codex to build a polished deck from a tested template, then drop your live demo right inside a slide.

Every grey box is a prompt you can copy — paste it into Cursor or codex. Keep this page open all class. Stuck? Mia is here. By the end, three files go up to GitHub: your PDF, its source, and your slides.

01 · Today — two tool jobs

Two jobs today, both about tools — not more writing. Here's the whole shape.

02 · Overleaf — like Word, in your browser

Overleaf is like Word, but it lives in your browser and it's built for academic papers. Under the hood it uses a thing called LaTeX to do the fancy formatting — but don't let that word scare you. You install nothing. It all runs on a web page. Go to overleaf.com, sign up with your email, and check you can log in and see the New Project button.

Before anything real, learn the one loop that never changes: New Project → Blank Project → click Recompile (top right). A PDF appears on the right. That's the whole rhythm — change something, click Recompile, see the new PDF. You'll do it a hundred times today.

03 · Start from the apa7 template

Don't build a paper from a blank page — start from a finished one. Overleaf has a template already formatted the APA way (that's the style your paper has to follow). In the template gallery, search apa7, open "Template and Sample for Authoring APA7 Manuscripts", and click Open as Template. That copies a whole working paper into your account — title, author, abstract, body, references, all laid out. You just swap the example text for yours.

One line to check. Near the top you'll see \documentclass[stu]{apa7}. The stu means student paper — the cover page and double spacing your teacher wants. Leave it as stu; don't change it to man or jou. Then fill in your title, name, school, and abstract, clicking Recompile after each so you catch mistakes while they're small:

The apa7 template — fill in these spots: \documentclass[stu]{apa7} keep "stu" = student paper \title{ ... } your paper's title \author{ ... } your name \affiliation{ ... } your school \abstract{ ... } your ~150-word summary change one -> click Recompile -> check the PDF. small steps.

04 · Let Cursor / codex write the LaTeX

Here's the trick that saves you: you don't hand-type LaTeX. You already wrote your paper somewhere — Word, Feishu, a Markdown file. Let Cursor or codex translate it into LaTeX for you. Copy the prompt below, paste your whole paper where it says, paste your checked reference list where it says, and drop the LaTeX it hands back between \begin{document} and \end{document}, replacing the template's example text.

你是 LaTeX 排版助手。我在 Overleaf 用 apa7 模板(\documentclass[stu]{apa7})建好了一篇英文 APA 论文项目。请把我下面写好的论文内容,转成能直接粘进模板 \begin{document} 和 \end{document} 之间的 LaTeX 正文。

要求:
1. 只输出正文,别输出 \documentclass、导言区、\begin{document}/\end{document}——这些模板里已经有了。
2. 一级标题用 \section{},二级标题用 \subsection{};**加粗** 转成 \textbf{},列表转成 itemize/enumerate,表格转成 tabular。
3. 把 LaTeX 特殊字符都转义:% & _ # $ { } 分别写成 \% \& \_ \# \$ \{ \};从 Word 带来的弯引号“ ”‘ ’ 换成普通的 " 和 '。
4. 参考文献用 \begin{thebibliography}{99} + \bibitem,把我给的每条按 APA 7 格式排好、按作者姓氏字母排序。只准排我给你的这些文献,绝对不许新增、补全、或编造任何文献、DOI、作者、年份。某条信息不全,就原样留着并标 [待核对],别替我猜。
5. 转完,用中文写 3–5 步告诉我:怎么把这段贴进 Overleaf、点 Recompile 出 PDF;如果报红,我该把什么复制回来给你改。

论文内容如下:
【把你写好的论文全文粘在这里】

参考文献如下(每条一行,都是我核对过的真文献):
【把你核对过的文献粘在这里】

05 · When it turns red, paste it back

Sometimes Overleaf will fail to build and show a red error with a line number. Don't try to read it yourself. The move is always the same: copy the red error and the few lines it points at, paste both into Cursor or codex, and ask it to fix it and say why in one line. Nine times out of ten it's a stray special character sitting on exactly that line.

这段 LaTeX 在 Overleaf 编译报红了。报错和出错的那几行我都贴在下面,帮我改好,并用一句话告诉我为什么会报这个错。

报错信息:
【把红色报错整段粘在这里】

出错的那几行代码:
【把报错行号附近的几行粘在这里】

Most red errors are one of these. Keep it next to you:

The red-error survival kit — the usual suspects: these need a backslash: % & _ # $ { } so you write them as: \% \& \_ \# \$ \{ \} smart quotes from Word: “ ” ‘ ’ break the whole line swap them for plain: " ' the line number points AT the bad character. copy the error + that line, paste to Cursor / codex, done.

06 · Three quick things before you export

Before you export, three quick adds people always forget. None is a big new section — a few sentences each.

Copy this sentence straight into your paper for the AI disclosure — change the verbs to match what you actually did:

AI disclosure (paste into Method or acknowledgements):
"The authors used an AI assistant to convert the manuscript from Markdown into APA 7 LaTeX and to help fix compilation errors. All research content, data, analysis, and references were produced and verified by the authors."
Never let AI make up a reference. A paper that doesn't exist, a made-up DOI, an author who never wrote it — that's fabrication, and teachers check. AI only formats the references you hand it. Every line in your reference list has to be real and checked by you. Missing a detail? Leave it and mark [待核对] — don't let the model fill the gap.

07 · Build your slides with Guizang PPT Skill

Job two. Recommended path: install the open-source Guizang PPT Skill, then ask Cursor or codex to turn your paper into a polished, single-file HTML deck. For a research defense, choose its Swiss style: it is built for facts, analysis, and clear visual hierarchy. The result opens directly in a browser and flips with the arrow keys. Because it is still HTML, you can drop your live demo straight into a slide.

先帮我安装 Guizang PPT Skill:
npx skills add https://github.com/op7418/guizang-ppt-skill --skill guizang-ppt-skill

安装完成后,请使用 guizang-ppt-skill,根据我的论文内容生成一套 6–7 页的瑞士风研究答辩 slides,交付为双击即可打开的单文件 HTML。先读我的论文,不要编造任何数据、结论或文献。要求:

1. 按下面的答辩骨架组织内容:
   ① 标题页(论文题目 + 我的名字)
   ② 研究问题(我想搞清楚什么、为什么值得研究)
   ③ 方法(我怎么做的、几个人、样本怎么选)
   ④ 发现(最重要的 1–3 个结果,尽量用图表)
   ⑤ 意义 / 结论(说明了什么,顺带一句诚实的局限)
   ⑥ 谢谢 + 提问
2. 需要时增加一页可点击的网页 demo:用 iframe 嵌入,并清楚标注我该把 demo 网址填在哪里。
3. 每页只放关键词、关键数字和图,不要大段文字;一页只讲一个意思,字号要让后排看清。
4. 严格使用 Skill 自带模板和版式,完成后按 checklist 自检并在浏览器预览。
5. 做完用中文告诉我:生成了哪些文件、怎么打开和翻页、以及哪些内容仍需我亲自核对或替换。

08 · Export a PDF backup

One thing you must not skip: export your slides to PDF too. On presentation day the room's wifi can die, a browser can act up, a file can refuse to open. A PDF opens anywhere, offline, every time. So keep both — your HTML slides (with the live demo) as plan A, and a PDF as the backup that always works. Ask Cursor or codex to help, or just open the HTML and print to PDF.

09 · Push it all to GitHub

Last step, and it's your homework tonight. Three files go up to your project repo: your paper PDF, its source (the .tex), and your slides. Free Overleaf: Menu → Download PDF and Menu → Download Source, then upload them to GitHub by hand or git push. No need to buy the paid GitHub sync — this takes two minutes.

Then drop your repo link in the class group chat. No link means the teacher can't find your work. Why the group chat? Because the teacher reviews what you push and files GitHub issues — one issue per thing to fix. Each issue is a to-do for your 7/15 office hour. That's your fix list, handed to you.

10 · Before you go — class feedback

Two minutes, every class. Tell us what landed and what didn't — it directly shapes next week's class.