Support `brand` in HTML format of `book` project

[cwickham]

E.g. something like this should change the colors on the web version of a book:

project:
  type: book

book:
  title: "My Book"
  chapters:
    - index.qmd
 
format:
  html:
    brand: 
      color: 
        primary: "#ff0"

[cderv]

Do setting brand under html works?

I do think it could, and it could be good, but I don't think we designed it this way, and I thought it was on purpose. But now I am thinking this is a bug.

Single document

---
format: 
  html:
    brand: 
      color: 
        primary: "#ff0"
title: "Hello"
---

# content

See <https://quarto.org>

The link should be yellow - it is not

But with this, it is

---
format: html
title: "Hello"
brand: 
  color: 
    primary: "#ff0"
---

# content

See <https://quarto.org>

So for books, I wouldn't expect setting brand under format to work.

But this is not working either - so definitely a bug

project:
  type: book

book:
  title: "My Book"
  chapters:
    - index.qmd
 
format: html

brand: 
  color: 
    primary: "#ff0"

However, using a _brand.yml works 🤔

BTW, I don't think this is a problem with book. With default project it does not work.

• index.qmd

   ---
   format: html
   title: "Hello"
   ---
   
   # content
   
   See <https://quarto.org>

• _quarto.yml

   project:
     title: "test"
   
   brand:
     color: 
       primary: "#ff0"

Not yellow

So the problem seems to be about defining brand in the _quarto.yml 🤔

[gordonwoodhull]

So this is intentional, at least for now.

We currently only support the filename syntax for applying brand at the project level. The inline brand syntax is only supported on documents.

I.e. this works

• _quarto.yml

project:
  type: book

book:
  title: "My Book"
  chapters:
    - index.qmd
 
format: html

brand: brand-book.yml

• brand-book.yml

color: 
  primary: "#ff0"

Leaving this open in case there's an argument for inline brand in the project, otherwise I think branded books do work.

[cderv]

The problem I see is that I don't know if our YAML autocomplete can handle this case.

Currently, it will offer to fill brand as an object in quarto YAML

I think all our other fields behave the same in _quarto.yml and the document header, so users may get used to it.

Do setting brand under html works?

This is the other issue here. Setting brand top level or under a format should work.

Or should be removed from YAML validation too...

But other field works this way too I think 🤔