Anthony

Yeah, I probably lean that way, assuming we have a slightly more established JS library pattern and break out all of this to a standalone library. I still don't know...

I'm more torn, because there is a tradeoff to injecting at build time so that the built artifact never changes in the future (we don't have to support old documentation...

Aye, that middle ground solution I'm describing would be maintaining multiple versions of the client library package, and also hosting multiple major versions in a shared place. It's a bit...

Sorry, this isn't quite clear. I'm assume you're referring to a right-to-left version of RTD? We support translations here, but no, we don't currently have a RTL centric design. I...

@yarons agreed! @rahmanidashti I missed your notification here, are you still interested in helping here? So, we are going to be prioritizing a redesign of our site styles soon, so...

No updates on this, no. We likely won't take this on while we are still converting our site to use a css framework.

Sorry, no particular updates here yet. I'm still working intermittently on a UI rewrite, but I'm the only one that has been working on this project. I have been careful...

It's not an API rate limitation, we can't take action on the webhook unless the user has a GitHub user with permission to change the project attached to the RTD...

Ping @stsewd :point_up: We can also push this out some sprints or back on the backlog if it makes sense to return to this later instead.

> There is a huge maintenance benefit in having the redirects defined within the repository's version control We definitely all would like to see this eventually, but this is actually...