GeezerVison

I remember there was something about tracing possible links in our videos that we'd need to keep active. Do we need to address this here too?

I remember there was something about tracing possible links in our videos that we'd need to keep active. Do we need to address this here too?

I'm not sure about this - do you mean links referenced in the videos? If so, that would probably need a redirect/permalink set up in the new Hugo site. Happy to take a look, but would prefer raising as a separate issue.

Why does it appear that we are making functional code changes, here? Is it just refactoring?

I remember there was something about tracing possible links in our videos that we'd need to keep active. Do we need to address this here too?

I'm not sure about this - do you mean links referenced in the videos? If so, that would probably need a redirect/permalink set up in the new Hugo site. Happy to take a look, but would prefer raising as a separate issue.

Created #393 for this.

Why does it appear that we are making functional code changes, here? Is it just refactoring?

Should just be a refactor, but it is quite a big one. I've pulled logic out of generate_hugo_learning_path_markdown.js and put it into generate_learning_path_markdown.js, which might be why it looks like functional change.

I'd like to review by actually trying this out but not sure exactly when I'll have time.

No worries @rrrutledge, I don't think this is blocking anything right now so no rush.

Sounds like this could be ready to be used in GitHub actions for automation purposes?

Sounds like this could be ready to be used in GitHub actions for automation purposes?

I think so - just need to wire it up.