-
Notifications
You must be signed in to change notification settings - Fork 4
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
Documentation #175
Documentation #175
Conversation
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.
Amazing 🤩
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.
ummm....whoa this is thorough!!!!!!! I will review tomorrow. 1.0
got me a little busy
I also made this cheatsheet (However some links need the documentation to be deployed) |
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.
Thanks @dgrassellyb for this, this is fantastic!!
I left a few specific comments for typos and requests for clarification. I also have some comments about the front page README:
- Many heading links in the readme don't work?
- Full stop missing at the end of renv propagation section
- Boilerplate or boilderplate? Could be a typo.
- docker image build: typo in "each R version" (no "s" at the end)
I also have some general comments:
- Within the navbar, for the User Guides section I would put a subsection titled "Basics" with the "Get Started", "Common structure of the workflows" and "Codespaces" sections. Then I would put another subsection titled "Invididual workflows" with all the other pages.
- I would retitile "common structure" to "Common strucure of the workflows" and put it at the top of the articles.
- There's also another "spell checks page" in the Articles drop down. Not sure what the difference is between the two?
vignettes/readme-render.Rmd
Outdated
|
||
# Render README Workflow | ||
|
||
This GitHub Actions workflow renders the README from R Markdown (`README.Rmd`) to Markdown (`README.md`). Additionally, it can format the generated Markdown using a formatter. The workflow is triggered manually (`workflow_dispatch`) and can also be invoked as a workflow call (`workflow_call`). |
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.
Could you specify why this is required?
vignettes/spellchecks.Rmd
Outdated
|
||
# Spelling Workflow | ||
|
||
This GitHub Actions workflow performs spellchecking on the specified R files. The workflow is triggered manually (`workflow_dispatch`) and can also be invoked as a workflow call (`workflow_call`). |
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.
Mention somewhere the exclusion wordlist here?
Can we add a hex to the front page too? smth like below |
Thanks a lot for your feedbacks, I will review this ! :) |
above and beyond!!! This cheatsheet is so cool |
Just a few notes: Musing on the README - should we just remove most of the stuff there as it is discussed more thoroughly in the vignettes. Get Started: Could this vignette get a separate tab? Cheatsheet: Could that be linked as a Get Started dropdown option? Like how we have it on https://pharmaverse.github.io/admiral/dev/ Lock Files and Propagation: Since we are moving away from this - wondering if this is still need to document? |
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.
Looks great overall.
Maybe we should structure the "Articles" menu, e.g., separate sections for workflows used in all admiral packages and workflows used in admiralci only.
vignettes/pkgdown.Rmd
Outdated
|
||
### `multi-version-docs` Job | ||
|
||
This job, if triggered, deploys the multi-version documentation to the `gh-pages` branch. It checks for the `skip-multiversion-docs` input and `[skip docs]` in the commit message before proceeding. |
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.
Does this job also update the "Versions" menu?
Co-authored-by: Stefan Bundfuss <[email protected]>
Co-authored-by: Stefan Bundfuss <[email protected]>
Ok let's do this ! it's ready to be merge now (I also pushed a fix in |
Shall we just merge and publish this and do the review in an issue? Might be a little easier if we don't have to pull down and render the site?? |
I'll fork it for rendering and send you the link |
* Update pkgdown.yml * [actions skip] Add/Update README.md for main * update cheatsheet * update cheatsheet * fix * fix pdf rendering * fix * fix hex * [actions skip] Add/Update README.md for main * fix rendering --------- Co-authored-by: GitHub Actions <[email protected]>
Pushed again some other fixs, here is the rendered doc from my forked repo : https://dgrassellyb.github.io/admiralci/
I even updated the |
@dgrassellyb That regex looks incorrect. |
reusable via the | ||
[`workflow_call`](https://docs.github.com/en/actions/using-workflows/reusing-workflows) | ||
GitHub Actions event. | ||
reusable via the \[`workflow_call`]\[workflow\_call] GitHub Actions |
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.
@dgrassellyb is it that I don't understand what this syntax is saying or is it a typo? Don't be afraid to tell me if it's the former 😄
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.
Indeed since to comes from .Rmd -> .md job, I have this in the .Rmd :
reusable via the [workflow_call
][workflow_call] GitHub Actions event.
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.
ok, thanks!
What about removing these links and just listing out our potential workflows? The one I clicked go to 404. Can we say why this is a bad practice? can't get latest and greatest updates - encourage you to make issues to enchance our workflows. Could we give some context on what these bullet points are leading us to? |
Possible to embed cheat sheet like we did for admiral? Shall we remove Many thanks again!! Could be a really good reference for discussion for upcoming admiralpeds @rossfarrugia |
Thanks Ben I will apply some changes as you suggested (and also for your other comments above ;) ) |
For the links it's not working because it's coming from my fork (if you replace on links pharmaverse by dgrassellyb it will work) - we won't have issues with links once it will be deployed in admiralci repo (non-forked one !) - I think it's nice to keep it (it's like a table of contents with redirections to detail documentation + workflows code) |
No description provided.