Description
Reepl combines a public post feed embed with an inbound article publisher.
Features:
– Simple setup using one Public Profile URL in admin settings
– Interactive settings preview so you can pick a layout before publishing
– Built-in layout presets: LinkedIn Grid, Clean List, and Minimal
– Shortcode-based rendering
– Grid and list layouts
– LinkedIn-style post cards (header, content/media, reactions, actions)
– Optional author/date visibility controls
– Optional profile header and per-post stats
– Optional Reepl-branded header pill, enabled with an explicit show_branding="true" shortcode attribute
– Cached feed fetching via WordPress transients
– One-click connect to a Reepl account, with no WordPress password required
– Signed Reepl webhook endpoint at /wp-json/reepl/v1/articles
– Idempotent article create/update by Reepl postId
– Optional native WordPress tags, excerpts, slugs, and featured images
– Publish incoming articles immediately or save them as drafts
Shortcode examples:
– [reepl_posts]
– [reepl_posts preset="linkedin_grid"]
– [reepl_posts preset="clean_list"]
– [reepl_posts preset="minimal"]
– [reepl_posts profile_url="https://app.reepl.io/public/profile/your-user-id"]
– [reepl_posts limit="9" layout="grid"]
– [reepl_posts show_branding="false"]
External services
This plugin connects to Reepl’s public API to display public posts, profile information, media URLs, and profile statistics for the Reepl profile selected by the site administrator. The service is operated by Reepl (Autodeus Technologies Private Limited).
When a page containing the [reepl_posts] shortcode is rendered and the feed cache is empty or expired, WordPress sends the configured public profile’s Reepl user ID and requested post limit to the Reepl API at https://4n7fgax35e.execute-api.eu-north-1.amazonaws.com. The API response is cached in a WordPress transient for 10 minutes. Media URLs returned by the API may be requested directly by the visitor’s browser from their respective media hosts.
The plugin also supports an optional administrator-configured feed_url shortcode attribute. When used, WordPress sends an HTTP GET request to that URL when the feed cache is empty or expired and renders the returned public feed data. Site administrators should use only services they trust and review those services’ terms and privacy policies.
To connect a Reepl account, the site administrator clicks Connect to Reepl in the plugin settings. WordPress generates a random secret, sends it to Reepl’s API together with the site URL and site name, and redirects the administrator to Reepl to approve the connection. Once Reepl confirms the pairing, the secret becomes active. No WordPress username or password is ever sent to Reepl.
For article publishing, once connected, Reepl sends a signed article payload to the site’s WordPress REST endpoint when an article is published. The plugin verifies the signature and creates or updates a local WordPress post; it does not forward that payload to another service.
Reepl’s legal documents are available at Terms of Service and Privacy Policy.
Installation
- Upload the plugin zip.
- Activate the plugin through the “Plugins” menu in WordPress.
- Go to Settings > Reepl and open the Display post feed tab.
- Paste your Public Profile URL, choose a layout preset, and check the preview.
- Add
[reepl_posts]to any page or post. - Open the Publish articles tab, click Connect to Reepl, and approve the connection in your Reepl account. Article publishing starts working automatically once the connection is approved.
- Choose whether incoming articles should be published immediately or saved as drafts, and save.
FAQ
Do I need a Reepl account?
Yes. The shortcode embed needs a public Reepl profile to display, and article publishing needs a Reepl account to send the signed webhook.
Is my WordPress password required?
No. The plugin never asks for your WordPress username or password. Connecting to Reepl generates a random, scoped secret on your site, and that secret is used only to sign incoming article webhooks. It cannot be used to log in to WordPress or to perform any action other than the signed publishing request it was created for.
What happens if I disconnect?
Disconnecting clears the stored secret from your site. Reepl can no longer publish articles to this site until you connect again. WordPress posts that were already published are not removed.
Does it work with any theme?
Yes. The shortcode renders standard HTML and CSS scoped to its own class names, and published articles are created as native WordPress posts, so they use your theme’s normal post templates.
What data leaves my site?
When the shortcode is used, your configured Reepl user ID and the requested post limit are sent to the Reepl API to fetch the public feed. When connecting to Reepl, your site URL, site name, and a generated secret are sent to Reepl to complete the pairing. No other site data, and no WordPress credentials, are sent to Reepl.
Changelog
0.7.0
- Reepl can now send an article to your site as a draft, so you can review it in WordPress before publishing. A post that is already published is never turned back into a draft.
- Republishing from Reepl updates the same post.
0.6.3
- Separated article publishing and the public post feed into tabs. The publishing tab now leads with connection setup; the feed tab shows settings beside a live preview.
0.6.2
- Reorganized the WordPress settings page with a clearer connection status, publishing controls, feed settings, preview, and shortcode guidance.
0.6.1
- Article responses now report whether WordPress saved a draft or published a post, so Reepl can show the correct destination status.
0.6.0
- Removed the manual webhook subscription option. Connecting the site to Reepl is now the only way to turn on article publishing.
- The Article Publishing settings section now shows whether the site is connected, instead of manual webhook setup steps.
- Connecting a site now prefills the Public Profile URL from the paired Reepl account, if one was not already set.
0.5.1
- Connection errors now say what actually went wrong. Hitting the one-per-minute connection limit, or a site Reepl could not reach back, previously both showed a misleading “could not reach Reepl” message.
0.5.0
- Renamed the plugin to Reepl. The plugin folder changed, so this installs alongside any earlier “Reepl Posts & Publishing” copy rather than upgrading it. Deactivate and delete the old one, then connect again.
- Settings are stored under a new key, so an earlier connection is not carried over.
0.4.0
- Added one-click connect to a Reepl account. No WordPress password is requested; the plugin generates its own scoped secret used only to sign incoming articles.
- Reepl articles now publish to this site automatically once connected, with no manual webhook setup required.
0.3.1
- Addressed WordPress.org review feedback by matching the
reepl-poststext domain. - Enqueued the admin preview JavaScript instead of printing a script block from the settings page.
- Made frontend Reepl attribution opt-in through the
show_branding="true"shortcode attribute. - Documented the Reepl API, webhook behavior, optional feed URL, Terms of Service, and Privacy Policy.
0.3.0
- Added signed inbound article publishing through the
article_publishedReepl webhook event. - Added idempotent native WordPress post creation/update with optional tags, excerpts, slugs, and featured images.
- Added publish-immediately or save-as-draft handling for incoming articles.
- Renamed the plugin to Reepl while preserving the existing
[reepl_posts]shortcode.
0.2.1
- Updated brand icon usage to consistently use the starburst logo.
- Added asset cache busting so updated logos/styles appear immediately after plugin updates.
- Improved text preview rendering with tighter spacing and “See more” affordance.
0.2.0
- Added Reepl public API mode (
/v1/public/user-postsand/v1/stats) with User ID. - Added profile header and post-level stats rendering.
- Added video media rendering support.
- Updated post layout to a LinkedIn-style card UI.
0.1.0
- Initial release.