Social Crew

SocialCrew Widgets loads the official SocialCrew widget runtime from <code>widgets-api.socialcrew.io</code> when a page contains a widget shortcode or the SocialCrew block.
<ul>
<li>Shortcode <code>[socialcrew_widget]</code> with catalog parameters (type, team, league) or a direct <code>space</code> id.</li>
<li>Shortcode <code>[socialcrew_widget_saved]</code> for presets you save under Settings → SocialCrew Widgets.</li>
<li>Gutenberg block SocialCrew Widget to pick a saved preset.</li>
<li>Settings screen with a shortcode builder, preview in a new window, and saved widget management.</li>
</ul>
The plugin loads the space catalog from the SocialCrew widgets API (<code>GET /plugin/v1/space-catalog</code>) on the server. No setup is required after install—the production API URL and read-only credentials are built into the plugin. The catalog is cached briefly in WordPress transients.
<h3>External services</h3>
This plugin relies on SocialCrew’s hosted widget loader to render widgets in the visitor’s browser.
What the service is: The endpoint <code>https://widgets-api.socialcrew.io/load</code> serves the JavaScript module that powers the widget UI (tables, fixtures, polls, etc.) when your site outputs the plugin shortcode or block.
What data is sent and when: On each page view where a widget is embedded (or when you use the admin preview), the visitor’s browser requests that URL. Typical query parameters are <code>space</code> (the widget identifier), <code>adaptive=true</code>, and optional <code>showHeader</code>. The plugin does not intentionally send WordPress user credentials or private admin data to SocialCrew—only the public widget parameters needed to render the embed.
Documentation (widgets product): <a href="https://widgets.socialcrew.io/" rel="nofollow ugc">SocialCrew Widgets</a>
Terms of Use: <a href="https://widgets.socialcrew.io/termos-de-uso" rel="nofollow ugc">https://widgets.socialcrew.io/termos-de-uso</a>
Privacy policy: <a href="https://widgets.socialcrew.io/politica-de-privacidade" rel="nofollow ugc">https://widgets.socialcrew.io/politica-de-privacidade</a>
<h3>Privacy</h3>
When a visitor loads a page that embeds a SocialCrew widget, the browser requests a JavaScript module from widgets-api.socialcrew.io. Query parameters may include the widget <code>space</code> id, <code>adaptive=true</code>, and optional <code>showHeader</code>.
On the server, the plugin may call api-v1.widgets.solutions to refresh the read-only space catalog (type/team/league to space id). That request uses credentials embedded in the plugin package; visitors never see those credentials.
The plugin does not send your WordPress user data to SocialCrew by default. Site administrators configure widgets in wp-admin; only public widget parameters are used in the front-end script URL.
For questions about data processed by SocialCrew’s servers, refer to the External services section above, the privacy policy at <a href="https://widgets.socialcrew.io/politica-de-privacidade" rel="nofollow ugc">widgets.socialcrew.io/politica-de-privacidade</a>, and the terms at <a href="https://widgets.socialcrew.io/termos-de-uso" rel="nofollow ugc">widgets.socialcrew.io/termos-de-uso</a>.

SocialCrew Widgets

Embed SocialCrew widgets in WordPress using shortcodes or a Gutenberg block, without pasting script snippets by hand.

Automattic

John James Jacoby

Gary Jones

Mohammad Jangda

Philip John

Nikolay Bachiyski

Your readers want your updates as quickly as possible, and we think we provide the easiest and most flexible publishing environment to make that happen. Sometimes though, that’s just not enough.
When you’re covering a fast-paced event — the latest Apple unveiling, an F1 Grand Prix or the Super Bowl — a full blog post for each individual update is a poor experience for your authors and your audience.
The <a href="https://wpvip.com/" rel="nofollow ugc">WordPress.com VIP Liveblog Add-On</a> was purpose-built to address these issues.
Here’s what makes it special:
<ul>
<li>Post updates right from the front end of your site (no need to use the <code>/wp-admin</code> dashboard).</li>
<li>Viewers of your liveblog get new entries served to them instantly and automatically, without needing to refresh.</li>
<li>Authors can drag and drop photos straight into the liveblog area, without separate browser tabs or windows.</li>
<li>No need for a separate site dedicated to liveblogging — every post can be a liveblog, even existing ones.</li>
</ul>
If you’d like to check out the code and contribute, <a href="https://github.com/Automattic/liveblog" rel="nofollow ugc">join us on GitHub</a> — pull requests are more than welcome.
<h3>Documentation</h3>
Developer and end-user documentation lives in the <a href="https://github.com/Automattic/liveblog/tree/develop/docs" rel="nofollow ugc"><code>docs/</code></a> directory:
<ul>
<li><a href="https://github.com/Automattic/liveblog/blob/develop/docs/end-user-guide.md" rel="nofollow ugc">End user guide</a> — for editors and site administrators.</li>
<li><a href="https://github.com/Automattic/liveblog/blob/develop/docs/customization.md" rel="nofollow ugc">Customization</a> — entry features, key events, hashtags, commands, emoji, shortcodes, template overrides.</li>
<li><a href="https://github.com/Automattic/liveblog/blob/develop/docs/admin-meta-box.md" rel="nofollow ugc">Extending the admin meta box</a></li>
<li><a href="https://github.com/Automattic/liveblog/blob/develop/docs/entry-hooks.md" rel="nofollow ugc">Hooking into entries</a></li>
<li><a href="https://github.com/Automattic/liveblog/blob/develop/docs/auto-archive.md" rel="nofollow ugc">Auto-archiving</a></li>
<li><a href="https://github.com/Automattic/liveblog/blob/develop/docs/websockets.md" rel="nofollow ugc">WebSocket support</a></li>
</ul>
<h3>Contributing</h3>
See <a href="https://github.com/Automattic/liveblog/blob/develop/CONTRIBUTING.md" rel="nofollow ugc">CONTRIBUTING.md</a> for how to set up the development environment and submit changes.

Liveblog

Empowers website owners to provide rich and engaging live event coverage to a large, distributed audience.

SocialCrew Widgets vs Liveblog