Hello Forum, this is my first Post. I am currently building a site for a client who intends to change content and eventually create a new page or change the layout. I wonder if anyone here has experience how clients with no coding knowledge cope and how it´s best acomplished?
It would be superhelpful – i did search but i guess this is not a mainstream question
Haha I guess that not an option in that case. I plan to do a workshop where I explain the most parts. I was more curious about what is advisable to set up to make editing for content providers or people in an company as easy as possible, with some freedom to do stuff but not the possibilities to destroy or uglify the page …
Well you can use a front end form to create new posts, or edit existing posts. That lets you control the style but leaves the end user the ability to add content.
Not sure what works with Bricks as not reached that stage just yet. But in Elementor I used ACF Front End forms with ACF. If you have a look at WPTuts Paul has some good tutorials on a user dashboard.
Sorry no real experience with this on bricks just yet …
Sounds good, but how would you force the clients to only use Bricks? As I presume you can only limit what they can do within Bricks but not if they decided to use Guttenberg for instance?
I don’t really think Bricks is ready for client hand-off just yet (hopefully very soon!). There are a few things clients can do “on accident” that will be cause for many a headache. To quote Rick Cook:
“Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.”
Oxygen and a few other pagebuilders allow for custom fields and dynamic data that the client can just type whatever they need and the pagebuilder will pull that information into the relevant areas. This can drastically reduce the number of moving parts the client can touch.
I am pretty sure (although have NOT tried this myself) this can be done in Bricks as well using either ACF+CPTUI, Metabox, Pods, etc. and Gutenberg (edit as normal, not in Bricks) and scroll to the bottom where the custom fields are.
The Builder Access is the right path forward although, like Tim said, there are a few things not yet limited, so if you trust your client have at it.
The goal of Builder Access is to restrict certain functionality that might “break” the basic build. However, bricks is still just the theme, the framework that displays content - no matter what source.
Basically, I see it as long as the client wants to fill their site with content themselves, write posts, etc., they are responsible for that. However, you are just as responsible for taking the customer by the hand at the beginning and explaining in as much detail as possible (with the help of screen recordings or in writing) what is possible where and how what problems there might be and what he should avoid as much as possible.
The worst thing that can happen with limited access is that the customer makes sure that the page is not semantically correct (wrong order of headings), and ugly (wrong colors, fonts, etc).
And this can be prevented in advance. And then if something does go wrong, you probably get paid to fix it