rstake

sdaweb

SDAweb Calendar Sync turns any Google Calendar into a polished, on-brand events display on your WordPress site — without duplicate data entry. Keep scheduling in Google Calendar the way you already do; the plugin pulls those events in and keeps your site in sync automatically.
It’s for anyone who already runs their events in Google Calendar and wants them to look like a native part of their site instead of an embedded iframe — businesses, teams, venues, clubs, communities, and organisations of every kind.
Insert a calendar with a Gutenberg block, a shortcode, or a classic widget. All three share one render pipeline, so the output is identical however you add it.
<h4>Six ways to show your calendar</h4>
<ul>
<li>List / Agenda — chronological, optionally grouped by day, week, or month</li>
<li>Month grid — classic 7×6 calendar with multi-day event ribbons spanning across cells, today highlight (cell or whole-column style), optional ISO 8601 week-number column, and per-feed pastel chips</li>
<li>Card grid — upcoming events as styled cards, responsive</li>
<li>Week — 7 day columns, today highlighted</li>
<li>Day — single-day agenda</li>
<li>Mini-month — compact dot-density grid for sidebars and widgets, with a tap-to-expand event panel showing today + next upcoming events and a “Load more” button</li>
</ul>
Switch between views with one setting, or expose a visitor-facing view-toggle pill so visitors can switch themselves. Under the hood every view shares the same data layer, the same CSS-variable system, and the same accessibility baseline.
<h4>Smart UX out of the box</h4>
<ul>
<li>Hover popover on event chips (Month, Week, Mini) — a floating card with date, time, location, calendar, recurrence summary, and a click-through link, so visitors get the full event detail without leaving the page. Desktop hover + keyboard focus only; touch users keep direct click-through.</li>
<li>Mobile auto-degrade Month → Mini — below ~600px the full grid is replaced by the compact Mini-month view, so phone visitors get a clean, tappable calendar with no extra work from you. One wrapper, two layouts, no JS swap.</li>
<li>ICS subscribe dropdown — one tap to add your events to a visitor’s own calendar: Google Calendar (web), Apple Calendar / Outlook (webcal), Android Google Calendar app (intent), and Copy-link with toast confirmation. Mobile becomes a bottom sheet.</li>
<li>Live search + jump-to-date picker — optional chrome controls so visitors can filter or navigate quickly.</li>
<li>Multi-day event ribbons — week-spanning bars with arrow indicators when an event continues beyond the visible row.</li>
<li>Recurring event indicator — small ↻ icon with a plain-language cadence summary in the tooltip (“Repeats weekly until 31 December 2026”).</li>
<li>Per-display locale override — render a calendar in a specific language (e.g. nb_NO) even when the site language differs, so you can run a localized calendar on a site that’s in another language.</li>
</ul>
<h4>Two authentication paths</h4>
<ul>
<li>API key — for calendars marked “Make available to public” in Google Calendar. One field, paste, done.</li>
<li>Service Account JSON — for private calendars without per-user OAuth. Upload the JSON, share the calendar with the service-account email, you’re set.</li>
</ul>
Credentials are encrypted at rest using a key derived from your site’s authentication salt. They are never echoed back into the admin UI — only the masked value and (for service accounts) the public service-account email are shown.
<h4>Theme-aware out of the box</h4>
The plugin reads your active theme’s <code>theme.json</code> color palette and uses your <code>primary</code>, <code>accent</code>, <code>foreground</code>, and <code>background</code> colors automatically. Per-display overrides let you set custom primary, accent, today-highlight, and link colors and force light/dark mode without touching code. Every design token is exposed as a CSS custom property so a developer can fully restyle the calendar from their theme stylesheet.
<h4>Five built-in theme presets</h4>
One-click coordinated colour bundles: Default (clean blue), Warm earth (cream + deep red), High contrast (solid black on white for AAA-stricter sites), Forest (deep green), Sunset (warm coral + amber).
<h4>Accessibility built in</h4>
WCAG 2.2 AA baseline with several AAA touches:
<ul>
<li>Live contrast warnings on every colour picker — the admin UI shows the WCAG ratio against both light and dark surfaces with pass/fail markers as you choose colours</li>
<li>Automatic high-contrast overlay via <code>prefers-contrast: more</code></li>
<li>Focus-visible halo: a 4px white ring behind the primary outline so focus stays visible against any chip background</li>
<li><code>prefers-reduced-motion</code> honored everywhere</li>
<li>ARIA roles and labels on the month grid, navigation, popovers, and view-toggle</li>
<li>Semantic HTML throughout</li>
<li>RTL-aware via CSS logical properties</li>
<li>Tabular numerals for day numbers and time labels so single- and double-digit values don’t drift</li>
</ul>
<h4>Built for the WordPress.org standard</h4>
<ul>
<li>Block editor first-class — server-side rendered, ServerSideRender preview, all the standard <code>InspectorControls</code></li>
<li>Shortcode and classic widget on the same render pipeline</li>
<li>No bundled core libraries (no jQuery on front-end, no Guzzle, no Carbon, no Monolog)</li>
<li>No third-party authentication relay — your credentials only ever talk directly to googleapis.com</li>
<li>Translation ready via translate.wordpress.org once the plugin is published and indexed (no bundled <code>.po</code>/<code>.mo</code> — WordPress auto-loads locale files into <code>wp-content/languages/plugins/</code> per the WP Plugin Handbook), plurals via <code>_n()</code>, JS strings via <code>wp_localize_script</code></li>
<li>Free and GPLv2</li>
</ul>
<h4>For developers</h4>
Extension hooks are documented in <code>docs/hooks.md</code> inside the plugin folder. The first-release set includes filters for event data, event URLs, query args, cache TTL, render output, palette resolution, plus actions for refresh and uninstall lifecycle.
<h3>Third-Party Services</h3>
This plugin connects to the Google Calendar API to retrieve events from calendars you configure.
<ul>
<li>Service: Google Calendar API v3</li>
<li>Website: https://developers.google.com/calendar</li>
<li>Terms of Service: https://developers.google.com/terms</li>
<li>Privacy Policy: https://policies.google.com/privacy</li>
</ul>
Data sent: the calendar ID(s) you configure, plus either your API key or a JSON Web Token signed with your service account credentials. Event data is returned to your server and cached locally as WordPress transients. No event data is sent to any third party.
The ICS subscribe feature, when enabled, links visitors directly to Google’s public iCal feed (<code>calendar.google.com/calendar/ical/.../public/basic.ics</code>) — the plugin does not proxy or store that data.

SDAweb Calendar Sync for Google Calendar

Display your Google Calendar events on your site in six views. Theme-aware, accessible, mobile-ready, no duplicate entry.

Vincent Dubroeucq

openagenda

Display calendars from https://openagenda.com on your site.
<h3>Basic usage</h3>
This WordPress plugin allows you to embed any calendar hosted on <a href="https://openagenda.com" rel="nofollow ugc">https://openagenda.com</a> on your WordPress site.
Upon activation, the plugin creates a new post type named Calendars. Just create a new calendar, provide the UID of the calendar you wish to display in the calendar settings box, and that’s it !
You can leave the content area for this calendar empty, as it will be populated automatically with your events !
Your events are automatically inserted after your content. If you wish to control where your events will be listed, just use the shortcode <code>[openagenda]</code> in your content.
<h3>Settings</h3>
General settings can be found under the Calendar > Settings entry in the admin menu.
All data related to your API key or calendars can be found on https://openagenda.com.
The settings are divided into two tabs: General and Integrations.
<h3>General settings</h3>
The General settings page provides the following settings :
<ul>
<li>OpenAgenda API key : Your user API key. Providing your account API key is required for the plugin to work properly. It can be found in your account on <a href="https://openagenda.com" rel="nofollow ugc">https://openagenda.com</a></li>
<li>Allow for embedded content : If your events contain embedded content, tick this box to allow the corresponding HTML tags.</li>
<li>Load default stylesheets : The plugin provides very basic styling and depends heavily on your theme’s styles. Disable this to rely 100% on your theme styles.</li>
<li>Legacy templates : Templates have been updated in 3.0.0. Check this option to continue using legacy templates.</li>
<li>Cache duration : For performance reasons, basic requests to OpenAgenda are temporarily kept in cache. This settings controls the time to keep them cached, in seconds.</li>
<li>Default event image : Choose an image to use in case events do not have one.</li>
<li>Delete all calendar content on uninstall ? : controls whether you want to delete all your calendars on uninstall.</li>
<li>Delete all options on uninstall ? : controls whether you want to delete all your calendar settings on uninstall.</li>
<li>Allow OpenAgenda to collect usage stats ? : controls whether you want to send CMS used and site URL to OpenAgenda, for statistic purposes.</li>
</ul>
<h3>Integrations settings</h3>
The Integrations tab allows you to fine tune settings for various third party services the plugin uses.
OpenStreetmap integration settings :
<ul>
<li>Default map tiles link : This is the map tile used for the various maps displayed by the plugin.</li>
<li>Default map tiles attribution link : this is the default attribution link placed on OpenStreetMaps.</li>
</ul>
CloudImage integration settings :
<ul>
<li>CloudImage API key : If you wish to use CloudImage to serve your images, enter your API key here.</li>
</ul>
<h3>Permalinks settings</h3>
In the Permalinks settings, you can change the prefix for your calendar pages. You cannot leave this blank as your URLs will conflict with WordPress’ default pages and posts.
In the Settings > Reading section, you can set a calendar page as your front page. Note that it will still use the default calendar template provided by the plugin and the default front page template provided by your theme.
<h3>Customizer settings</h3>
In the Customizer, a new panel is available to house various display settings. For now only a main color setting is available.

If you add Openagenda Filter widgets via the customizer, the preview will not display them immediately. That’s simply because filters are initialized on page load and the customizer preview is not always fully refreshed when a setting is changed.
Simply publish your settings and refresh the page, or open your agenda page in another tab. Your filter should work just fine.
<h3>Filter widget and shortcodes</h3>
To allow users to easily find relevant events, the plugin also provides a convenient filter widget. Place the widget in your sidebar or other widgetized area, pick a filter and tweak any additional settings in the widgets admin.
To integrate filters directly in your content instead of widget areas, the plugin also provide shortcodes.
Every shortcode listed here (except for <code>[openagenda]</code>) corresponds to a filter option in the widget.
Additionaly, shortcodes and widget filters have the same parameters, and every shortcode attribute corresponds to a widget filter setting.
<code>[openagenda]</code>
Displays the calendar. You do not need to use this shortcode explicitely, as it is automatically injected in the content of your “calendars” posts.
However, if you need to insert static content after your list of events, you can do so by inserting this shortcode, then your static content afterwards.
<code>[openagenda_filter_active]</code>
Displays the active filters. It takes no parameters.
<code>[openagenda_filter_choice]</code>
Displays a list of choices, depending on the field chosen. It takes the following parameters :
<ul>
<li><code>field</code>: the slug of the choice field you want to display (e.g. “cities”, “keywords”, “departments”, “favorites”, etc… ).</li>
<li><code>additional_field</code>: Any custom field you have setup in your OpenAgenda administration. Only works when ‘Additional Field’ is the chosen field.</li>
<li><code>page_size</code>: Number of options to display before the ‘More options’ button.</li>
</ul>
You can find the list of available additional fields in the Forms section of your agenda settings on openagenda.com (ex: https://openagenda.com/[your-agenda]/admin/schema)
<code>[openagenda_filter_calendar]</code>
Displays a calendar. It takes no parameters.
<code>[openagenda_filter_map]</code>
Displays an interactive map to locate and search events. It takes the following parameters :
<ul>
<li><code>map_tiles_link</code> : Map tiles link to use. Defaults to <code>https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png</code></li>
<li><code>map_auto</code> : Whether to automatically update map on scroll. </li>
</ul>
<code>[openagenda_preview]</code>
Displays a preview of any calendar. It takes the following parameters :
<ul>
<li><code>uid</code> : UID of the calendar you wish to preview.</li>
<li><code>size</code> : Number of events to display.</li>
<li><code>sort</code> : Event sort option. Accepts <code>lastTimingWithFeatured.asc</code>, <code>timingsWithFeatured.asc</code>, <code>lastTiming.asc</code>, <code>timings.asc</code>, <code>updatedAt.asc</code> or <code>updatedAt.desc</code>.</li>
<li><code>filters</code> : Query string representing filters to apply to the request. To ensure it works properly and avoid breaking the shortcode, you should urlencode the query string. You can do so via a simple tool like <a href="https://www.urlencoder.org/fr/" rel="nofollow ugc">https://www.urlencoder.org/fr/</a></li>
<li><code>links</code> : Accepts <code>oa</code> or an empty string. If set to <code>oa</code>, event links will point to events pages on https//openagenda.com instead of local pages.</li>
</ul>
<code>[openagenda_filter_relative]</code>
Allows to filters past or upcoming events. It takes no parameters.
<code>[openagenda_filter_search]</code>
Displays a search field. It takes the following parameters :
<ul>
<li><code>placeholder</code> : text field placeholder.</li>
</ul>
<h3>Customization</h3>
Templates for the list of events and individual events can be customized in your child theme.
If you’re not already using a child theme, it is recommended to create one.
<a href="https://developer.wordpress.org/themes/advanced-topics/child-themes/" rel="nofollow ugc">https://developer.wordpress.org/themes/advanced-topics/child-themes/</a>
Just create a folder named <code>openagenda/</code> in your child theme, then copy and paste the template you wish to override from the plugin’s <code>templates/</code> folder.
Here is a list of templates you can find in the plugin’s <code>templates/</code> folder :
<ul>
<li><code>event-loop.php</code> : main wrapper for list view and single event view. Displays exports button and pagination at the top and bottom. </li>
<li><code>list-header.php</code> : contains the total number of events and active filters display.</li>
<li><code>event.php</code> : template used to display the event information on list views.</li>
<li><code>single-event.php</code> : template used to display the event information on single event views.</li>
<li><code>event-location.php</code> : template used to display the location information on single event views.</li>
<li><code>event-additional-fields.php</code> : template used to the list of additional fields on single event views.</li>
<li><code>preview-loop.php</code> : main wrapper for the preview widget and shortcode.</li>
</ul>
The <code>legacy/</code> folder contains templates used prior to version 3.0.0. If you updated the plugin and notice issues on your frontend, that’s probably because your site used legacy templates. Please try and check the Use legacy templates checkbox in the settings page.
The plugin provide convenient template tags for you to display event data in the <code>inc/template-tags.php</code> file. Feel free to define your own in your theme.
The plugin also provides many hooks to allow you to customize the html output or other various data.
<h3>Usage of third party services and copyright information</h3>
This plugin displays data hosted and provided by <a href="https://openagenda.com" rel="nofollow ugc">https://openagenda.com</a>. By using this plugin, you accept and agree with OpenAgenda’s <a href="https://openagenda.zendesk.com/hc/fr/articles/201753991" rel="nofollow ugc">terms and conditions</a> and <a href="https://openagenda.zendesk.com/hc/fr/articles/360003182014" rel="nofollow ugc">privacy policy</a>. Please make sure to read them before using this plugin. Also, using this plugin DOES require an account at <a href="https://openagenda.com" rel="nofollow ugc">https://openagenda.com</a>, and an API key.
By default, maps displayed by this plugin use data from <a href="https://openstreetmap.org/" rel="nofollow ugc">https://openstreetmap.org/</a> and uses the <a href="https://leafletjs.com/" rel="nofollow ugc">leaflet JS library</a>. By using this plugin, you accept and agree with OpenStreetMap’s <a href="https://wiki.osmfoundation.org/wiki/Terms_of_Use" rel="nofollow ugc">terms of use</a>, <a href="https://wiki.openstreetmap.org/wiki/Acceptable_Use_Policy" rel="nofollow ugc">acceptable use policy</a> and <a href="https://wiki.osmfoundation.org/wiki/Privacy_Policy" rel="nofollow ugc">privacy policy</a>
The plugin provides optional integration with CloudImage. The integration requires to create an account at <a href="https://cloudimage.io" rel="nofollow ugc">https://cloudimage.io</a> and accept and agree their <a href="https://assets.scaleflex.com/Sales/Legal/Scaleflex+Services+Terms+and+Conditions+%5BFR%5D.pdf" rel="nofollow ugc">terms of use</a>.
Icons used in the UI are <a href="https://genericons.com/" rel="nofollow ugc">Genericons</a>, licenced under the GPL 2.0.

OpenAgenda

I find this plugin quite neat indeed. Any wordpress user can easily add dedicated agenda pages powered by the OpenAgenda platform.

Little disclosure: I work for OpenAgenda.

Simple OpenAgenda integration

Display calendars from https://openagenda.com on your site.

SDAweb Calendar Sync for Google Calendar vs OpenAgenda