[ENH]: Add flowchart for users and improve docs #210
No reviewers
Labels
No labels
CRITICAL
Stale
WIP
bug
concept
coordinate
dataset
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
maintenance
maps
marker
mask
on hold
parcellation
preprocess
question
ready
storage
template-space
triage
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
juaml/junifer!210
Loading…
Reference in a new issue
No description provided.
Delete branch "enh/docs_flowchart"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Add a flowchart so users can be guided through the documentation.
Codecov Report
100.00% <ø> (ø)Flags with carried forward coverage won't be shown. Click here to find out more.
100.00% <ø> (ø)@ -0,0 +1,108 @@.. include:: links.inc... lose ...
I propose: "When we conceived Junifer, we thought of neuroimaging researchers' problems, and tried to come up with the best way to help them by building a tool that is easy to understand, learn and use. And of course, we are here to help you with your research."
I propose: "If you have any questions, problems and / or suggestions, ..."
"... help us help you"
I would kind of put this in a slightly different way like so:
"Communication is the key for you to help us and in turn help you solve your problems. Hence, we have opened several communication channels for you to contact us in the way that is most convenient for you."
I propose: "Some people do ..."
I propose: "... prefer to communicate verbally ..."
I propose: "Difficult to follow linearly."
@ -0,0 +71,4 @@In short, these are the 3 communication channels to get help:#. Discussions on Github (`junifer Discussions`_):The + and - might be a bit confusing for users to understand and I would lean towards having "Pros" and "Cons" explicitly mentioned and divided for each point.
@ -0,0 +1,158 @@.. include:: links.incread_adding_coordinates_start("Read Creating a Junifer extension")
read_adding_coordinates_start("Read Creating a Junifer extension")
solved => solve
@ -0,0 +1,108 @@.. include:: links.incI specifically don't want to mention neuroimaging here. Although it's only for neuroimaging, it's also very useful for other kind of data (e.g. electrophysiology.)
@ -0,0 +1,108 @@.. include:: links.incwhy do you like fancy words? This is for people that are looking for help because things are too complicated.
but I do agree with you.
@ -0,0 +1,108 @@.. include:: links.incFair enough, so my proposal still stands with the removal of "neuroimaging".
@ -0,0 +42,4 @@We can continue with the song, but we think you get the point. The point is that we will need help, and we will needto ask for it. We will need to ask for help from our colleagues, from our supervisors, from our friends.Has an indented new line here in the final render.
I would not put the "mind readers" part specifically and words in and around it.