Is there a way to add a custom site header when using gh-pages?

[aflip]

Description

I'm deploying my quarto-built site using github pages. I would like to add something to the page headers. Currently I am rendering the website locally using quarto render then manually editing the index.html page. But i would like this meta content to go on all pages. On netlify there is an option to add a _headers file, is something like this possible on quarto > GH ?

<meta http-equiv="X-Clacks-Overhead" content="GNU Terry Pratchett"/> this is what i want to add to all the page headers

[mcanouil]

Use include-in-header at the level you want https://quarto.org/docs/output-formats/html-basics.html#includes

On netlify there is an option to add a _headers file, is something like this possible on quarto > GH ?

That's not up to Quarto.
This is cloud provider features, so you need to check the documentation of the provider you chose.

---

edit: adding my reply with code/screenshot

The following should work and can be combined with profiles, etc.
(the meta is at the bottom but still in the header)

format:
  html:
    include-in-header:
      - text: |
         <meta http-equiv="X-Clacks-Overhead" content="GNU Terry Pratchett"/>

[cscheid]

But i would like this meta content to go on all pages. On netlify there is an option to add a _headers file, is something like this possible on quarto > GH ?

I would use post-render project scripts that edit the file programmatically: https://quarto.org/docs/projects/scripts.html#pre-and-post-render

[mcanouil]

The following should work and can be combined with profiles, etc.
(the meta is at the bottom but still in the header)

format:
  html:
    include-in-header:
      - text: |
         <meta http-equiv="X-Clacks-Overhead" content="GNU Terry Pratchett"/>

[aflip]

Confirming that this works, but since it is sent in the page, and not as the server's header, the signal tracking extensions do not pick this up. more here: http://www.gnuterrypratchett.com/#HTML
I will now chase down github pages to see if there's a better way. Thank you.

[mcanouil]

I don't understand what you are saying.
The line is exactly where the link you shared indicates it should be.
Beware of DNS, server, and browser caching.