emoji not being printed/rendered

[Masber]

Context

I am learning material mkdocs and trying to create a document with an emoji.
https://github.com/eth-cscs/manta/blob/docs/docs/basics.md?plain=1#L17

When I open this md file in browser in github, I can see the emoji https://github.com/eth-cscs/manta/blob/docs/docs/basics.md

https://github.com/eth-cscs/manta/blob/docs/docs/basics.md#set-boot-image

However, the emoji is not rendered when opening the static document rendered by material mkdocs

https://eth-cscs.github.io/manta/basics/

Any idea why?

Bug description

I can't see emoji in my material mkdocs page

Related links

• Reporting a bug

Reproduction

1. Create a md file like below:

## List images

## List cluster details/summary

## List hardware information

## Set runtime configuration

## Set boot image

> :warning: **Highly discourage**: only do this if sessions in the system has been deleted

## Set boot configuration

## Set kernel parameters

2. Set github workload as below

❯ cat .github/workflows/docs.yml
name: docs
on:
  push:
    branches:
      - master
      - main
      - docs
      - gh-pages
permissions:
  contents: write
jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Configure Git Credentials
        run: |
          git config user.name github-actions[bot]
          git config user.email 41898282+github-actions[bot]@users.noreply.github.com
      - uses: actions/setup-python@v5
        with:
          python-version: 3.x
      - run: echo "cache_id=$(date --utc '+%V')" >> $GITHUB_ENV
      - uses: actions/cache@v4
        with:
          key: mkdocs-material-${{ env.cache_id }}
          path: .cache
          restore-keys: |
            mkdocs-material-
      - run: pip install mkdocs-material
      - run: mkdocs gh-deploy --force

3. git add, git commit and git push

4. wait page to render

5. open link

https://eth-cscs.github.io/manta/basics/

Steps to reproduce

above

Browser

Chrome

Before submitting

• I have read and followed the bug reporting guidelines.
• I have attached links to the documentation, and possibly related issues and discussions.
• I assure that I have removed all customizations before submitting this bug report.
• I have attached a .zip file with a minimal reproduction using the built-in info plugin.

[squidfunk]

Converting to discussion, as this is definitely not a bug.