Anthony

> This should be a reader's decision. The UI has to be clear about "where your query is going to be performed" and also "results should be clear about where...

> Well, I think communicating "whether they mean to search subprojects/organization projects/etc" is part of the work the UI has to do. Yeah a bit, though I'm describing a problem...

Yeah, I would probably implement the scoping options in a larger overhaul of the front end pieces. I'm not yet certain how this will look, given some technical hurdles with...

> And we could have "shortcuts" below the saerch box +1 on this eventually, but what I'm trying to describe would be a step in the middle. We wouldn't add...

Doing some pruning here. How likely are we to get back to this PR? Is it worth prioritizing in the near future, or should we discuss retiring this work?

This will be addressed in the application with: https://github.com/readthedocs/ext-theme/pull/274 This PR is mentioning docs, which I do think should still be updated to cover these types of caveats more. The...

Just a note here: we worked translation pull/push into our release process, which happens weekly. This is far off from daily or twice daily, but automating commits was deemed too...

> do you have any objections about moving forwards with the first item during the coming weeks? Nope! It's something we have to do at some point. I would say...

I believe there are a few issues going over the blocks to upgrading if you're interested, but you've found the major issues we've touched on. The dependency on a very...

That would be my suggestion for the time being as well. It is possible to build the assets, but the dependency chain is extremely fragile right now and held together...