Neuroscout tour + tooltips in Builder

[adelavega]

I was thinking about how to document Neuroscout, and I realized that I personally never read frontend manuals unless I absolutely have to. I still think it's a good idea, especially for more technical model building details, but I think if we intersperse tours/tips/hovers throughout the interface to answer most questions, more people will actually see it.

I messed around with reacttour and it was pretty easy to make a tour that could be shown to first time users. The code is quite compact, and easy to trigger actions including Router changes. It gets a bit trickier once the builder starts (arguable the most important part), but doable.

Just an idea, but here's some screenshots of what it looks like.

[codecov-io]

Codecov Report

Merging #607 into master will increase coverage by 0.14%.
The diff coverage is 93.87%.

@@            Coverage Diff             @@
##           master     #607      +/-   ##
==========================================
+ Coverage   72.39%   72.54%   +0.14%     
==========================================
  Files          53       55       +2     
  Lines        2054     2065      +11     
==========================================
+ Hits         1487     1498      +11     
  Misses        567      567

Impacted Files	Coverage Δ
neuroscout/basic.py	100% <ø> (ø)	⬆️
neuroscout/utils/core.py	100% <ø> (ø)	⬆️
neuroscout/models/auth.py	95.83% <100%> (+0.18%)	⬆️
neuroscout/resources/analysis/reports.py	53.08% <100%> (-1.14%)	⬇️
neuroscout/resources/utils.py	95.91% <100%> (+0.17%)	⬆️
neuroscout/api_spec.py	100% <100%> (ø)
neuroscout/schemas/user.py	92.3% <100%> (+0.3%)	⬆️
neuroscout/utils/factory.py	100% <100%> (ø)
neuroscout/resources/predictor.py	97.56% <66.66%> (-2.44%)	⬇️
neuroscout/core.py	70.58% <86.66%> (-3.84%)	⬇️
... and 2 more

---

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 b72343f...00b6f8d. Read the comment docs.

[tyarkoni]

That looks good to me. I think a manual is still important, but it's fine if it focuses more on the implementation details (i.e., stuff people need to know for their methods sections) than on the UI.

[adelavega]

Yep, agreed!

[adelavega]

Okay, for this I added tooltips to all the pages

We still need to:

• Implement tooltips only pop up on first time
• Check text for all tooltips, maybe add some for every transformation
• Decide if tour is necessary at all, or if we should take it further. I think it might be OK as is, if the pop ups follow the tour.

Also, this PR closes #605. For that wee need to:

• Add back "predictions" question. When at the Run stage?
• Remove FAQ link to manual

[adelavega]

I'm going to go ahead and merge this, and we can keep working on it.

In particular, we need to add a place in the Transformations definition where we can put the tooltip text, and add that tooltip (with the idea each transformation would have its own tooltip helper).

We also need to add back the Predictions form (see #613)