mirror of
https://github.com/harvard-edge/cs249r_book.git
synced 2026-05-07 18:18:42 -05:00
[GH-ISSUE #877] References section header in Latex/PDF build #1610
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/cs249r_book#1610
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @profvjreddi on GitHub (Jun 26, 2025).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/877
Originally assigned to: @hzeljko on GitHub.
@hzeljko, can you add the title References section header before we place the references at the end of each chapter?
Currently, they just appear suddenly. Also, can we adjust the font size?
In general, what is the best practice for references? Should I include them all at the end in one big list, or is it better to have them at the end of each chapter for quick review?
@hzeljko commented on GitHub (Jun 26, 2025):
Sure, I can add a "References" section title before the references at the end of each chapter.
Also, I’ll look into adjusting the font size to make the section visually consistent with the rest of the chapter content.
About best practices:
Both approaches are valid, but here’s a summary:
References at the end of each chapter:
One big reference list at the end: Common in academic books and dissertations. Might be less convenient for chapter-level navigation.
For a large book like this, organizing references by chapter improves readability and helps readers locate sources more easily in context.
@profvjreddi commented on GitHub (Jul 2, 2025):
Thanks for the feedback. I generally prefer references at the end of the chapter myself.
@profvjreddi commented on GitHub (Aug 23, 2025):
Resolved - References section headers fixed in LaTeX/PDF build