Replies: 1 comment
-
Hello—Thanks for posting this! A long time ago, when I used _s, I had a handful of changes I made every time I started a new project. I kept a list, and after generating a new theme, I would manually make those changes because it only took ten or so minutes. Eventually, the number of changes I made started to grow, so I forked the _s generator. This was also a long time ago, so at the time the generator was still being updated. (It hasn't been in seven years.) I ran it locally, so I would go to something like underscores.test on my own machine, and it would produce a version of the theme with my changes. I would keep it updated as _s evolved over time. You could do something similar. The one downside for you is that the code for the _tw generator is not public because it's based on very old code, and I haven't overhauled it to the point that I'm comfortable sharing it publicly. That said, you could use the _s generator code as a base if you wanted to go that route, or you could create a similar generator or script from scratch. A shell script that made some minor modifications to a theme generated by underscoretw.com could also potentially solve your problem, and that's the sort of thing an AI code generator would do a pretty solid job of putting together. And since it never would run in production, it's pretty low stakes. Hopefully that helps—good luck with your projects! |
Beta Was this translation helpful? Give feedback.
-
Hello
Thank you for your hard work.
I want to use _tw as a base for a theme of multiple clients with some basic style change between them.
What would be the best option ?
The second option would be the best for me, as I would be able to update the theme in the future without having to redeploy a large number of themes.
Thank you for your answer.
Kind regard
Beta Was this translation helpful? Give feedback.
All reactions