oceanhackweek / oceanhackweek/oceanhackweek.github.io
Near-final updates to OHW23 pages
Open
@emiliom is already working on this.
Since Aug 1, 2023.
- Dominant language
- CSS
- Stars
- 12
- Forks
- 49
- Avg merge
- 19m
- Merged PRs (30d)
- 1
Description
Here are the pages that still need updating to OHW23. @alisonpchase @btupper and @emiliom, let's add our names next to the pages we will tackle. Thanks!
@btupper this is a good time to revisit your tutorials PR, https://github.com/oceanhackweek/oceanhackweek.github.io/pull/260. Let's discuss it there.
Pages in the ohw23 directory
- https://oceanhackweek.org/ohw23/index.html AC once appropriate, remove admonition
- https://oceanhackweek.org/ohw23/schedule.html EM
AC will link in the new table once it is finalized - https://oceanhackweek.org/ohw23/logistics/index.html EM. #268
- https://oceanhackweek.org/ohw23/projects/index.html BT (EM already made an update. See if it needs edits and additions!)
- https://oceanhackweek.org/ohw23/tutorials-index/index.html (maybe just a very brief intro paragraph/section? The rest will be a table of content that's auto-generated, I think) BT
- https://oceanhackweek.org/ohw23/tutorials_getting_started.html EM #270
Pages in the resources directory
- https://oceanhackweek.org/resources/index.html
- https://oceanhackweek.org/resources/prep/git.html AC (change all references to
ohw22-projtoohw23-proj?) - https://oceanhackweek.org/resources/prep/jupyterhub.html (we should replace the JupyterLab screenshot at the end of jupyterhub.html#how-do-i-access-the-shared-cloud-environment; the one there is outdated and misleading)
- https://oceanhackweek.org/resources/prep/conda.html#installing-conda (no ohw23 updates needed per se, but we should add content here with our recommendation for installing conda/mamba locally on one's computer; and add the content from Filipe's 2022 Managing conda environments screencast)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.