Open izmeez opened 2 months ago
The whole discussion is only 20 minutes and worth a listen.
For clarity: what needs to be done is to use GitHub actions to "inject" the build assets into the .zip that is built with each project release - these assets will NOT be added to the codebase (it should be kept "clean" in order to not cause problems for developers and the maintainers of the theme).
In zulip it was also mentioned
Using GitHub actions will only help if someone uses the theme exactly the way it is defined in the stylesheet. If they want to customize it for their own site they'll need their own workflow for building it
and I was wondering how will the repo work for PRs. Will a fork need to build the components?
Here's some info on the build process https://tailwindcss.com/docs/installation. As I was saying, any change to any style to adapt to a specific site requires running npx. So I don't think GitHub actions will provide much value.
While listening to the, Backdrop weekly development meeting for June 13, discussion on the Stanford Decanter Theme, it was interesting to hear that github actions can be used to build the additional required components and include them in the release zip. This would mean the theme would be usable on download by anyone, without extra effort. Is this worth further consideration?