Tony Fast

yea. i'm not going to find the time to setup my own qhub. i am thinking that there qhub.dev/alpha or qhub.dev/sandbox. these endpoints would deploy a different on a different...

adding to this, it would be nice to aggregate accessibility changelogs here.

what do y'all think about using discussions, now that we have them, to collect documentation https://github.com/jupyter/accessibility/discussions/29

working on this in #105

I'm sorry I delayed answering this. Could you post a line of code/pr that shows the fix you used?

will get to this. thanks bro

to track the nearness between the file managers, i put together side by side comparisons. i'm sharing the comparison below from this original [hackmd comparing retro and classic](https://hackmd.io/@tonyfast/HyEH6-zdt) to me,...

I would suggest namespacing the URL too. If the crawl space is `foo` and the crawler is called `bar` then you could access it as `http://explorer.continuum.io/explore/foo/bar` something like that.

i spent a little time thinking about a few tools different kinds of extra schema we could define. these are just some use cases for reference or discussion later on....

i dont have a good perspective of the jupyterlab issues anymore so i couldnt find issues about long running cells. maybe one of yall know better than me. im wondering...