Why force a custom page builder to change the look of course pages?

  • Alvaro Gois dos Santos

    (@alvarogois)


    2 months, 2 weeks ago

    I understand that for those who develop paid themes and plugins, accommodating the block editor’s multiple changes, delays, and poor decisions can be frustrating and can stall development. But the decision to develop a custom page builder (Droip) to manage courses and course archives is absurd.

    OK, it might not be absurd from an economic standpoint, because it’s just another add-on they can sell to anyone who wants to change the look of archive pages. But for those who want to maintain a clean workflow, without adding plugins and new ways to edit content beyond the native one, it’s a huge step backward.

    I refuse to add another page builder to do something that should be handled by the native WordPress editor, even if it were in a simplified version.

    I invested in the premium version some time ago, when no other plugin was necessary. Now I’m frustrated that I can’t fully utilize the plugin’s potential. Bad move.

    It seems I’ll have to do some intensive research on LMS plugins again. This is the second one I’ve abandoned due to poor development choices they make.

Viewing 1 replies (of 1 total)
  • Plugin Support Md Rashed Hossain

    (@wprashed)

    2 months, 1 week ago

    Hello @alvarogois

    I understand your frustration. WordPress’s block editor changes often stall our development, and Droip was built to give users stable design control over courses/archives without waiting on core updates. It’s optional—native editor still works. Many prefer flexibility, but your feedback matters and helps shape our roadmap.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this review.