New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Kali Forms — Contact Form & Drag-and-Drop Builder | You have to log in to add a translation. | Details |
Original untranslated |
|||
| ↑ | Build contact forms for your WordPress website in minutes through the Drag & Drop builder and Guided Emails for entries notifications. | You have to log in to add a translation. | Details |
Original untranslated
Build contact forms for your WordPress website in minutes through the Drag & Drop builder and Guided Emails for entries notifications.
CommentShort description. You have to log in to edit this translation. |
|||
| ↑ | WORDPRESS CONTACT FORM PLUGIN | You have to log in to add a translation. | Details |
Original untranslated
WORDPRESS CONTACT FORM PLUGIN
CommentFound in description header. You have to log in to edit this translation. |
|||
| All build dependencies … | You have to log in to add a translation. | Details | |
Original untranslated
All build dependencies …
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Kali Forms is a WordPress form plugin suitable for businesses, web design agencies and anyone with a WordPress website. If you want to add a form to your WordPress website, Kali Forms provides a solid solution. | You have to log in to add a translation. | Details | |
Original untranslated
Kali Forms is a WordPress form plugin suitable for businesses, web design agencies and anyone with a WordPress website. If you want to add a form to your WordPress website, Kali Forms provides a solid solution.
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| For development with watch mode, use <code>npm run start</code> or the specific <code>start-*</code> commands. | You have to log in to add a translation. | Details | |
Original untranslated
For development with watch mode, use <code>npm run start</code> or the specific <code>start-*</code> commands.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| To build the plugin from source: | You have to log in to add a translation. | Details | |
Original untranslated
To build the plugin from source:
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| For specific examples of how bundled libraries are used and whether they make external calls, see the "JavaScript Libraries (Bundled)" section above. | You have to log in to add a translation. | Details | |
Original untranslated
For specific examples of how bundled libraries are used and whether they make external calls, see the "JavaScript Libraries (Bundled)" section above.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Any CDN references found in vendor files are either:↵ 1. Comment banners or attribution notices (like library name and version information)↵ 2. Optional features within bundled libraries that are not used by the plugin (such as optional output methods that require external resources) | You have to log in to add a translation. | Details | |
Original untranslated
Any CDN references found in vendor files are either:↵
1. Comment banners or attribution notices (like library name and version information)↵
2. Optional features within bundled libraries that are not used by the plugin (such as optional output methods that require external resources)
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| All vendor libraries are bundled locally within the plugin and do not make external network requests during normal operation. The source code for these libraries is available through their respective npm packages, and the bundled versions are included in the plugin distribution. | You have to log in to add a translation. | Details | |
Original untranslated
All vendor libraries are bundled locally within the plugin and do not make external network requests during normal operation. The source code for these libraries is available through their respective npm packages, and the bundled versions are included in the plugin distribution.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| A complete list of all vendor dependencies, including their versions and licenses, can be found in the <code>package.json</code> file included with the plugin. The dependencies are categorized as:↵ - <strong>dependencies</strong>: Runtime libraries required for the plugin to function↵ - <strong>devDependencies</strong>: Build tools and development dependencies used only during compilation | You have to log in to add a translation. | Details | |
Original untranslated
A complete list of all vendor dependencies, including their versions and licenses, can be found in the <code>package.json</code> file included with the plugin. The dependencies are categorized as:↵
- <strong>dependencies</strong>: Runtime libraries required for the plugin to function↵
- <strong>devDependencies</strong>: Build tools and development dependencies used only during compilation
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| The plugin includes bundled vendor libraries in <code>public/assets/backend/js/vendor.js</code> and <code>public/assets/frontend/js/vendor.js</code>. These files contain third-party JavaScript libraries that are compiled and bundled during the build process. | You have to log in to add a translation. | Details | |
Original untranslated
The plugin includes bundled vendor libraries in <code>public/assets/backend/js/vendor.js</code> and <code>public/assets/frontend/js/vendor.js</code>. These files contain third-party JavaScript libraries that are compiled and bundled during the build process.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| The plugin's JavaScript source code is located in the <code>resources/assets/js/</code> directory and is compiled into the <code>public/assets/</code> directory. The build process does not use code obfuscation or minification that makes code unreadable - only standard webpack production optimizations are applied. | You have to log in to add a translation. | Details | |
Original untranslated
The plugin's JavaScript source code is located in the <code>resources/assets/js/</code> directory and is compiled into the <code>public/assets/</code> directory. The build process does not use code obfuscation or minification that makes code unreadable - only standard webpack production optimizations are applied.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Kali Forms uses modern web development tools to build its frontend assets: | You have to log in to add a translation. | Details | |
Original untranslated
Kali Forms uses modern web development tools to build its frontend assets:
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| The source code for Kali Forms is available in the plugin directory. The plugin includes a <code>package.json</code> file that documents all build dependencies and development tools used to compile the plugin's JavaScript and CSS assets. | You have to log in to add a translation. | Details | |
Original untranslated
The source code for Kali Forms is available in the plugin directory. The plugin includes a <code>package.json</code> file that documents all build dependencies and development tools used to compile the plugin's JavaScript and CSS assets.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Plugin name.