As you've probably guessed, the method Drew describes means that once you've exported the site and added perch functionality to the code, you can no longer edit the design in Muse/Blocs.
However, if Muse or Blocs allow you to add snippets of code to the head (for <?php include($_SERVER['DOCUMENT_ROOT'].'/perch/runtime.php'); ?>) and php snippets in the page (eg: <?php perch_content('Heading'); ?> You could in theory get some Perch editability into the site without destroying your Perch work every time you export.
I can imagine it working fine for simple fields that use the content regions that come with Perch, like 'text', 'textarea', or perhaps even 'image'. For more complex areas, you'd need to use the code generated by Muse/Blocs to help create custom content templates before replacing them with a Perch Content Region snippet.
I've used Muse, Blocs and other WYSIWYG web editors in the past and while they appeared to speed up the design and build process, I often found myself burning time wrestling with quirks of the software and manipulating them to get what I want to achieve.
Switching to hand coding with the Bootstrap framework was a learning curve but it enabled me to break free from fighting with apps to get the desired result.
Yes, I made a video about this - you can see it here: https://www.youtube.com/watch?v=B94EO_Ub_kk
The video shows the Perch 2 interface, but the functionality is the same with Perch 3.
As you've probably guessed, the method Drew describes means that once you've exported the site and added perch functionality to the code, you can no longer edit the design in Muse/Blocs.
However, if Muse or Blocs allow you to add snippets of code to the head (for
<?php include($_SERVER['DOCUMENT_ROOT'].'/perch/runtime.php'); ?>) and php snippets in the page (eg:<?php perch_content('Heading'); ?>You could in theory get some Perch editability into the site without destroying your Perch work every time you export.You'd need to be able to change the file extensions to
.phptoo (unless you're able to set your server to parsehtmlasphphttps://docs.grabaperch.com/perch/getting-started/file-extensions/I can imagine it working fine for simple fields that use the content regions that come with Perch, like 'text', 'textarea', or perhaps even 'image'. For more complex areas, you'd need to use the code generated by Muse/Blocs to help create custom content templates before replacing them with a Perch Content Region snippet.
I've used Muse, Blocs and other WYSIWYG web editors in the past and while they appeared to speed up the design and build process, I often found myself burning time wrestling with quirks of the software and manipulating them to get what I want to achieve.
Switching to hand coding with the Bootstrap framework was a learning curve but it enabled me to break free from fighting with apps to get the desired result.