Extension Structure – Localizing Extension’s Description

Make sure more people notice your extension by translating your
extension’s description into various languages.

Separate description files are created for translated description.

• Description files are using the Markdown format (.md).
• Description files are stored in the /_meta/descriptions/
  directory.
• Multiple description files may be created, one for each different
  locale. An appropriate file is chosen based on the active Plesk
  locale.
• The name of a description file matches its locale ID: en-US.md,
  de-DE.md, ru-RU.md, etc.

Based on the locale used by Plesk, the description from the appropriate
description file is displayed. If the appropriate file is unavailable in
the descriptions/ directory, the description from the
DESCRIPTION.md file will be displayed.

Here is a sample description file for an extension released by Plesk.
Feel free to use it for reference.

To help you meet the evolving requirements of your customers, Plesk Onyx comes with Docker support.
Here is what you can do with it:
 - Have on-demand access to a wide range of modern technologies,
   such as redis, mongodb, memcached, and many more.
 - Choose from a catalog of available images, or upload a custom image.
 - Deploy and manage Docker containers straight from the Plesk interface.
 - Install Docker containers locally, or to a remote node registered in Plesk.
[Learn More](https://docs.plesk.com/en-US/current/administrator-guide/web-hosting/using-docker.75823/)
*This extension is **FREE** with Plesk. You can also get remote node support for only $5.00 a month.*