Open nickcernis opened 5 years ago
I actually like both approaches, and don't think we should exclude either one, necessarily.
But we do likely need to prioritize. We can throw both of them in our backlog and let @bryankennedysmith help us make that decision.
Sounds good. We could start with npm run rename
, then potentially run that same command in an environment from the website to rename and generate custom themes.
This would be an outstanding feature to be able to automatically rename any of the StudioPress child theme names thought a script or a website theme generator. All my custom design sites are started with Genesis Sample and even when a client wants to use a StudioPress child theme I still rename the theme because eventually, I know they are going to want something customized about the website.
This looks useful https://www.npmjs.com/package/theme-claim
Automattic open sourced the underscores.me site and generator here: https://github.com/Automattic/underscores.me
I hacked together this last plugin last night. It adds a wp-cli command for Genesis, grabs genesis-sample-master and updates the things. Having some trouble with Author and URI stuff but the slug transformations appear to work. https://github.com/jayhill90/genesis-generator
@jayhill90 Nice work! I found a couple of Sample strings still present, but otherwise this looks like a great start: https://github.com/jayhill90/genesis-generator/issues/24
Thanks @nickcernis! I've gotten that sorted out now. Definitely some more improvements to be made but this should help people starting from a scratch Genesis Sample theme.
Created a Node package for renaming/replacing strings - https://www.npmjs.com/package/genesis-theme-claim
If Genesis Sample is to be widely used as the starting point for custom Genesis child themes, it would be helpful to have a way to rename the theme more easily.
Common approaches are:
npm run rename
command that prompts people for the new name and replaces all genesis_sample strings and variants.