-
Notifications
You must be signed in to change notification settings - Fork 6
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
Update Project section #171
Conversation
We may want to choose either the figure or the table but not both
Maybe replace this figure with a markdown table in the future
Moving these instructions to their own page
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.
Very nice overhaul of the project information. Impressive work!
Looking at the content - I wonder how much should live of that in the JupyterBook template vs the guidebook (https://github.com/uwhackweek/hackweeks-as-a-service).
From my perspective, we should keep the event specific information in the template and then have the guidebook for general approaches that are applicable for all events no matter what theme or year. Think we should start linking more between the two and have one be the manual (the guidebook) and the template as the execution of the guide book (this template). This would also assist in us having to manage less content in many places and keeps everything more consistent.
Curious what others think?
@JessicaS11 @scottyhq @aaarendt
book/projects/project_github.md
Outdated
1. Select “Manage access” on left side of page | ||
1. Add your team name under the "Manage access" section | ||
1. Select “write” to enable all team members to make commits | ||
2. Click “Settings” tab in upper right corner |
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.
In markdown land, I think it is preferred to let markdown take care of the numbering and only use 1.
to indicate a numbered list. Frees one up of having to manage the sequence.
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.
wow! today I learned! thanks :)
|
||
## Project Development Milestones: | ||
|
||
1. **May 21, 2024 - Project Leaders Kick-off Meeting** |
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.
Being a template, I wonder how we could generalize all these dates? 🤔
Today I learned that this is how markdown does numbered lists!
Closing this PR, will instead put this content in the guidebook! |
These are updates to the Project section of the jupyterbook template, which contains more information outlining what hackweek projects are, how project leaders are expected to go about forming a project, some tips on how to run a project team.
No doubt we'll want to make more changes and add more information as we learn from experience during the 2024 event.