Generally (though not ubiquitously) the default namespace is the main article space and you need to have expressed an interest in including other administrative or discussion focused namespaces to see them. is an option of adding it above the title?

The only issue with not having quickview for the other name spaces is that we are moving the metadata into the panel. Not a deal breaker I suspect, but there are real possible benefits to serving things like Table of Contents etc. in that panel. It could be an interesting venue for explaining process pages etc. to users. This is all out of scope at the moment, but it feels like a real area of opportunity. But I don't think adding more than metadata needs to be an immediate priority right now though.

Resolving so that work on implementation can begin with T307053

Its clunky but it matches how things are in places like preferences for example.

The vue.js implementation for quickview to be primarily done in core with the caveats detailed in the implementation notes ( T307560#7926123 ) and augmented via extensions should that be absolutely necessary.

• Design systems
• Search platform

Quickview could an extension (existing one, or even totally new) - it’s mostly “just an enhancement”, searching would still work fine without it. The main benefit would be that it’d be simpler: we’d only need to worry about the WMF ecosystem and what extensions/data/technology are available there, and not jump through some hoops to provide decent alternatives/fallback for when that data may not be there.

Based on conversations with Design Systems ( @Catrope and @AnneT )

One question at the heart of this implementation is what can rely purely on core and what is dependent on other extensions.

This will need a SPIKE