It could fit nicely in the collaboration pillar?

we could use GitHub actions and issue comments to replace some of the templating features. Like slash commands to create a new blog post with some parameters, and it can create the file with the name, and the date in the right place, with some placeholder content to fill out in a new branch and draft pull request.

We just need to think about how non-UGRC people could do this or if they could do this. No Portor issues don’t need blog posts they need sgid index entries.

I like the idea of issue templates + github actions that respond to slash commands in comments. The only bummer would be that as a user, I could create the issue but then I would have to wait for one of us to approve it before I can start working on the content. Why not just create the branch and draft PR when the issue is created? That seems like a relatively cheap operation. If it starts to become abused then we could work in checks like validating that the user who opened the issue is part of a specific team.

Works for me! We need an external user story but that can come later

internal story is complete.