Tools That Can Be Used in Building

I mentioned this in a reply to another person’s post. To bring it to the surface more, I am reposting and elaborating on my thought.

I always have and notice that I continue to prefer “The Drupal Way” of providing high-level tools (modules) that can be used to build extensible and scalable sites rather than being provided solutions in the form of plug-ins. That approach reduces the plethora of plugins that must be maintained in the WP environ, while enabling the building of anything one can imagine – without WIXing it.

While devs find this approach attractive, the Drupal weakness has long been a ui that pushes non-techy clients of devs away from the table. Additionally, Drupal’s update process can be simply annoying. Add to that, it’s weakness in the ecommerce area.

Imagine bringing the great features of WordPress and the great features of Drupal together. The result would be innovative, a unique position in the CMS arena, and simply amazing.

Think about it? Consider it?


Read-only archive: https://petitions.classicpress.net/posts/114/tools-that-can-be-used-in-building

Author: Sunshiney

Vote count: 5

Status: open


Comments

Any interest in this? This sounds more like packages, which CP already includes for various functionality. Like PHPMailer, SimplePie, etc.

This is too large and vague to be actionable, but I still think other petitions like object relationships are heading in the same direction. Closing this in favor of making individual petitions for other, specific “tools”.

IMO, if we provide plugins that only ship “dev” oriented Apis without user interface, the only users who will ever potentially use this, will not be users in the common sense but devs.

In that case however, we can also think about permitting things we have until now dismissed because “dangerous for the users”.

So I don’t get the “core idea”.
Why do we want to ship plugins that are focusing solely on dev api, and leave the user behind by not providing a GUI, if we same time try to kill every request that somehow might endanger a “common” user?
A dev knows well what he does, or supposedly does.
So forbidding SVG upload, or a rename of files, because the users will do messes and get their sites in danger (which makes total sense), but then provide things that are dev focused and do not come with an UI (which is really the only thing differentiating this sort of CMS from a PHP implementation with database), … is weird, I think.

Out of 10 or 100 or 1000 users, how many can actually write PHP or deal with APIs?
And why do folks use a CMS that has a GUI?
IMO, Because either one can’t write code or because one wants to save time.
So a plugin with just API but no GUI is… useful, but not really (not for most).

So for one I agree that the petition is not focused and does not really let you act on anything anyway, but on the other hand I also don’t think that this should be our main focus.
The GUI is what makes these CMS useful, along with the APIs which are necessary to even have a GUI. But without GUI, WordPress would not have 50 million websites done with it. And Without GUI, I think the current CMS is actually too limiting, because a dev will just use a framework that does not lock him into the limitations of a GUI. Is it not too late to make the CMS a “less GUI more Dev” oriented thing?

The whole idea of this is to allow anyone possibly to manage his/her site. Am I wrong with this?
So for me if anyone wants to provide a plugin with just code, be my guest (I do the same when I do not have time to actually provide settings and GUI interface)
But that should not be the standard in CP, I think?

2 Likes

I agree completely. If it has no UI, it should almost always be a plugin. (There are some exceptions, such as things to go in the wp-config.php file, but not many.)

1 Like

This topic was automatically closed after 7 days. New replies are no longer allowed.