feat: add dedicated community meeting pages

[charantejguniganti]

Concisely describe the change

This change replaces the community meeting modal with dedicated pages for meeting notes.

It adds:

• A /community/meetings page containing the meeting archive
• Individual /community/meetings/YYYY-MM-DD pages
• Filtering between Community Meetings and Community Cabal meetings
• Direct links to meeting recordings
• Static generation of meeting pages and their Markdown content
• Handling for older meeting-note formats

The existing /community page now links to individual meeting pages instead of displaying the meeting notes in a modal.

Before screenshot / screen recording

Previously, meeting notes were displayed through a modal on the /community page. Individual meetings did not have dedicated shareable URLs.

After screenshot / screen recording

The new implementation provides:

• /community/meetings — meeting archive with Community/Cabal filtering
• /community/meetings/2026-08-04 — current meeting notes with a dedicated URL
• /community/meetings/2020-10-06 — historical meeting notes using an older format

Checklist

• I certify I wrote the patch or otherwise have the right to pass it on as an open-source patch.
• I referenced the relevant issue/discussion where applicable.
• The PR description, commit message, and GitHub comments are written in my own words, in accordance with the repository's LLM policy.

Testing

• yarn build passes.
• Meeting parser tests pass.
• Verified the meeting archive page.
• Verified current meeting pages.
• Verified historical meeting pages.
• Verified meeting Markdown is included in the generated static HTML.
• Verified the legacy meeting modal is removed.

[charantejguniganti]

Hi @TomSweeneyRedHat, this is my first PR to the Podman repository.

I spent some time researching the existing community meeting implementation, historical meeting-note formats, and Docusaurus's plugin/static-generation approach before implementing this change. I tested it against both current and historical meeting formats, verified the generated static HTML, and ran the build and parser tests locally.

I noticed the required workflow is currently awaiting maintainer approval. When convenient, could you or another maintainer take a look? I'm happy to make any changes based on your feedback.

Thank you!

[Prat260104]

Hey @charantejguniganti,

This is part of the upcoming LFX Mentorship Program for the Fall term.

It would be advisable not to work on this for now, or at least to avoid reducing the scope of the project, as it is intended for the upcoming mentee. You can go through the guidelines and proposal to get an idea of what the project is about and what it includes.