The Classic Block isn't just the default block for when you publish from SiteContent You can also add additional Classic Blocks to one Page/Post.
This is where the hybrid mode starts to come in to play, as you are able to use other blocks, including multiple Classic Blocks, within a Single Page/Post.
This is great if you still want to work with the Classic Block, but you would also like to use the HTML Block for adding affiliate links to the end of the post. Or even in the middle if you have one classic block, then an HTML block and then another classic block.
To add additional blocks, including the Classic Block, you can click on the plus (+) icon at the top of the page, you can then either scroll through the list of available blocks, or you can search for "classic". Once you have found the Classic Block, or the block you require, you can click on it to add it to your Page/Post.
When you are ready to proceed, please click on the Next Page button below.
I have a question for you. If I remember this well, I saw in one off Jay's seminars, that there is a way to use a 'reusable block' for a table. But without changing every table in every post! Because, if I understood this correctly, it does change every table in every post. I hope you understand what I mean ? And someone mentioned a Ninja trick ( I think it was Sonja), to avoid the table from changing everywhere, so kind off creating a 'template' table, that you can fill in with different info each time. Could you tell me that trick please? I could go listen to every single video again but sorry would take me to much time , so I thought that maybe you would know ;-) Thanks !
Lizzy
But is it better than the classic editor?
Does it have a positive impact in search engine or something else?
I'm using the classic editor and I'm perfectly fine with that.
Just wondering what Gutenberg has of special...
Cheers
At the moment, I only know that by continuing to use the SiteContent to write our post, we get the benefit that WA platform will track when a post gets indexed by Google.
The downside I see is that when we published via SiteContent, it is really live in our website. Sometimes, I would like to further edit it in Wordpress first before really publishing, perhaps like adding the Featured image or using some advanced tabs that is available as a plugin. Hence, I thought it is not so viable anymore, at least in my case, to use SiteContent. But I do like it, just that it feels abit more extra work like having to publish first and then go to WordPress to immediately take it down to become draft mode again? I'm not sure what could be some solution for this. Any recommendation?
Thanks!
Can you explain why you need to have the Classic Editor plugin disabled when you publish from SiteContent to Wordpress?
Can I ask a non Site Content question? - Block Editor has been a huge headache/failure for me. I have the Classic Editor plugin enabled.
My writer is getting problems when she loads text into Classic Editor and then when she sees Block Editor. This only started on 18th June.
Her process is as follows
1. copy google doc text to WP classic editor
2. save draft and move to block editor
3. edit html codes and tables through block editor (we have a red button uses HTML code (current theme work around, note I am moving from this to Generate Press soon), and also to create tables)
4. save and go back to classic editor to edit heading colors "So the only things i do on the block editor is edit html codes and tables. also to arrange images sometimes. but i always start with classic, because its easy for me to find the blue color to edit the heading" "and i was so frustrated last night because all the text would disappear and become all this "conflicts" that I cant read the text and find where i want to edit."
So I have attached the Block Editor resolve conflict message and then after we resolve it. But the HTML text suggestions don't make any sense at time?"
Is there a better process to follow to prevent all this palaver?