make it a plugin, don’t add to core!

  • after more than 10 years of crafting custom themes and functions for my clients, i will probably leave wordpress if when this goes to the core

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Tammie Lister

    (@karmatosed)

    @getupworks, are you aware of the classic editor plugin? I ask as this means you can use the existing editor. That said, what is it you feel that is driving you from crafting custom themes in Gutenberg? I’d love to dig a little more.

    Thread Starter getupworks

    (@getupworks)

    @karmatosed i really appreciate you taking the time to reply to – from what i can tell – every comment on the plugin… anywhere. i’m sure by now you’ve heard all the cons and there’s really not much i could add there. what kills it for me are things like inline styles / accessibility, backwards compatibility, cooperation with existing plugins (like acf, which i use i.e. to create client specific layout builders), video embeds, backend clarity for clients.
    i am aware of the classic editor plugin, but it’s the wrong approach imo: the system should be as simple as possible, with the option to extend it as needed with plugins, not the other way round.
    i think the plugin you work on is very promising, but nothing that is needed by the majority of the wp users and therefor it shouldn’t be part of the core. why not make it “semi default” like that hello-dolly nonsense: ship it with the package, but still make it optional.

    • This reply was modified 7 years, 3 months ago by getupworks.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘make it a plugin, don’t add to core!’ is closed to new replies.