DOC: added all projects toctree to databroker

[mrakitin]

Description

Add all projects toctree to the databroker documentation.

Motivation and Context

Motivated by NSLS-II/docs#73.

How Has This Been Tested?

Tested locally by building the documentation.

[codecov-io]

Codecov Report

❗ No coverage uploaded for pull request base (master@6e1dad0). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #321   +/-   ##
=========================================
  Coverage          ?   83.11%           
=========================================
  Files             ?       50           
  Lines             ?     6355           
  Branches          ?      922           
=========================================
  Hits              ?     5282           
  Misses            ?      943           
  Partials          ?      130

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6e1dad0...2c70ac2. Read the comment docs.

[jrmlhermitte]

this looks good to me (and I'm trusting that it builds when you say it does)
@danielballan is this good to go?

[danielballan]

Let's get Travis's BUILD_DOCS build to pass before we merge. I just kicked it to re-run. Merge at will if/when it passes.

[mrakitin]

Probably it needs rebasing and manual resolution of the conflict.

[danielballan]

I think we should revisit whether and how to do this. The number of packages is growing large. Instead of linking to them all, maybe just link to blueskyproject.io? What do you think, @mrakitin?

[mrakitin]

I agree with that approach.

[mrakitin]

I rebased on master and changed all the project documentation links to a single URL. Does it make sense, @danielballan?

[danielballan]

Thanks! Do you think we should remove the NSLS-II link as well, just to give the right impression? And maybe replace BugReports with the gitter, which is probably a better first place to go for help?

[mrakitin]

It's available via 560185a.

[danielballan]

Actually --- In the spirit of scrubbing facility-specific branding out, should we move to a bluesky gitter? The way projects do this (e.g. jupyterlab moved from jupyter/jupyterlab -> jupyterlab/jupyterlab) is to post a big message in the gitter with a link to the new one. There is no way to set up an actual redirect.

[danielballan]

If this were mainly an NSLS-II support channel I would say we should leave it as is, but it seems that a fair fraction of the questions we get are from other facilities that are evaluating bluesky.

[stuartcampbell]

I agree

[stuartcampbell]

I think moving the gitter to a non NSLS-II would be good, but we can always do that in a follow on PR if we want to merge this one now and then go off and investigate the best way to deal with Gitter.

[stuartcampbell]

I agree

[danielballan]

Good enough for me. We might want to resolve the gitter question before we update all the repos though, to save effort.