Adding and Managing Plugins
The plugin directory (1) is to WordPress.org what the App Store is to the Mac: the marketplace of native and third-party extensions which enable users to add new functionalities to their websites. In terms of making rational decisions, the criteria of choice to be taken into account are the same as when it comes to finding the right theme templates, with a few variations pertaining to security issues.
Considering indeed that from our conceptual perspective, the audit focus lies with the type of WordPress module which is integrated by default in OVH’s shared web hosting plans (2), the only extensions that hold real added value are those which will enable the administrator to honor the contractual terms that bind him to his web hosting provider (and vice versa), i.e.:
- to reinforce the global security of his installation, with a view to remaining compliant with criteria pertaining to the technical specifications of the web hosting server provided by the web host;
- to customize his installation according to the nature of his activity, i.e. of the paid products and/or services to be provided;
- to secure financial transactions in compliance with national regulations, through official payment modules;
- to integrate infographic added value without losing in reliability, by installing for example a library of additional widgets related to specific uses.
While it might seem difficult to make the WordPress core adapt to any type of existing professional configuration, although this is precisely the objective that provides for convergence in this direction, the fact remains that all safety reinforcement plugins should be native by default, i.e. provided by WordPress.
Further reading
(1) https://wordpress.org/plugins/
(2) https://www.ovh.co.uk/web-hosting/website/wordpress.xml
Please review the entire moderation codex as presented in the eight pages of the Feedback menu before publishing a contribution.