attention for developers is lacking

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter JoshuaDoshua

    (@dkampdesign)

    5 years, 8 months ago

    Things that would make me feel less cringy:

    – ability to disable almost half the settings.
    – especially Text Size and color.
    – inline styles are not responsive.
    – ability to disable a bunch of those blocks

    • This reply was modified 5 years, 8 months ago by JoshuaDoshua.
    Thread Starter JoshuaDoshua

    (@dkampdesign)

    5 years, 8 months ago

    this templating system seems like it’s going to add hours and hours to dev time, making it less likely we go with WP as a cms for client builds

    • This reply was modified 5 years, 8 months ago by JoshuaDoshua.
    • This reply was modified 5 years, 8 months ago by JoshuaDoshua.
    Thread Starter JoshuaDoshua

    (@dkampdesign)

    5 years, 8 months ago

    Wait, is this going to be the default editor for WordPress.com? or for the CMS as downloaded from WordPress.org?

    The target market for an “editor” (I would call it a “page builder” rather than an editor”) is for non-developers, i.e. WordPress.com users. The target market for those that download the CMS and implement it themselves would be devs right?

    Why not make it default for WordPress.com and a pre-installed plugin for WordPress.org?

    I don’t think this is a bad editor. It’s relatively easy to use and offers pretty much anything you can think of. But I wouldn’t want it on any of my clients’ admins.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘attention for developers is lacking’ is closed to new replies.