arctraining/hackpad-templator

GitHub action based repo for generating HackMD pages for training sessions

hackpad-templator's Issues

Update hackmd-cli version

Hackmd-cli is now on v2.0.0, should look at updating this.

Create template for hpc0-2023-11

Image tokens expire after 7 days

Converting repo to public will resolve this.

SWD1a agenda appears as a preformatted block

After running the hackpad for swd1a in person the agenda appears as a preformatted block rather than a markdown table.

This is because the section is indented.

Create a new hackpad for hpc1-2023-11

Set-output in GitHub action will soon be deprecated

Update github action to not use set-output.

Fix links

The links here are not working

hackpad-templator/templates/hpc0.md.j2

Lines 21 to 22 in e0fcb30

	- **Slides for today** - https://bit.ly/hpc0linux
	- **Exercises for today** - https://drive.google.com/file/d/1dV8fMS_n6GOFZO_rmFfUBwnuBFGj6C58/view?usp=sharing

change the slides to: https://docs.google.com/presentation/d/1-iMN4PQ8gt2HEw5kERHDSY-OzcFK-Rrz/edit?rtpof=true
change the solution to: (?)

Creating duplicate hackpads

I usually create a hackpad by navigating to the GitHub repository, clicking full stop on the keyboard and getting the quick github.dev editor.

Within this I create a branch and update the config and add this commit (which is automagically pushes to the repository).

However, this always leads to duplicate hackpads being created because the action runs on any push to a branch that isn't main, dev-* or master. So the very action of creating a new branch triggers the create template action.

The simple fix for this is for me to not use this method of creating a hackpad branch and just do it locally or via a codespace. This should be documented potentially to avoid this issue.

Update template files for in person training

Currently template files work on the assumption the training is half days. When training is in-person the schedule should be for a full day 0930-1600.

Suggested changes:

• config.yaml should have different syntax:

date: "2021-11" 
timing: all-day # accepted values being `morning`, `afternoon`, `all-day`

The jinja logic will become:

{% if timing == "morning" %}
Morning timetable
{% else if timing == "afternoon" %}
Afternoon timetable
{% else if timing == "all-day" %}
All-day timetable
{% endif %}