Wordpress plugin

[thtmnisamnstr]

GitHub Sponsors Bounty

Bounty Amount: $2,000

*** DO NOT SUBMIT A PULL REQUEST FOR ANY BUG OR ENHANCEMENT WITH AN ASSOCIATED BOUNTY UNLESS IT IS ASSIGNED TO YOU. PULL REQUESTS FROM UNASSIGNED CONTRIBUTORS WILL BE REJECTED. ***

How Bounties Work

• Apply to work on this via the Google Form here. You can apply as an individual or as a team.
  • Provide the issue number, a link to the issue, GitHub usernames for you and all team members, a single contact email, an estimated date that you think you could complete work by, and a brief note on why we should select you/your team.
  • You and everybody on your team must have GitHub Sponsors enabled. Details on how to enable GitHub Sponsors on your account are here. If you are on the GitHub Sponsors waitlist and are selected, we will work with GitHub to get you approved quickly.
• If we are interested in your application, we will reach out via email. If we aren't, we will do our best to reach out in some way as well.
• Once a contributor is selected, they will be assigned the Issue in GitHub, and applications will be closed.
• After completion and a PR has been approved (not necessarily merged) by RudderStack, the contributor will be paid via GitHub sponsors in the most expedient way possible (e.g. until one-time payments are implemented for GitHub Sponsors, if bounty = $2500 => 2-months of $1000 sponsorship and 1-month of $500 sponsorship).

Enhancement Info

Description

WordPress is widely used. It's estimated that almost 40% of all websites on the internet are powered by WordPress. Event capturing in WordPress can still be difficult to implement though. Adding a tool like RudderStack to your WordPress site makes sense for a few reasons:

1. You want to reduce the lib payload as much as possible. Using one library, like RudderStack, instead of multiple, tool-specific libraries will make a big difference in the performance of your site, and that’s important for a technology stack that has speed and latency as one of the main value drivers.
2. You want to reduce the number of deployments. By incorporating RudderStack, the developer can deploy one library/plugin and be enabled to continually add external apps that will receive the events on the backend without redeploying.

Implementation

The implementation will be a plugin for WordPress. The plugin can be similar to the deprecated Segment plugin that can be found here. The implementation should be pretty straightforward and include:

1. A way to track custom events from within WordPress.
2. A way to automatically catch page views and send them to RudderStack.
3. The plugin should implement or wrap as much of our JavaScript SDK here as is possible.
4. The plugin must comply with the Wordpress plugin guidelines.

Nice to have features

1. It would be awesome if the plugin could create a “schema” of the events that are being tracked across the project.

Additional resources

• WordPress Plugin Developer Information
• WordPress Plugin Developer FAQ

[theafolayan]

Hi @thtmnisamnstr I'd like to take this up and get started over the weekend. I expect I should be able to wrap up an MVP version in about a week.

[thtmnisamnstr]

Hi @theafolayan,

I'm not working at RudderStack anymore. So I'm not sure if this bounty still stands.

@ryanmccrary can you help out here?