Website and Architecture

A Wix site extended with Velo code, plus a documentation-only repo that records how everything around it connects.

The site

Developed with the Wix CLI and Git integration: page code, backend modules and HTTP functions live in a repo. Pushing does not publish; a separate publish step does, and there is no staging site.
Members and newsletter subscribers are Wix Contacts carrying one of two labels. They reach the email provider live through automation actions, or in bulk through admin migration jobs, with a webhook coming back to confirm.
News and events are not typed into the CMS. The admin tool pushes them through authenticated HTTP routes, and read-only routes serve its duplicate checks and social drafter.
Page code covers a group directory lightbox, prefilled contact forms, a signup form that blocks existing members, and a shared tag-pill component with a style guide page.
Secrets sit in Wix's Secrets Manager, never in the repo.

Screenshots

The live public site, tasclimatecollective.org. Public pages only, captured without signing in or submitting anything. Photos of people in banner images are cropped out.

The News and Updates page with category, source and tag filters above a grid of article cards with tag pills — News: articles imported through the admin tool, filterable by tag.

The Upcoming Events page with filters for past or upcoming, topic, type and location above a grid of event cards — Events: filters and cards built from the events collection.

The Resources page with a tag filter and a grid of resource cards for flyers, submissions and guides — Resources: tag-filtered documents and guides.

The membership page with two ways to join and an empty application form — The join form (empty; nothing was submitted).

The events page at phone width with the menu collapsed — The events page on a phone.

The architecture repo

No code. It exists because knowledge of how the repos relate was living only in people's heads.
Documents cover contact and email data flows, the reconciliation design, the link queue, social posting and its safety properties, the shared tag system, and a handover set on ownership, costs, kill switches and recovery.
Where documents disagree, the handover set wins. Parked and unbuilt plans are kept and labelled as such.

Design decisions

No renaming of existing CMS fields, since the page rework would cost more than the tidy-up is worth; new concepts are mapped onto existing fields.
Every automation can be replaced by hand, and each document says how.

Wix
Velo
Wix CLI
Documentation