Support » Plugin: Gutenberg » the worst editor/builder

  • Automatic could made new tab in the editor with the gutenberg features, but not, the invent new layer, full page, to make inusable and incomplete solution.
    I disagree it at all

Viewing 3 replies - 1 through 3 (of 3 total)
  • Automatic could made new tab in the editor with the gutenberg features

    @jackalpret, this is exactly what I suggested a few days ago. Why not just have two modes–block, non block, and leave it at that? Let the kids who want to play with blocks and colors and images pick “blocks” mode. Let the adults who want to just input text use text mode.

    • This reply was modified 1 year, 5 months ago by rcnyc.
    • This reply was modified 1 year, 5 months ago by rcnyc.

    @rcnyc I agree with the idea that a Block tab could/should be the way to go, but Gutenberg is totally and fundamentally incompatible with the classic editor because it uses crazy new React codes in the markup to save block settings. It doesn’t use normal HTML that can be rendered by TinyMCE (and aren’t much use when you want to edit HTML in Text mode, for that matter).

    I’m frontend developer, I develop in Angular.
    All things can be converted, so, react can be showed in classic editor or in “code” editor … if not it can’t be showed in final frontend as html …

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘the worst editor/builder’ is closed to new replies.