Handling appendix "numbering" in left navbar in book mode

[matthalstead-mfe]

Description

I am using project: type: book and rendering in both html and PDF. This helps with consistent section numbering and cross chapter referencing.

However, when producing the Appendices, I can't make the left-bar nav stop numbering the appendices. A manual declaration of left bar contents appears to be ignored in this mode. I could use css to remove them, but wondering if there is a way to override left navbar contents rendering for book type projects.

Here is an example of the _quarto.yml

  project:
    type: book
  
  brand: _brand.yml
  number-sections: true
  bread-crumbs: false
  
  book:
    title: "A Title is here"
    page-navigation: true
  
    navbar:
      pinned: true
      search: true
      background: "#003d59"
      right:
  
        - text: Files
          href: https://xxxx
  
        - text: Archives
          href: https://xxxx
  
    sidebar: 
      id: "left-sidebar"
      style: "docked"
      background: light
      alignment: left
      contents: 
        - section: "Intro"
          contents:
            - text: "Introduction"
              href: index.qmd
            - text: "About"
              href: 1_about.qmd
        - section: "Part 2"
          contents:
            - text: "Something A"
              href: 3_something.qmd
        - section: "Appendices"
          contents:
            - text: "Appendix A"
              href: appendix-a.qmd
            - text: "Appendix B"
              href: appendix-b.qmd 
      
  
    chapters: 
      - part: "Introduction"
        chapters:
          - index.qmd
          - text: About
            href: 1_about.qmd
  
          - text: How To
            href: 2_how-to.qmd
  
      - part: "Part 2"
        chapters:
          - text: Something A
            href: 3_something.qmd
  
          - text: Something B
            href: 4_something.qmd
  
          - text: Something C
            href: 5_something.qmd
  
          - text: Something D
            href: 6_something.qmd
  
          - text: Something E
            href: 7_something.qmd
  
          - text: Something F
            href: 8_something.qmd
  
          - text: Something G
            href: 9_something.qmd
  
          - text: Something H
            href: 10_something.qmd
  
          - text: Something I
            href: 11_something.qmd
  
      - part: "Appendices"
  
        chapters: 
        - text: Appendix A
          href: appendix-a.qmd
  
        - text: Appendix B
          href: appendix-b.qmd
  
        - text: Appendix C
          href: appendix-c.qmd
  
        - text: Appendix D
          href: appendix-d.qmd
  
        - text: Glossary
          href: glossary.qmd      
    
    page-footer: 
      background: light
      left: 
        - text: About
          href: https://a
        - text: Feedback
          href: https://b
        - text: Contact us
          href: https://c
  
      right: "© REPLACED" 
  
  
  format:
    html:
      theme: 
        - cosmos
      css: styles.css
      toc: true
      number-sections: true
      number-depth: 3
  
  crossref: 
    chapters: true
  
  execute:
    cache: false

[mcanouil]

Could you share a small self-contained "working" (reproducible) example to work with, i.e., a complete Quarto document or a Git repository? The goal is to make it as easy as possible for us to recreate your problem so that we can fix it: please help us help you! Thanks.

---

You can share a self-contained "working" (reproducible) Quarto document using the following syntax, i.e., using more backticks than you have in your document (usually four ````).
See https://quarto.org/bug-reports.html#small-is-beautiful-aim-for-a-single-document-with-10-lines.

If you have multiple files (and if it is absolutely required to have multiple files), please share as a Git repository.

R	Python
````qmd --- title: "Reproducible Quarto Document" format: html engine: knitr --- This is a reproducible Quarto document. {{< lipsum 1 >}} ```{r} x <- c(1, 2, 3, 4, 5) y <- c(1, 4, 9, 16, 25) plot(x, y) ``` {#fig-placeholder} {{< lipsum 1 >}} The end after @fig-placeholder. ````	````qmd --- title: "Reproducible Quarto Document" format: html engine: jupyter --- This is a reproducible Quarto document. {{< lipsum 1 >}} ```{python} import matplotlib.pyplot as plt x = [1, 2, 3, 4, 5] y = [1, 4, 9, 16, 25] plt.plot(x, y) plt.show() ``` {#fig-placeholder} {{< lipsum 1 >}} The end after @fig-placeholder. ````

Additionally and if not already given, please share the output of quarto check within a code block (i.e., using three backticks ```txt), see https://quarto.org/bug-reports.html#check.

[matthalstead-mfe]

I have added an example config. The key is that the contents definition is not used. It is used if the type is a website. The left nav bar seems to be auto generated from the contents of the book chapters. I can't share the whole project as it is an internal one that can't be made public.

[mcanouil]

I did not asked for your particular project. I asked for a small reproducible example that would allow anyone to work on your issue without having to guess.
Use quarto create project, make small modifications to reproduce the issue, share as a Git repository.

[matthalstead-mfe]

I was hoping it was obvious from the site yml file.

Here is a basic project. The contents configs are ignored in the sidebar, but not say the setting of search to false.

[mcanouil]

I don't understand your GitHub repository.
Your issue is about the appendix, but there is none in it.

Regarding the "sidebar", I missed it in your original long configuration file. There are no sidebar: in books. It's being overtake by the book template and the chapters/appendices.

Now looking back at your original configuration, your appendices are actually not appendices, they are chapters as any others.
I suggest you take a second look at the book guide, in particular the parts and appendices part.

[matthalstead-mfe]

Thanks for that. The sidebar: does still seem to have some effect in books in terms of attributes docked and search, so it doesn't seem completely irrelevant.