oceanhackweek / oceanhackweek/oceanhackweek.github.io
Renaming and rearranging resources
Open
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 12
- Forks
- 49
- Avg merge
- 19m
- Merged PRs (30d)
- 1
Description
Maybe a renaming/rearranging is in order at some point, so we have:
- Logistics
- Getting Help
- Preparation (link to various pages/guides)
- Python/R learning resources
- Tutorials
- Projects
- Reference (how does the environment, work)
- Git
- Github
- JupyterHub
- Conda
- Guides (how to accomplish small specific tasks)
- Git setup
- Cloning tutorials
- Git workflows
Originally posted by @abkfenris in https://github.com/oceanhackweek/oceanhackweek.github.io/pull/175#issuecomment-1206481787
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.
Research direction
Review the current site navigation and the pages linked from it, then compare them with the proposed Logistics, Tutorials, Projects, Reference, and Guides structure. Done means agreeing on an information architecture and rearranging the relevant links or pages accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, python, r
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100