Jon Udell judell

Event Rewriting for WFHB

WFHB needs to edit certain events as they flow from the community-calendar database to the iframed viewer. The approach: add an eventOverrides object to the existing excluded.json file that WFHB already manages in GitHub. The community-calendar viewer already fetches this file via the ?exclude= query param; it just needs to apply overrides in addition to exclusions.

Two repos are involved:

community-calendar (Jon) — the shared viewer that any city can iframe
wfhb (Chuck) — the WFHB-specific moderator UI

Part 1: community-calendar viewer (Jon)

The published blog at blog.xmlui.org is a standalone XMLUI app (xmlui-blog), separate from the main website. Its source lived in blog/src/ but has been removed from the working tree — only blog/dist/ remains.

The key file was blog/src/config.ts, which contains:

A hardcoded blogPosts array listing every post's metadata (title, slug, description, author, date, image, tags, draft).
That array is passed to the XMLUI runtime via appGlobals.blog.posts.
Blog markdown files are loaded from blog/public/blog/*.md via Vite glob import.
The Main.xmlui for the blog app used hardcoded Page routes with index-based references (posts[0], posts[1], etc.).

Adding a new post to the published blog requires:

Plan: Stop Committing Generated ICS/JSON Files to the Repo

Current State

CI workflow commits cities/*/events.json, cities.json, and version.txt to git after every build
Individual .ics files from scrapers/feeds are also committed
The app does not serve these files to users — it queries Supabase directly
The load-events edge function fetches events.json from raw.githubusercontent.com to upsert into Supabase
cities.json and version.txt ARE used by the frontend at load time (via GitHub Pages)

When “RSVP Today” Stops Making Sense

I received this Meetup email today and could not make sense of it.

  1. Verify Node.js/npm prerequisites

  node --version && npm --version
  Output: v20.19.0 and 10.8.2 ✅ (meets v20+ requirement)

  ---
  2. Install .NET 9.0 SDK on macOS

  brew install dotnet

XMLUI Select Component Reset Feature Implementation

Initial Exploration

Human: do you see the Select implementation here?

Claude: [Claude examines the Select.tsx file]

I see the Select component implementation.

├── node_modules
│   ├── @adobe
│   │   └── css-tools
│   │       ├── LICENSE
│   │       ├── Readme.md
│   │       ├── dist
│   │       │   ├── index.cjs
│   │       │   ├── index.cjs.map
│   │       │   ├── index.mjs

	<!-- after -->
	<HStack>
	<WeatherStat
	label="Cloud Cover"
	value="{condition.cloudcover}%"
	/>
	<WeatherStat
	label="Humidity"
	value="{condition.humidity}%"
	/>

	<!-- before -->
	<HStack>
	<VStack>
	<Text variant="secondary" fontSize="$fontSize-sm">Cloud Cover</Text>
	<Text fontWeight="semibold" fontSize="$fontSize-lg">
	{condition.cloudcover}%
	</Text>
	</VStack>

	<VStack>

	<Component name="TubeStops">
	<DataSource
	id="stops"
	url="https://api.tfl.gov.uk/Line/{$props.line}/StopPoints"
	transformResult="{window.transformStops}"
	/>
	<Text variant="strong">{$props.line}</Text>
	<Table data="{stops}">
	<Column width="3*" bindTo="name" />
	<Column bindTo="zone" />