Date: June 11, 2025
We are seeking a qualified WordPress plugin developer to create a simple, white-label plugin designed for submission to the official WordPress Plugin Directory. The primary function of this plugin will be to provide a mechanism for users to access an external, pre-existing webpage containing a form. The plugin itself will not require complex functionality beyond this integration.
To provide WordPress users with a straightforward way to access our external form.
To ensure the plugin adheres to all WordPress coding standards and security best practices.
To achieve official inclusion in the WordPress Plugin Directory, enhancing discoverability and trust.
To implement a reliable system for tracking plugin installations and deinstallations.
The plugin shall:
Provide a clear and intuitive method (e.g. a menu item in the WordPress admin) for users to integrate and link to an external webpage.
Upon user interaction, open a pre-defined external webpage (URL will be provided by the client) in a new browser tab/window or within an iframe on the WordPress site. The preferred method (new tab/window vs. iframe) will be discussed during the project initiation phase.
The external webpage contains a form that the user will interact with; the plugin itself is not responsible for processing or storing data from this form.
The plugin must be developed as a “white-label” product, meaning:
It should contain no branding or explicit references to the developer’s company or individual name within the plugin’s user interface (admin screens, public-facing elements).
The plugin header (as described in the wordpress-plugin-guide immersive, including Plugin Name, Author, Author URI, etc.) will be customized with client-provided information.
The developer is responsible for, or will provide comprehensive assistance with, the full process of submitting the plugin to the official WordPress Plugin Directory (wordpress.org/plugins/).
This includes ensuring the plugin meets all WordPress.org requirements, preparing the readme.txt file in the required format, and guiding through the review and approval process.
A successful submission and listing on WordPress.org is a critical deliverable.
The description page for the plugin (as displayed on WordPress.org and linked from the plugin within a WordPress installation) must be professionally designed.
The design should ideally leverage Elementor for ease of future client modifications, but alternative robust design approaches will be considered if justified.
The client will host this description page, and the developer will be responsible for providing all necessary assets (e.g., HTML, CSS, images, Elementor templates/exports) for this hosting.
Download Feature: The description page must include a prominent download feature (e.g., a button or link) allowing users to download a specified file (e.g., a .zip archive, or other format as agreed upon). This feature will link to a file hosted by the client.
Code Quality: The plugin must adhere strictly to WordPress Coding Standards (PHP, JavaScript, CSS).
Security: Development must prioritize security, including but not limited to:
Preventing direct file access (if ( ! defined( 'ABSPATH' ) ) { exit; }).
Proper sanitization and validation of any input.
Correct escaping of all output.
Appropriate capability checks for administrative functions.
Protection against common vulnerabilities like CSRF and XSS.
Performance: The plugin should be lightweight and optimized for minimal impact on website performance.
Compatibility: The plugin should be compatible with the latest stable versions of WordPress and common PHP versions used in WordPress hosting environments.
Internationalization (i18n): All user-facing strings must be properly internationalized using WordPress’s __() and _e() functions, with a defined Text Domain and Domain Path.
No Database Interaction (within plugin): The plugin is not expected to create custom database tables or store user data directly.
We require a mechanism to track plugin installations and deinstallations. The proposed solution should:
Provide accurate counts of active installations and deinstallations over time.
The method of data collection and delivery (e.g., direct access to a dashboard, API endpoint, periodic email reports, integration with a third-party analytics service) is open for discussion and proposal by the developer.
Upon project completion, the following deliverables are expected:
Complete Plugin Source Code: Well-documented, clean, and organized PHP, CSS, and JavaScript files for the plugin.
Installation & Usage Documentation: Clear instructions for installing, activating, and using the plugin.
readme.txt File: Formatted correctly for WordPress.org submission.
WordPress.org Submission: Successful listing of the plugin in the official directory OR detailed guidance and support during the submission process.
Tracking Implementation: Fully functional system for installation/deinstallation tracking.
Plugin Description Page Design Assets: All necessary files (e.g., Elementor templates/exports, HTML, CSS, images) required to host the designed plugin description page. This includes implementation for the download feature.
Interested developers are requested to submit a proposal that includes:
Company/Individual Overview: A brief introduction to your experience and expertise in WordPress plugin development.
Relevant Experience: Examples of previous WordPress plugins developed, especially those submitted to the WordPress Plugin Directory or involving similar integration/tracking requirements.
Proposed Technical Approach: Outline how you intend to meet the functional and non-functional requirements, including:
Your strategy for opening the external webpage (new tab/window vs. iframe, and how it will be triggered).
Your proposed solution for tracking installations and deinstallations, including how the data will be accessed/delivered.
Your approach to designing the plugin description page, especially your familiarity with Elementor or alternative design tools, and how you will implement the download feature.
Any libraries or specific WordPress APIs you plan to utilize.
Estimated Timeline: A realistic timeframe for completing the project, from commencement to WordPress.org listing.
Cost Breakdown: A detailed cost estimate for the entire project, including any potential milestones or payment schedules.
Maintenance & Support: Information on post-launch support options, if available.
Not enabled on this site