Skip to content
Menu

An event website that connects the process.

I build websites for events, conferences and trade fairs: from programme and attendee information to registration, exhibitor directories and recurring editions.

Konrad Dziekan

Strategy, content and code. From diagnosis to implementation.

An event has several audiences. The site connects them.

Attendees, speakers, exhibitors and organisers need different information and actions. The website must support preparation, operation and a useful archive after the event.

Programme and event content

Agenda, speakers, location, partners and practical information receive a clear structure and editorial ownership.

Registration and communication

Forms, confirmations and data handover follow the agreed process. Payments and tickets need a separate specification.

Exhibitors and partners

Profiles, a directory, filters and partner materials can form a distinct module with publishing and update controls.

Editions and integrations

The architecture accounts for archives, future editions, languages and integrations. Each module is scoped before delivery.

What you get from this work.

  • A map of roles, content and attendee journeys.
  • A working website and the agreed event modules.
  • Publication, operation and edition-archive rules.

From a first conversation to implementation.

I lead the diagnosis and key decisions. We agree the scope and responsibilities before implementation.

  1. Map the event

    Agree roles, deadlines, data, registration and team responsibilities.

  2. Build the site and modules

    Connect content design with features suited to this event.

  3. Check readiness

    Test critical journeys and prepare operation and future updates.

Before you decide.

Can I commission an information-only site?

Yes. Registration, tickets, exhibitor directories and other modules are optional. The scope follows the event process.

Can the website support recurring editions?

Yes. We first define the relationship between the current edition, archives, URLs and content that should remain available.

Are ticketing and check-in always included?

No. Payments, tickets, QR and check-in require their own rules, integrations and tests and are included only in an agreed scope.

Tell me what needs to change.

Send your website address and describe the goal or the issue. I will help identify the scope and the next step.

+48 695 987 600See all contact details