Before diving into any changes to how the calendar is defined and maintained, I think it is vital to establish what is wanted from the calendar, both from the maintenance point of view and the user PoV.
The existing calendar allows views by week, month and agenda (serial). One can move back and forth in the listings easily, and they can be downloaded and printed. Individual entries can be copied to one's personal calendar. Selecting an entry shows more information, with links to further details. There are probably more functions I have not considered. Are all these needed? On Fri, 19 Apr 2024 at 15:08, Bertrand Delacretaz <bdelacre...@apache.org> wrote: > > On Fri, Apr 19, 2024 at 2:13 PM Rich Bowen <rbo...@rcbowen.com> wrote: > > ...I would *really* like to not have to edit ics files directly. That way > > lies madness... > > Indeed. If someone wants to take a look, Hugo (which is used for both > the comdev and events websites) does support the generation of iCal > files directly from markdown files representing events. > > https://github.com/raoulb/hugo-ical-templates-demo looks like a good > example of that, except that it's using a complicated date format in > the Markdown event files. But that can certainly be fixed. > > -Bertrand (really in "someone should" mode here, won't probably have > time to help right now) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
