Thanks!

Let's talk about the class you're using. I would prefer that we used a class starting with quarto-, something likequarto-exclude-from-search-index. It is admittedly verbose, but this is a feature that has the potential to be quite confusing for users if they're unaware, and a quarto- prefix minimizes the change that some existing document already has a class like that. (You can always retarget your preferred classes to quarto-exclude-from-search-index in a Lua filter)

In addition to the CLA signature and the changelog entry, we will need a few more things:

1. Tests of course need to all pass.
2. This is a new feature, so we need an accompanying documentation PR against the prerelease branch of https://github.com/quarto-dev/quarto-web/
3. Tests. Probably the easiest way to do it is to add a test that

• renders a full project with the a div that excludes a unique word, and then check that the word is missing from the search.json file.
• renders the same project with a project profile that adds a filter to remove the class, and then check that word is present in the corresponding search.json file.

The class is now renamed to quarto-exclude-from-search-index. CLA is underway. I contacted the head of ops at TileDB for a review, and I'm also trying to identify other members of my company who may want to contribute to this repo in the future. In response to your other feedback:

1. Understood, and I'm now testing different variations locally. My TypeScript is rusty, but it'll get there 😄
2. Once I get this working, I'll start work on a docs update.
3. I'll work on tests as well.

The class is now renamed to quarto-exclude-from-search-index.

Just FYI, I don't think you've pushed this yet.

Correct, I haven't. I'm still testing locally.

@nickvigilante I was in the process of fixing a separate search index bug, and so I made a PR that includes a test that you should be able to adapt for this one. Take a look at #11191