Skip to content

Pereira Tech Day 2026 — August 22, 2026 — Where talent, technology, and brands meet. Save the date.

Únete

Contributing to Pereira Tech Talks

How to contribute to Pereira Tech Talks — from giving a talk to writing for the blog to maintaining the open-source website. Every kind of contribution has a clear path and a real impact.

Last updated

Why contribute

Pereira Tech Talks runs on the time and care of people who show up. There is no full-time staff, no agency, no marketing team. Every meetup, every talk, every page on this site exists because someone decided to spend a few hours moving it forward.

Contributing back is how the community stays alive — and how it scales beyond what any single organizer can carry. Below is a map of the paths into contribution, sorted by the kind of energy each requires.

Paths of contribution

1. Speak at a meetup or Pereira Tech Day

The highest-leverage contribution: bring a topic, share what you have learned, and help someone else grow into the next stage of their craft.

  • What we look for: practical, technical talks grounded in real experience. Architecture, AI/agents, devops, mobile, web platforms, security, software lifecycle, community programs.
  • First-time speakers are welcome. We mentor through the Speaker School.
  • How to propose: Call for Speakers.

2. Mentor a new speaker

If you have given talks before, the most multiplicative thing you can do is mentor someone preparing their first one. Speaker School cohorts always need mentors.

  • Reach out via the contact form with the subject “Mentor at Speaker School” and tell us your area.

3. Lead or co-lead a vertical

The verticals (Speaker School, La Biblioteca del Mañana, AI Channel, Monthly Meetups) need stewards — people who take responsibility for their cadence, programming, and direction.

4. Help organize events

Logistics, communication, photography, recording, hosting, MC. These are the invisible threads that make the in-person experience work.

  • Show up to a meetup, find an organizer, and tell us how you would like to help. Or write to us.

5. Write for the blog

The bilingual blog is part of how we connect Pereira to the global tech ecosystem. We publish recaps, technical deep-dives, talks turned into essays, and community reflections.

  • Bring a topic, an angle, and a draft. We pair-write and edit before publishing.
  • Open a discussion via the contact form with the subject “Blog contribution”.

6. Connect a sponsor

If you work at — or have a clear line to — a company that benefits from a strong local tech community, intro us. Sponsorship sustains everything that is free to attend.

7. Contribute to the open-source website

This entire site is open source. Anything from a typo fix to a new page, a new content type, or a Lighthouse improvement is welcome.

  • Repository: github.com/pereiratechtalks
  • Stack: Astro 5, Svelte 5, Tailwind 4, TypeScript, Biome, MDX.
  • Local dev: pnpm install && pnpm run dev (Node 22+, pnpm 10+).
  • Before opening a PR: run pnpm run biome:check, pnpm run astro:check, pnpm run test, and pnpm run build locally.
  • Spanish content: every blog post, page, and major UI string must exist in both English and Spanish. Spanish requires correct diacritical marks (ñ, accented vowels, interrogative accents).
  • Conventional commits: <type>: <description> where type is one of feat, fix, docs, style, refactor, test, chore, perf, ci.

For ongoing or large changes, open an issue first to discuss direction.

8. Help with photography, video, or design

We always need help capturing meetups, editing recordings, and producing edition branding for Pereira Tech Day. Reach out via the contact form with subject “Media contribution”.

9. Just be there

Showing up is a contribution. Every attendee gives back energy that the speakers and organizers feel. There is no rite of passage to belong.

Recognition

Contributors are listed at Contributors. Speakers appear at Speakers. Sponsors appear at Sponsors. If you have contributed and are not yet listed, write to us and we will add you.

A few principles we work by

  • Bilingual by default. Anything user-visible exists in EN and ES.
  • Accessible by default. WCAG AA, fast pages, agent-readable Markdown twins.
  • Open by default. Code, content, and decisions are public unless there is a clear reason not to be.
  • Welcoming by default. Beginners, first-time speakers, and people coming from non-traditional paths are core to who we are.

Questions?