-
| Problem StatementI'm trying to make my website more maintainable by storing sidebar contents in external programmatically-generated YAML files instead of directly in  IssueThe sidebar panel appears, but it's empty - no content is displayed. If I hardcode the same structure directly in  QuestionWhat's the proper way to reference external YAML files for section-specific sidebar contents? The documentation isn't clear on this specific use case. Below is an example of the structure of the external sidebar,  - section: Organization
  contents: about/index.qmd
- section: People
  contents:
    - text: Team Member 1
      href: about/people/member1.qmd
    # more team members...And in my  website:
  navbar:
    pinned: true
    left:
      - text: About the Team
        href: about/index.qmd
    # other pages
  sidebar:
    - id: about
      title: "About the Team"
      style: docked
      background: dark
      contents: sidebar_about.yml
    # Other section sidebars defined here...
metadata-files:
  - sidebar_about.ymlI also include  | 
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
| Be sure to read the documentation on sidebar: https://quarto.org/docs/websites/website-navigation.html#side-navigation Then provide a small and simple fully reproducible example preferably as a Git repository. | 
Beta Was this translation helpful? Give feedback.
Where did you see this?
Contents of sidebar does not take a
filekey so why would you expect it to work?metadata-filesinclude the file as if you copy/pasted them in_quarto.yml, meaning you are including the content of the file at the top level of the project YAML thus not at all at the right place.Please read the documentation I have linked earlier to ensure you have a valid file or that your use of
metadata-fileswill lead to a valid file.If you use LLM, please double check that it's valid code and not made up code.
means
sidebar.ymlis: