Description
ORGRIN plans, writes and publishes the articles of your site: it studies what your customers search for, writes each article in your brand’s voice, reviews it with an editor and delivers it here, with its cover image and tags. This plugin is the bridge: it receives each approved article and publishes it on this WordPress.
- Connect in one click. Click “Connect with ORGRIN”, confirm in the ORGRIN portal and come back connected: no key to copy, no WordPress password shared.
- Signed deliveries only. Every delivery is signed with a secret only this site and ORGRIN know, checked against replays and refused if anything is off.
- Your site, your choices. Choose the author and the category of the articles; posts you edit stay yours.
- Know it works. The ORGRIN screen shows the last article received and the recent activity; Site Health checks the connection, the server clock and whether a firewall is in the way.
- Light. Nothing is loaded on your public pages and nothing is kept about your visitors. The secrets are stored encrypted.
- In your language. English, Portuguese, Spanish, French and German, every regional variant.
An ORGRIN account is required: https://orgrin.com
The ORGRIN screen uses the Fraunces typeface (Copyright 2018 The Fraunces Project Authors, SIL Open Font License 1.1, included in assets/fonts): it ships with the plugin, so the dashboard never loads fonts from another service.
External services
This plugin connects to ORGRIN (https://orgrin.com), the service that writes the articles, at the API address https://api.orgrin.com. It is needed to receive the articles; nothing is sent before you click Connect, and every call to ORGRIN follows an administrator’s action.
- When you click “Connect with ORGRIN”, your browser opens the ORGRIN portal (https://portal.orgrin.com) with the address of this site’s REST API (for example https://example.com/wp-json/orgrin/v1/), the address of this ORGRIN screen and a one-time challenge; after you confirm there, the plugin sends the one-time code it received back, with the matching secret, to ORGRIN, which answers with a site key and a delivery secret, kept in this WordPress and never shown.
- The plugin sends to ORGRIN the site key, the address of this site’s REST API and the plugin version at these moments, and only then: when you connect (or connect with a pasted site key), click Refresh status, click Send a test delivery, or Disconnect; while the ORGRIN screen follows a confirmation (every few seconds, for two minutes at most); when you open Tools > Site Health (never in WordPress’s weekly automatic check); when you deactivate the plugin; a few seconds after you activate it again (and, if ORGRIN cannot be reached, again after 5 minutes and after 1 hour), or when an administrator opens the dashboard while the reactivation is not yet confirmed or a confirmation has been waiting for more than a minute (each at most once every 10 minutes); and when you remove the plugin.
- Site Health also calls this site’s own route /wp-json/orgrin/v1/ping once, unsigned, to check that no security plugin or firewall blocks it.
- After connecting, ORGRIN calls this site’s routes /wp-json/orgrin/v1/ping (to confirm the connection) and /wp-json/orgrin/v1/posts (to deliver each approved article: title, text, excerpt, address, tags and cover image). The plugin accepts only deliveries signed with the delivery secret.
- To set the cover image, the plugin downloads the image from the address ORGRIN sends with the article, served by https://images.orgrin.com.
- Like every WordPress request, the calls to ORGRIN carry this site’s address in the User-Agent header.
ORGRIN terms of use: https://orgrin.com/terms
ORGRIN privacy policy: https://orgrin.com/privacy
Installation
- In WordPress, go to Plugins > Add New Plugin, search for “ORGRIN”, click Install Now and then Activate. Or upload the .zip file in Plugins > Add New Plugin > Upload Plugin.
- Open the ORGRIN menu and click “Connect with ORGRIN”. Confirm in the ORGRIN portal; you come back connected. (Or paste a site key under “I prefer to paste a key”.)
If a security plugin or firewall is active, allow the REST API path “orgrin/v1”.
FAQ
The connection fails or articles do not arrive. What should I check?
Open Tools > Site Health: ORGRIN checks the connection, the server clock and the route ORGRIN calls. Security plugins and firewalls (Wordfence, Cloudflare, your host’s firewall) must allow the REST API path “/wp-json/orgrin/v1/”. Cache plugins must not cache it. The ORGRIN screen keeps the recent activity, ready to copy to ORGRIN support.
Does ORGRIN get my WordPress password?
No. ORGRIN never logs into your WordPress. It delivers each article to this plugin, signed, and the plugin publishes it.
What happens if I deactivate or uninstall the plugin?
Deactivating pauses the deliveries: ORGRIN is told and waits; activating again checks the connection on its own. Uninstalling disconnects the site from ORGRIN, which revokes its key, and removes everything the plugin kept (on every site of a network). The posts already published stay on your site.
What data does the plugin collect?
None about your visitors. It keeps only the connection to ORGRIN (the site key and the delivery secret, encrypted) and the recent activity of the connection. It calls ORGRIN only after an administrator’s action, at the moments listed under External services. A paragraph for your privacy policy is offered in Settings > Privacy.
Screenshots
Changelog
1.0.0
- The first public version on WordPress.org.
- The ORGRIN brand on its screen: the wordmark and the Fraunces typeface, bundled with the plugin.
- Works from PHP 7.4 and WordPress 6.0 (tested up to WordPress 7.1 and PHP 8.4, single site and network).
- The connection is confirmed in two steps: ORGRIN answers at once and the screen follows until it is connected, so hosts with a single PHP worker connect too.
- The cover image never holds a delivery: 10 seconds at most, then up to two more attempts in the background.
- A new ORGRIN screen: the connection status with the last article received and the last check, Open ORGRIN, Send a test delivery, the author and the category of the articles, and the recent activity ready to copy to ORGRIN support (never with keys or secrets).
- Site Health checks the connection, the server clock and whether a security plugin or firewall blocks the ORGRIN route; a notice in the dashboard when ORGRIN cannot deliver.
- A Settings link on the Plugins screen and the ORGRIN mark in the menu.
- Translations through WordPress (text domain “orgrin”): Portuguese, Spanish, French and German ship with the plugin, for every regional variant, and the plugin can be translated on translate.wordpress.org.
- Deactivating tells ORGRIN to pause the deliveries; activating again checks the connection on its own.
- Uninstalling disconnects from ORGRIN and removes everything the plugin kept, on every site of a network.
- A paragraph for the site’s privacy policy in Settings > Privacy.
- The site key and the delivery secret are stored encrypted, with a key derived from this site’s own salts in wp-config.php.
- The connection is saved in one option, never half written; the options of 0.4 are migrated automatically.
- The ORGRIN addresses are fixed (constants ORGRIN_API_BASE_URL and ORGRIN_PORTAL_URL, https only, for development).
- Disconnect removes the site key too, and ORGRIN revokes it; the screen says when ORGRIN could not confirm.
- A refused delivery tells nothing to a caller that did not sign it; a wrong server clock has its own message.
- No “check, then write” left: the activity log, the refusal limit, the one-click return, the article lock and the background cover all use single-statement claims or locks with an owner; refusals never push the articles out of the recent activity.
- A wrong pasted key never replaces the key that works; it is stored only after ORGRIN accepts it.
- Send a test delivery shows the result of that test; the screen follows a confirmation for two minutes at most.
- Activating again retries when ORGRIN cannot be reached, and opening the dashboard confirms it even without WP-Cron; the dashboard notice can be hidden.
- The background cover never replaces a cover set by hand; an article in the trash is never created again.
- Site Health checks are asynchronous and never run in WordPress’s weekly automatic check.
- Uninstalling also clears the object cache (Redis, Memcached): a new installation starts disconnected.
- Language packs from translate.wordpress.org load for the languages the plugin does not ship.
0.4.1
- A delivery id is claimed in a single database statement: simultaneous copies of one delivery can no longer both pass.
- One delivery of an article at a time, so simultaneous deliveries never create two posts.
- A return from the ORGRIN portal that this user did not start changes nothing.
- One nonce per action on the ORGRIN screen.
- External services: the image host is named.
0.4.0
- Connect with ORGRIN in one click: confirm in the ORGRIN portal, no key to copy.
- Pasting a site key moved to “I prefer to paste a key”.
0.3.1
- Ready for the plugin directory: Plugin Check issues resolved.
- External services described in this readme; output escaping on the status icon.
0.3.0
- Connect, confirm and disconnect with a signed test delivery.
- Receives the articles from ORGRIN, with cover and tags.
- Five languages.


