== Description ==

An event at 19:00 in Berlin is a different instant for every reader, and most event plugins store a naive datetime and hope. Lantern stores an instant and a venue timezone, displays the venue’s local time by default, and offers the reader theirs — labelled, so nobody has to guess which they are looking at.

Recurring events are generated occurrences, each editable individually. Editing one occurrence does not detach the series, and editing the series does not silently overwrite the one you changed.

Event structured data comes from the same fields as the display, including the timezone, so a calendar aggregator and a human see the same time.

== Screenshots ==

Numbered the way they ship in /assets/. Click any one to see it full width.

== Installation ==

Install and activate the theme.
Create a venue, with its timezone. The theme will not let you skip it.
Create events at that venue. Recurrence is a field on the event.

Past events keep their URLs. An archive that deletes what already happened is a broken link generator.

== Frequently asked questions ==

Online events?

A venue with no address and a timezone of your choosing, usually the organiser’s.

Does it export to calendar apps?

Every event has an .ics link generated from the stored instant, so it lands correctly wherever it is imported.

Tickets?

A link to wherever you sell them. Ticketing is not a theme’s job.

== Changelog ==

= 2.5.0 = March 6, 2026

Reader-local time display, labelled, alongside venue time.
ics export uses the stored instant rather than the formatted string.

= 2.4.0 = October 17, 2025

Editing a single occurrence no longer detaches it from its series.

= 2.0.0 = March 25, 2025

Events store an instant plus a venue timezone. Naive datetimes from 1.x are migrated with a report of any that were ambiguous.