Archived topic
GeneratePress child theme files fusion with main theme
10 replies · Started by Jaakko Pöntinen on March 29, 2022
Hi.
I've had a project during which I've become confident in updating code relating to GP's core functionality. So much so that I am ready to handle updating the theme core files and parts of them I have in my modified template base manually should true need rise.
I'd like to merge my child project to the main theme.
Have some pointers for me as to what to expect? I'll up the version number to something nutty, keep the original functions.php (and just include() all my child theme's functions.php extensions) and style.css - enqueuing my child theme's stylesheets with WP's built-in style enqueue etc etc.
Broad question with nyances in execution, I know. Just maybe, something? :) Thanks!
Hi there,
i am not 100% sure what you need - this doc provides info on using a Child Theme:
https://docs.generatepress.com/article/using-child-theme/
it also includes a link to a blank child theme zip. If you use that then is fairly autonomous. You don't need to do anything special. Just add styles to styles.css, GP will enqueue them and functions to functions.php
Hi
If I understand your question you will modify core files from GP theme with those modifications you have in your child theme, rigth?
Bad idea.
The purpose of a child theme is making modifications without lose it when theme is updated.
If you have a function A in the child theme and a function A in the core theme, then the function A in the child theme is executed but the function A in the core theme not.
If you modify the file A in the core theme, when the core theme is updated, the changes are lost and you must to re-add these changes.
Heya,
Thanks, I know of child themes. Have built some 100 WP/Woo sites with them.
What I'm talking about is using a version of GP theme as a starter. Like Axio Starter (https://github.com/generaxion/axio-starter) or Air Light (https://github.com/digitoimistodude/air-light). These are themes that are meant to be built into. There won't be automatic updates - the developer is the updater.
In my use case I don't need GP to automatically update. I don't even want it doing so. If some majorly beneficial updates come to GP later on, I will - as I stated - manually bring over any and all needed bits.
This is a project that I'll be the lead dev on for years to come. What's basically needed of GP itself here are the semantics of navigation and of certain content, as well as the neatly packaged all around basis for developing.
So yeah, I want to merge what I've developed as a child theme of GP with GP itself, like I wrote :)
Thanks!
- JP
Sounds like you know what you're doing :)
What :D Do I? Yikes. Not so sure! I'll see how it goes.
Cheers!
To be honest - i didn't have a better answer :)
Let us know how you get on.
<3 Oh you :D
Wish me luck. I'll report back here when I've pulled my last hair.
- JP
Good luck 😀
Heya,
Just to give an update: It's death. I'm postponing this whole fusion-merger-thing and focusing on critical project tasks.
I went in, got my behind handed to me, aint going back anytime soon x)
All is well. I love GP <3
- JP
Glad to hear you still love GP :)
