bitcircus101 is a tech and creative space located in Bonn, Germany.

This repository contains the website for bitcircus101.

index.html                  Main landing page
events.html                 Events page (loads events-data.json)
donations.html              Donation / funding page (loads funding.json)
raum-nutzen.html            Room usage info
impressum-datenschutz.html  Legal / privacy
dankedankedanke.html        Thank you page
style.css                   Global styles (terminal theme, dark bg, green accent)

events.js                   Frontend: fetches events-data.json, renders event cards, tag filtering
calendars.json              Calendar source definitions (ICS URLs, names, flags)
funding.json                Current funding percentage (generated by CI)

scripts/
  sync-events.mjs           Fetches ICS from Nextcloud, generates events-data.json + feed.xml

tests/
  site.spec.js              Playwright end-to-end tests (204 tests × 3 browsers)
  sync-events.spec.mjs      Unit tests for ICS parser and RRULE expansion (22 tests)
playwright.config.js        Playwright config (Chromium, Firefox, Mobile Chrome)

.github/workflows/
  deploy.yml                Test on main → deploy to live
  sync-events.yml           Calendar sync (every 15 min)
  update-funding.yml        Funding level update (manual)
  sitemap.yml               Sitemap generation (on push to live)

These files are created by CI actions and committed to the live branch only:

main (push) → Unit tests → Sync script → Playwright E2E → Deploy to live

Every push to main triggers:

1. Unit tests: ICS parser, RRULE expansion, date parsing (node:test, 22 tests)
2. Sync script: Generates events-data.json for E2E tests to use
3. E2E tests: Playwright across 3 browsers (204 tests)
4. Deploy (only if all tests pass): Syncs site files from main to live

Nothing reaches production without passing all tests first.

• Trigger: Cron every 30 minutes + manual
• Branch: Checks out live, pulls scripts/config from main
• What it does:
  1. Runs scripts/sync-events.mjs (Node 22, zero dependencies)
  2. Fetches ICS feeds from all calendars defined in calendars.json
  3. Parses VEVENT entries, expands RRULE recurrences (weekly, monthly with BYDAY/BYSETPOS)
  4. Filters out internal/blocker events and past events
  5. Generates events-data.json with lastSync timestamp (max 40 cards, 120-day horizon)
  6. Generates feed.xml (RSS 2.0, primary calendar only, max 15 items)
  7. Commits and pushes to live with retry logic

• Trigger: Manual (workflow_dispatch) with percent input (0-100)
• Branch: live
• What it does: Writes funding.json with the given percentage, commits to live

• Trigger: On push to live + manual
• Branch: live
• What it does:
  1. Uses cicirello/generate-sitemap to scan all HTML files
  2. Strips Google verification files from the sitemap
  3. Commits sitemap.xml to live

To add a new calendar, add an entry to calendars.json — no code changes needed.

Tags are resolved in priority order:

1. Explicit #hashtags in the Nextcloud event description (e.g. #workshop #hardware)
2. ICS CATEGORIES field (set in Nextcloud calendar UI)
3. Keyword auto-detection from title + description (fallback)

If no tags match, the event gets #community as default.

• Events with "blocker" or "interne veranstaltung" in the title are excluded
• Only future events are shown (up to 120 days ahead)
• Max 30 events per calendar, 40 total

• Loads events-data.json, falls back to live ICS fetch if JSON unavailable
• Renders event cards grouped by month
• Dynamic tag filter bar (OR logic: any matching tag shows event)
• Source badge for non-primary calendar events
• Permalink anchors with smooth scroll

Static site — open HTML files directly or use any local server:

python3 -m http.server 8080

npm install
npm test                   # all tests (unit + E2E headless)
npm run test:unit          # only unit tests (ICS parser, fast)
npm run test:e2e           # only Playwright E2E
npm run test:headed        # E2E with browser window
npm run test:ui            # Playwright UI mode

Unit tests (tests/sync-events.spec.mjs — 22 tests, ~100ms):

E2E tests (tests/site.spec.js — 68 tests × 3 browsers = 204):

Browsers: Chromium, Firefox, Mobile Chrome (Pixel 5).

node scripts/sync-events.mjs

This fetches live ICS data and writes events-data.json + feed.xml to the project root.