A good candidate query for a fresh Wikibase instance could also be to query the Wikibase registry for other instances of Wikibase.

Find all other (registered) Wikibase instances that have information for "exact match" to something specific.

This partially relates to T179262 as the examples need to be configurable in order to be able to show other examples.

I support strongly this issue. It will also push other WDQS-frontend related issues.
It needs at least two things. That's how I do it in my Wikibase instance.

1. Include custom-config.json with parameters taken from .env to the volume for wdqs-frontend. The custom-config.json specifies also the path to a page with SPARQL examples.

wdqs-frontend:
  image: "${WDQS_FRONTEND_IMAGE_NAME}"
  restart: unless-stopped
  volumes:
    - ./custom-config.json:/templates/custom-config.json

2. By default the empty Wikibase creates only the main page. It has to add two more pages: SPARQL examples and a template SPARQL.

As soon as this will be a default configuration, the related issues T179262 and T192914 will be resolved as well. Probably it would provide a basis to resolve T296917.

Moving to Wikibase Suite backlog. Please also consider https://phabricator.wikimedia.org/T296917 when addressing this, and resolve as well if it seems within scope at that time.

Moving to Wikibase Suite backlog.

Alright, moving it to #wmde-wikidata-tech’s radar then :)

As discussed in internal MatterMost conversation, there are basically two ways forward for making the examples configuration. Either we document the workaround of volume mapping and tracking the custom-config.json in the image, or we provide a mechanism to override the example related configuration in that file through container config. To set this through container configuration we could use either env vars, or preferable if possible, an optional custom config file which would merge and override the one provided in the container.

In T192907#10412103, @lojo_wmde wrote:

As discussed in internal MatterMost conversation, there are basically two ways forward for making the examples configuration. Either we document the workaround of volume mapping and tracking the custom-config.json in the image, or we provide a mechanism to override the example related configuration in that file through container config. To set this through container configuration we could use either env vars, or preferable if possible, an optional custom config file which would merge and override the one provided in the container.

This sounds very far away from the original intention of this ticket
The idea of this ticket is / was

As a user, that installs the query service UI against a wikibase instance and query service,
there are some default example queries that make sense for all wikibases
For example

e.g.

number of triples
latest revision
number of items
number of properties
example of a query federated with Wikidata

There are of course a bunch of other linked tickets in this ticket, but documenting a config workaround, or allowing changing configuration (which can already be done) don't seem to be tackling this ticket.