frontend do not work

[leokolt]

Hello! Why all my styles work only in the backend of the site and in the frontend do not work? I'm using the file editor-formats.json

[aprokopenko]

The plugin doesn't add any styles on frontend. Editor styles are usually very simple and they should not be placed on frontend.

Even standard WordPress theme has separate CSS for editor.

The main idea of the plugin - to add the ability to add some CSS classes or wrap elements with pre-defined div blocks without editing the size code in "Text" mode.

This gives you the ability to make more advanced styling comparing to standard WordPress editor.

Like for example when you use bootstrap in your theme -it has a lot of classes for formatting, however you can't set them from the editor.

[bw-everstring]

If this doesn't place styles on the front end, then what is the purpose? Why would I create a style/format that can only be used in the editor?

There is a huge opportunity for an editor that would allow users to manage these add on styles without having to get into FTP'ing files, particularly if it wrote styles to editor-style.css

[aprokopenko]

The plugins is suppose to be used by developers, not by final clients to add something to their editor.
This plugin is used when you have custom design and need to implement it into the theme. Within this design content parts may have special styled elements (like buttons, tables, headers etc). To allow client choose this without remembering class names or IDs of the dom elements - we created the plugin to set this preferences inside the editor Formats dropdown.

But plugin suppose that these styles are already exists inside the theme css.

I can open discuss somewhere and maybe add new option to print styles to the frontend too. But complex styling can break the WordPress editor, so it's not recommended to use editor styles as real styles on the frontend (because they require media queries for responsive html, ::before, ::after statements etc)

[bw-everstring]

Hi Alex - thanks for chiming in. Here is the use case: Client wants to use a different heading styles in blog posts vs other page types. The do not want to manage styles in at the code level in a spread sheet (too technical for them) and it needs to be easy for a non-technical content writer to apply from within TinyMCE. Their current theme allows most of the heading styles to be managed from Customizer. Custom post types are an option as well, but the idea was being as non-invasive as possible and adding custom classes that can be easily managed without having to FTP files or edit them within the file editor. Think artist logic - they want to 'see' what they are working on, visual 'styles' should all live in the same spot. On the editor side of things, your plugin is great - it's easy enough for the non-technical users to figure out with an example. If that could carry over to the front end...perfect.

…

On Thu, Jul 27, 2017 at 3:19 AM, Alex Prokopenko ***@***.***> wrote: The plugins is suppose to be used by developers, not by final clients to add something to their editor. This plugin is used when you have custom design and need to implement it into the theme. Within this design content parts may have special styled elements (like buttons, tables, headers etc). To allow client choose this without remembering class names or IDs of the dom elements - we created the plugin to set this preferences inside the editor Formats dropdown. But plugin suppose that these styles are already exists inside the theme css. I can open discuss somewhere and maybe add new option to print styles to the frontend too. But complex styling can break the WordPress editor, so it's not recommended to use editor styles as real styles on the frontend (because they require media queries for responsive html, ::before, ::after statements etc) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AYgXpwfiYpd-17gikG88KRrWrBotXtGOks5sSGQigaJpZM4MV15I> .