1. Choose a theme or plugin that solves a specific customer need. Check its supported WordPress and PHP versions, maintenance history and any required service subscription.
2. Obtain the package from its legitimate source. For WordPress.org items, use the supported catalogue entry; for uploaded packages, use a valid ZIP from the developer or your authorised distribution.
3. Open the relevant library in the Hosting Suite administration area and add the package through the available source option.
4. Enter a clear customer-facing name and description. Explain whether a separate licence, account or activation step is required.
5. Review its plan availability, then open a test website's Design or Plugins section and confirm it appears in the intended selection, including Picked for your plan where applicable.

Use a new or staging website. Install the package, confirm its expected files and check that the site remains functional. Theme activation can change the site's appearance. Plugin activation may need a separate step or additional configuration, so do not describe installation alone as a completed integration.

The website-level Upload a plugin workflow accepts one valid plugin ZIP and prevents overwriting an existing plugin folder. The interface's package limit is 40 MB, while PHP or web-server upload limits can be lower. An upload failure should be investigated against both limits and the ZIP structure.

Review curated packages after major WordPress or PHP changes. Remove recommendations that are no longer suitable and replace their descriptions where setup requirements have changed. Keep your internal record of the package source, licence conditions and validation date.

Adding a package to a library does not update or activate it across every customer's existing website. Plan any existing-site rollout through the appropriate website management and backup process. Never overwrite a plugin directory simply to work around an installer conflict.

Check whether the existing installation should be updated through its normal vendor or WordPress mechanism. Ask the customer to confirm their licence rights and avoid requesting licence secrets in a public ticket. If support needs access, use your established secure access procedure and record the specific change you are authorised to make.

• Prepare a cPanel server for managed WordPress plans
• Set a WordPress update policy and validate changes in staging
• Define and test the backup scope of managed WordPress plans
• Choose customer tools for application hosting plans

• cPanel: manage WordPress with WP Toolkit