Problems about "Parts" #235

New Issue

GiteaMirror · 2026-03-22T15:32:27-05:00

GiteaMirror commented

2026-03-22 15:32:27 -05:00

Originally created by @BravoBaldo on GitHub (Oct 29, 2024).

I would like to highlight 2 problems regarding the "Parts"
In "_quarto.yml" you have some "parts" for example:
"- part: FRONT MATTER"
"- part: MAIN"
"- part: Fundamentals"
...
But an incorrect hierarchy creates problems in Pdf:

For Example
Part II\nMAIN
Part III\nFundamentals
Having the same hierarchical level "Part II\nMAIN" appears as something omitted.

Another problem is when you render as EPUB and Word (Docx): As you can read here:
https://quarto.org/docs/books/book-structure.html#parts-appendices
"...When rendering a book with parts to these formats, the parts will be ignored."

Then I suggest a different division and to add explicitily pages for "part"s

What do you think about dividing the book between theory and lab?

Originally created by @BravoBaldo on GitHub (Oct 29, 2024). I would like to highlight 2 problems regarding the "Parts" In "_quarto.yml" you have some "parts" for example: "- part: FRONT MATTER" "- part: MAIN" "- part: Fundamentals" ... But an incorrect hierarchy creates problems in Pdf: For Example Part II\nMAIN Part III\nFundamentals Having the same hierarchical level "Part II\nMAIN" appears as something omitted. Another problem is when you render as EPUB and Word (Docx): As you can read here: https://quarto.org/docs/books/book-structure.html#parts-appendices "...When rendering a book with parts to these formats, the parts will be ignored." Then I suggest a different division and to add explicitily pages for "part"s What do you think about dividing the book between theory and lab?

GiteaMirror added the area: book label 2026-03-22 15:32:27 -05:00

GiteaMirror closed this issue

2026-03-22 15:32:28 -05:00

GiteaMirror commented

2026-03-22 15:32:29 -05:00

@profvjreddi commented on GitHub (Oct 30, 2024):

Thanks for catching this issue. Coincidently, I was also thinking of the same lines: https://github.com/harvard-edge/cs249r_book/issues/493

I agree we should ditch the empty parts. Several others have mentioned this to me.

What do you think about dividing the book between theory and lab?

+1 again! I do think building two separate builds makes sense.

@profvjreddi commented on GitHub (Oct 30, 2024): Thanks for catching this issue. Coincidently, I was also thinking of the same lines: https://github.com/harvard-edge/cs249r_book/issues/493 I agree we should ditch the empty parts. Several others have mentioned this to me. > What do you think about dividing the book between theory and lab? +1 again! I do think building two separate builds makes sense.

GiteaMirror referenced this issue

2026-03-22 15:47:42 -05:00

[PR #236] [MERGED] Fixed minor markdown issue in text and url highlighting in Data Engineering chapter #649

GiteaMirror referenced this issue

2026-04-11 07:43:27 -05:00

[GH-ISSUE #235] Minor syntax issue: Section 14.4 has an issue with markdown in text and url highlighting #1330

GiteaMirror referenced this issue

2026-04-11 08:10:07 -05:00

[PR #236] [MERGED] Fixed minor markdown issue in text and url highlighting in Data Engineering chapter #1872

GiteaMirror referenced this issue

2026-04-13 13:11:10 -05:00

[PR #236] [MERGED] Fixed minor markdown issue in text and url highlighting in Data Engineering chapter #2594