THREAD — Powered by Filigran

Official website of THREAD, Filigran's annual conference for the threat intelligence and cyber defense community.

Live at thread.filigran.io — October 15, 2026, Les Jardins de Saint-Dominique, Paris.

Editing the content (no coding required)

All the text of the website lives in three files under src/content/. Edit the text between quotes ("..."), commit to main, and the site redeploys automatically in about a minute.

File	What it contains
src/content/site.ts	Event name, date, venue, countdown, key figures, footer links, contact email
src/content/sections.ts	"Why THREAD" story, audiences, the five zones, speakers, Community Zone experiences
src/content/agenda.ts	The full agenda, track by track (instructions at the top of the file)
src/content/sponsors.ts	Sponsorship tier packages and the sponsor logo showcase

Each file starts with a comment block explaining exactly how to edit it. You can do this entirely from the GitHub web interface: open the file, click the pencil icon, edit, and commit.

Managing the sponsors section

The sponsors section lives entirely in src/content/sponsors.ts. It has two parts:

Sponsorship packages

The sponsorship object holds the three tier cards ("Supporter", "Partner", "Premier"). Rename the name field, update tagline and perks, and reorder entries freely — the page reflects your changes after the next deploy.

Sponsor logo showcase

The logo grid is hidden by default and only appears once you switch it on.

Step 1 — Add the logo file

Drop the logo into the public/sponsors/ folder (create it if it doesn't exist yet). SVG is preferred because it scales perfectly. Name it clearly, e.g. acme-corp.svg.

Step 2 — Register the sponsor

Open src/content/sponsors.ts and add an entry to the sponsors.items array:

{ name: "Acme Corp", logoPath: "/sponsors/acme-corp.svg", url: "https://acme.com", tier: "Premier" }

tier is optional but controls the display order (Premier → Partner → Supporter).

Step 3 — Switch the section on

In the same file, set sponsors.show to true. While it is false the entire logo section is invisible — no empty grid, no layout shift.

Step 4 — Commit to main

The site redeploys automatically. No other code changes are needed.

Tech stack

Same stack and design system as filigran.io:

• Vite + React 18 + TypeScript
• Tailwind CSS with the Filigran design tokens (Sora font, dark navy, cyan accent)
• lucide-react icons

Development

npm install
npm run dev        # local dev server on http://localhost:8080
npm run build      # typecheck + production build to dist/
npm run preview    # preview the production build

Deployment

Every push to main triggers the Deploy to GitHub Pages workflow: build with Node 20, upload the dist/ artifact, deploy to GitHub Pages. The custom domain (thread.filigran.io) is configured in the repository Pages settings.