-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DOC] Update documentation #399
Conversation
Thinking about to give an overview of the project, would it make sense to have an OSF project to help do that as OSF allows to have project components and have each of them track a github repo. This is what I did for the COBIDAS (see here: https://osf.io/anvqy/) and I could try to do the same with the Reproschema. |
Other doc related issue: This PR on the UI "doc" needs reviewing : ReproNim/reproschema-ui#148 |
@Remi-Gau - i think i want to stay with the docs controlling the narrative on reproschema for now before creating an OSF project. perhaps in the future, but at this point, i think github is fine. |
okidoki I am cool with that. :-) |
@Remi-Gau - whenever you get a chance, it would great if you can merge the PR i sent to your repo. |
56d169f
to
a639390
Compare
@Remi-Gau - i did open the svg to edit and then decided i had a few other things to address first here are some thoughts that crossed my mind.
btw, i've just released 1.0.0-rc1 and my hope is that we can get any updates to the documentation merged in before the 1.0.0 release (say over the next two weeks). |
Agreed: will try to see how this can be visualized "easily".
Agreed I think I did start working on this in the pre-historic times of this repo when we still had the context files. Will drop that.
Agreed.
Are you referring to this one?
Woohoo ! 🤞 |
Oh actually I could make:
Or would that be too much? |
perhaps before making the figure (or alongside it), creating the doc section that describes how you can create your own protocol. what are the bare bones requirements (of structuring the repo - see the demo-protocol repo), and what tools (or soon to be available tools) you can use.
acutally no just the right part of the figure you posted earlier.
i would say one figure should be sufficient. instead of the example in the reproschema repo, which is more for expanding and illustrating test cases, perhaps use the demo-protocol repo. the demo-protocol repo should really simplify itself to demonstrating reproschema rather than a specific study (current scenario). for example, here are local new activities vs remote activities. in this local activity we are creating new items but also reusing existing items and so on. and i think this is the sentiment that has to come across in the figure. |
Finally took some time to start working on a I sort of took the use-case of someone starting from scratch and I try to assume no prior knowledge on git and github. If you have time to have a look let me know what you think. Still need to do:
One idea that we was thrown around was to create a template repo, no? To help providing the bare-bone folder structure and infrastructure to create a standalone app, no? |
Another idea: would it make sense to have a draft pull request on the library for a new activity where members of the community who want to try to contribute. |
@Remi-Gau - thanks for this - looks great. i think this is the start of great walkthrough. and it's important that people understand the structure even if they end up using more automated tools. yes. we should definitely create a starter template for those who want to do by hand. a section that would be good to add is how to fix the references so that any usage/reference is fixed using github checksums and ensure relative paths within an activity. ps. on to dreaming, the same thing should be generated by a
where the |
I like your dreams 😍 Actually I think I am actually going to break this part of the doc in several pages because I already anticipate there will be a lot of scrolling otherwise. |
- stub for creating activities and items - add some tips referring to CI and how to use valueConstraints
I started adding some tips for validation and using CI. Also adding some TODOs in comments for future-me. Sorry if the way the doc grows is not the most linear: I am adding things also as a way for me to takes notes while using some "new" aspects of the reproschema. |
- expand on activity creation and tips - start creating page for translation - pointers to items for collecting demographic info
In the schema structure:
{
"@id": "schema:value",
"schema:domainIncludes": {
"@id": "reproschema:Choice"
},
"schema:rangeIncludes": [
{
"@id": "reproschema:Skipped"
},
{
"@id": "reproschema:DontKnow"
}
]
} |
@Remi-Gau - thanks for putting this together. i think this will be good to resurrect and finish. @Rahul-Brito may be able to review this and add any additional materials. |
Happy to wrap this one up. |
@Rahul-Brito - can you coordinate a docathon around this ? |
Hi @Remi-Gau so sorry for not replying earlier. I'm a new graduate student in Satra's lab, nice to meet you. 've been trying to prioritize all the things I want to do/need to do and replying to this has been on the back of my mind for a little. My understanding is we want to get a nice, easy-to-implement "hello world" reproschma repo up and running? If so, that sounds great to me. I have run into issues getting my own started, even with the existing documentation we have, and I can't always tell if this is user error, dependency error, etc. Let me know if I misunderstand! Also, how does a dockathon compare to a hackaton :D. Anyways, let me know! Perhaps next week or the week after we can set something up. I will be sure to be much more responsive as well. |
hey @Rahul-Brito nice to e-meet you I suspect that finishing up all the unticked boxes in this PR could be a start as well for some doc And a dockathon is litteraly a hackaton but where participants only work on the documentation of a project. So 2 or 3 days where we don't write code but instead we write code comments, doc for developpers, tutorials, demos, FAQ... |
- pymdownx.highlight: | ||
anchor_linenums: true | ||
line_spans: __span | ||
pygments_lang_class: true | ||
- pymdownx.inlinehilite | ||
- pymdownx.snippets | ||
- pymdownx.superfences |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
adds syntax highlithing
merge conflicts fixed moved all my stuff in a "tutorial" section this will probably need a "refactoring" Also need to make sure that people following the tuto would actually result in something valid: almost tempted to say that all the code snippets should actually be executable to make sure they stay valid. Also not sure how the "linkMLification" will affect the doc. |
we're going to merge then clean up duplicates |
To-do / TOC
INFRA
Related issues or PR
Primarily in this issue but see also:
UI documentation