Do not export seems for me the approach which fits more in the current workflow.
But that would mean, that PG has to generate all files which normally get auto exported whenever you turn your project into a WP-Theme into your project-folder (for flagging them later). So that you can manually pick then which files not to export, default could still remain then to export everything and as you do it with other files you would need to add the “do not export” to files you don’t want to be auto-generated!
Written in a few lines, but I guess could be not that easy to implement, as always with feature requests!
@iHuman why not use Function action or PHP code blocks directly in the header on the source page, so that any custom code is defined there and will be exported into the header.php? In this way, everything would defined be in the same place (in index.html for example).
@matjaz when I insert anything into Pinegrows header.php (includes, etc) it get’s overwritten. I guess I could add custom functions for meta-data etc in the functions.php file (wait…can’t edit that one either)…the custom.php file, but it’s not ideal. Any reason you overwrite header.php and functions.php? How about an option to disable overwrites selectively?
Most of the sites I was building prior to Pinegrow were all hand coded. (Also all Tailwind with Gulp) So I have a system of includes that works really well for me. It’s not necessary for me to have a visual editor like Pinegrow…but I do enjoy it! Pinegrow has convenient features. Can you explain why you overwrite certain files?
Great info @matjaz! Adding the logic for the header.php would be wonderful. Thank you. The more I use Pinegrow…the more I love it! I’ve coded sites without a visual editor, moved to Elementor for a while, then Oxygen. I came across Bricks and Pinegrow about the same time…and have been loving it! I’ve been spreading the word on an Oxygen group I’m part of. Pinegrow is a great app, with excellent support. Kudos!