Performance is product quality
Event discovery breaks down when calendars lag under real content. Dayo is designed around indexed queries, cache-aware views, and a small front-end footprint.
About Dayo
We built the WordPress events plugin we needed and could not find.
Dayo exists because event teams should not have to choose between powerful calendars, fast queries, accessible visitor experiences, and a developer experience that respects the people maintaining the site.
Fast calendarsBuilt for large event datasets, year views, and real editorial workflows.
7 viewsIncluded in the free plugin
Big dataDesigned for large event sets
SecureExtensively tested
No bloatFast by design
Why we built it
The market changed, but our requirements did not get simpler.
We came from a higher education background, where calendars are not brochure decoration. They are operational infrastructure. Teams need to publish thousands of events, expose year views, filter large datasets, and keep the public experience fast at peak moments.
At the same time, popular tools in the WordPress events space were bought by other companies, gained unnecessary bloat, and became harder to extend cleanly. Dayo is our answer: a focused events plugin built for performance, accessibility, and maintainable development.
What we wanted to avoid
- Heavy event plugins slowed down as datasets grew.
- Important views, especially year view, were missing or treated as an afterthought.
- Acquisitions changed products that teams had already built workflows around.
- Front-end payloads included more behaviour than event visitors needed.
- Developer extension points were often inconsistent, under-documented, or difficult to test.
Our mission
Make WordPress event publishing fast, accessible, and calm to maintain.
Dayo is deliberately opinionated: enter event data once, reuse it everywhere, and render it in views that match how visitors and organisers actually think.
Accessibility is a default
Calendars, search controls, and event detail pages must work for everyone. Dayo prioritises semantic markup, visible focus states, contrast, and keyboard-first interaction.
Developers deserve a clear surface
A plugin should not punish teams for extending it. Dayo keeps APIs typed, templates predictable, and integration points intentional.
Higher education roots
Built around the hard calendar problems universities face every day.
Higher education calendars are complex: open days, lectures, public events, departmental sessions, research seminars, multi-day programmes, recurring series, and organiser-owned events all compete for attention.
A calendar plugin has to stay fast when the dataset is large and the filters are specific. It must also support year-level planning because academic and public engagement teams think beyond the next week.
- Large archivesQuery thousands of current and past events without turning every page into a bottleneck.
- Year planningShow long-range event density and seasonal programming at a glance.
- Reusable dataManage venues, speakers, organisers, sponsors, and event series without duplicate entry.
Who it is for
Dayo is for teams that treat events as important content infrastructure.
Higher education teams
For universities, colleges, faculties, departments, and public engagement teams managing thousands of events across many organisers.
Agencies and developers
For teams who need a WordPress events foundation that is typed, maintainable, extensible, and pleasant to ship.
Public event programmes
For venues, communities, conferences, and organisations that need fast discovery, flexible calendar views, postcode search, and reusable event data.
The result