DOC: Bring implementation details to the foreground of documentation

[oesteban]

Trying to give some more visibility to the theory. Also, discussed a little about find_estimators (related to nipreps/fmriprep#2560)

EDIT: Link to the new document - https://3553-189236569-gh.circle-artifacts.com/0/%7E/docs/docs_refactor-content-organization/methods.html

[codecov-commenter]

Codecov Report

Merging #248 (bc7ccda) into master (0e19395) will decrease coverage by 0.41%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #248      +/-   ##
==========================================
- Coverage   83.06%   82.64%   -0.42%     
==========================================
  Files          25       25              
  Lines        1836     1902      +66     
  Branches      208      231      +23     
==========================================
+ Hits         1525     1572      +47     
- Misses        280      299      +19     
  Partials       31       31              

Flag	Coverage Δ
travis	82.64% <100.00%> (-0.42%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
sdcflows/workflows/fit/syn.py	48.52% <ø> (ø)
sdcflows/workflows/fit/fieldmap.py	98.43% <100.00%> (ø)
sdcflows/workflows/fit/pepolar.py	100.00% <100.00%> (ø)
sdcflows/conftest.py	0.00% <0.00%> (ø)
sdcflows/utils/wrangler.py	100.00% <0.00%> (ø)

---

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 0e19395...bc7ccda. Read the comment docs.

[eilidhmacnicol]

Just some small things from me

[oesteban]

Thanks much @eilidhmacnicol . Do you think you learned something? - this is just a start, but someone who reads it should end with a relatively clear idea of what's going on and how SDCFlows attacks the problem.

[eilidhmacnicol]

Yes - as someone fairly representative of the target audience, the individual workflow functionalities were clear. There were some sentences that required a second read but I think, like you said, that it's a solid base.

[oesteban]

@effigies - if the docs do not clarify the answers to your question #247 (comment), then I need help improve this text.

@mgxd - I believe this documentation should help a lot in identifying when a bug could come from (thinking of that weird flip in the direction of correction of your data). Also interested in your feedback.

[effigies]

Will try to read through before our meeting.

[mgxd]

This is super useful, definitely helpful to digest some of what is going on during SDC

[effigies]

Looks good. Style issues only.