Gutenberg styling to ACF text blocks

• Michael Heins

• March 19, 2019 at 4:36 am

Big fan of ACF and really neat how easy it is to build custom blocks with ACF, thank you for making that happen!

I have a question to understand what the road map of ACF and Gutenberg is like:
Currently the TinyMCE WYSIWIG editor still feels like the old WordPress. The new Headline / paragraph blocks are much more elegant and easy to use, especially when changing styles while editing. Also, when mixing normal blocks and ACF blocks the difference in style will make for a confusing UX for content managers.

Is it planned to move the text editing to something similar to the Gutenberg blocks (or have that as an option)? And if so, what is the timeline like?

• captiv8sam

• May 2, 2019 at 3:52 am

Would also like to know if there’s any plan to have the Gutenberg editor applied to WYSIWYG fields.

• John Huebner

• May 2, 2019 at 10:22 pm

My hope is that ACF will not use guberbug to replace the wysiwyg editor. If anything I would think this will be a new type of field, if it is added. In any event. I seriously doubt that Elliot will remove the old style wysiwyg field from the field types no matter what happens with WP. The field may need to be changed, but it should still be there.

• John Huebner

• May 3, 2019 at 3:02 am

Here’s another question, if you are going to build guberbug blocks then why on earth would you need an ACF field that emulates the guberbug editor? It’s going to eventually let you edit “side bars” or whatever they end up calling them, so there will be no real need to have different sections of blocks. The plan is to make the entire front end page editable with the new editor, meaning that there is no real reason to have separated “sections” to edit.

Why would you need another instance of the block editor?

And another question, why would you put a WYSIWYG editor into an ACF block built to work in guberbug? Wouldn’t you just create text fields, text area fields, and other types of fields and then format those fields in the block to appear the way they need to appear?

Are you asking, will ACF let you nest the block editor inside of itself? Why would you do this? Wouldn’t you just create multiple “blocks”?

After thinking about this for a while the entire question confuses the hell out of me as to what use it could serve.

Granted, I’m on the other end, I dislike guberbug and I feel it is a bad decision. That is based on knowing the types of clients I serve and what their needs are. The last thing my clients want is for any editor to be able to putz around with the site design. I plan to built in 100% ACF fields.

But I’m still paying attention to what’s going on and where this disaster is headed.

Please explain what purpose this could serve?