diff --git a/docs/code-of-conduct.md b/docs/code-of-conduct.md
new file mode 100644
index 00000000..b9cd0737
--- /dev/null
+++ b/docs/code-of-conduct.md
@@ -0,0 +1,37 @@
+# Code of Conduct
+
+We are a collective and we want to bring people in the community together to exchange ideas, make new friends, and build things as an inclusive, welcoming, and safe community.
+
+Therefore, any harmful or discriminating behavior by anyone (gardeners, organizers, founders, contributors, or absolutely anyone involved in our community) will not be tolerated and results in the offending person(s) being excluded from the group.
+
+Members should be judged by their actions, not criteria such as degrees, age, race, nationality, sex, sexual orientation, gender, gender identity or expression, disability, physical appearance, religion (or lack thereof), or position. We are a diverse community. Leave your egos at the door.
+
+## Be Open
+We welcome one and all. We especially love to adopt newbies in the community. We foster decentralized, open communities, society, and technology, so we should be open to everyone and everything. We all bring different backgrounds and experiences. Great things can happen when we show up with an open mind and curiosities to explore. If you don't have an open mind, this group is not for you.
+
+## Be Respectful
+Be exceptionally kind to others. Respect their work, time, and perspectives. Do not insult or troll others, unless it is for banter (covered in a later point). We all spend our time, resources, and energy to be part of this group. Respect each other, the projects, and the process.
+
+## Be Daring
+Dare to create something nobody did before. If you get stuck, ask for help - people will help you when you ask. This is a community. We create things together.
+
+## What We Create
+Promote Decentralization. Build what matters to you. You can organize events, build applications, or foster public discourse. You can create art and beauty on a computer. Most importantly, create, hack, and build together.
+
+## Contributions in Other Ways
+Banter and memeing is encouraged as you see fit.
+
+## Personal Responsibility
+Everyone in this community is responsible for their own tasks. If you have a project, it is your responsibility to manage it. We are not here to spoon feed you or do your work for you. Ain't nobody got time for that. But we are a community and here to support. Always reach out if you are having issues with completing a task.
+
+## Unacceptable Behavior & Harassment
+Unacceptable behavior includes: intimidation, harassment, abuse, discrimination, derogatory or demeaning words or actions by any participant in our community online or in person. If you have disagreements with someone, communicate directly with each other and work on a solution.
+
+Harassment includes: harmful or prejudicial verbal or written comments related to gender, sexual orientation, race, religion, disability; inappropriate use of nudity and/or sexual images (including presentation slides); inappropriate depictions of violence (including presentation slides); deliberate intimidation, stalking or following; harassing photography or recording; sustained disruption of talks or other events; inappropriate physical contact, and unwelcomed sexual attention.
+
+## Notify Us
+If you are subject to or witness unacceptable behavior, or have any other concerns, you can always notify a project lead, event organizer, or member of the core group. Anytime. We will do everything to help and support you.
+
+---
+
+Code of conduct adopted from [ETHBerlin3](https://ethberlin.ooo/code-of-conduct/) and [EEG](https://docs.ethevents.club/en/code-of-conduct/). Thank you!
\ No newline at end of file
diff --git a/docs/events/cfp.md b/docs/events/cfp.md
index ff5ba2ef..8204e901 100644
--- a/docs/events/cfp.md
+++ b/docs/events/cfp.md
@@ -1,5 +1,7 @@
 # Call for Proposals (CfP)
 
-We have a single form for all those interested in speaking at our [Events](/events/):
+Our [events](/events/) are open to all privacy enthusiasts.
 
-* https://tally.so/r/nrOzXl
\ No newline at end of file
+If you have a proposal for a talk, workshop or other content then you can submit your proposal using this form:
+
+* https://cfp.web3privacy.info
\ No newline at end of file
diff --git a/docs/events/concepts.md b/docs/events/concepts.md
deleted file mode 100644
index 40a95cf2..00000000
--- a/docs/events/concepts.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-sidebar_position: 1
----
-
-# Event Concepts
-
-## Hackathon
-
-## Summit
-
-## Meetup
\ No newline at end of file
diff --git a/docs/events/events.md b/docs/events/events.md
deleted file mode 100644
index 6f5640c1..00000000
--- a/docs/events/events.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-sidebar_position: 5
----
-
-# Events
-
-As part of our initiative, we organise various events and gatherings.
-
-## [Event Concepts](./concepts)
-
-* **[Hackathon](./concepts#hackathon)** - a multi-day event including talks, workshops and hacking
-* **[Summit](./concepts#summit)** - a day-long gathering
-* **[Meetup](./concepts#meetup)** - shorter gatherings for a few hours
-
-## List of events
-
-You can find a list of all our events in the [`@web3privacy/w3pn-events`](https://github.com/web3privacy/w3pn-events) GitHub repository:
-
-* https://github.com/web3privacy/w3pn-events#list-of-events
-
-## Want to speak at our event?
-
-Our events are open to all privacy enthusiasts, if you have a proposal for a talk, workshop or panel discussion then you can submit your proposal using this form:
-
-* https://tally.so/r/nrOzXl
-
-More information can be found on the [Call for Proposals (CfP)](/events/cfp) page.
-
-## Want to become a sponsor?
-
-Please go to the page [Event Sponsoring](/events/sponsors).
\ No newline at end of file
diff --git a/docs/events/formats.md b/docs/events/formats.md
new file mode 100644
index 00000000..89b130ec
--- /dev/null
+++ b/docs/events/formats.md
@@ -0,0 +1,27 @@
+---
+sidebar_position: 3
+---
+
+# Program formats
+
+At each event, the program is made up of [slots](/events/concept#slots) that are filled with different formats.
+
+## Formats overview
+
+| Format | Duration | Slots |
+| --- | --- | --- |
+| [Lightning talk](#lightning-talk) | ~10 minutes | 0.5 |
+| [Talk](#talk) | 25 - 50 minutes | 1 - 2 |
+| [Fireside chat](#fireside-chat) | 25 - 50 minutes | 1 - 2 |
+| [Panel discussion](#panel-discussion) | 50 - 80 minutes | 2 - 3 |
+| [Workshop](#workshop) | 25 - 80 minutes | 1 - 3 |
+| [Campfire](#campfire) | 25 - 80 minutes | 1 - 3 |
+
+## Formats details
+
+### Lightning talk
+### Talk
+### Fireside chat
+### Panel discussion
+### Workshop
+### Campfire
\ No newline at end of file
diff --git a/docs/events/index.md b/docs/events/index.md
new file mode 100644
index 00000000..863eac03
--- /dev/null
+++ b/docs/events/index.md
@@ -0,0 +1,168 @@
+---
+sidebar_position: 5
+---
+
+# Events
+
+Our event concept is based on creating a unified schedule of events for the entire season and spreading events over whole year and different locations. Instead of just doing one huge event in one location that only happens for a day or two, we are trying to create something like a "distributed conference".
+
+We aim to produce high quality events that bring a very similar atmosphere and content to many venues around the world, providing a unique experience for visitors, speakers and other participants.
+
+## List of events
+
+All our events and RSVPs can be found in our lu.ma calendar:
+
+* [lu.ma/web3privacy](https://lu.ma/web3privacy)
+
+The source files can be found in the [`@web3privacy/w3pn-events`](https://github.com/web3privacy/w3pn-events) GitHub repository ([list](https://github.com/web3privacy/w3pn-events/blob/main/README.md#list-of-events)).
+
+## Seasons
+
+In terms of time, everything is divided into individual programme seasons or planning periods. For us, this is the calendar year.
+
+Prior to each season, each [regional team](/events/regional-teams) will prepare a unified event plan for the entire region.
+
+Within the season, all events are prepared together as one package. This also applies to sponsors and speakers, which are gathered for the whole package.
+
+* Current season: [2023](/events/seasons/2023)
+* Upcoming season: [2024](/events/seasons/2024)
+
+[List of seasons →](/events/seasons)
+
+## Regions
+
+The basic division by location is into major regions according to wider regions or continents (e.g. Europe, LATAM, etc.). 
+
+### [Regional teams](/events/regional-teams)
+
+[Regional teams](/events/regional-teams) are responsible for organising events in a specific region. We only start doing events within a region if we have enough people forming a [regional organization team](/events/regional-teams).
+
+### Regions we cover (2024)
+
+For the 2024 season, we want to cover the following regions:
+
+* **Europe** - Europe regional team (EthCC, ETHBerlin, ETHDam, ETHPrague and many more)
+* **Devcon (Southeast Asia)**
+
+Our goal in each region is to spread the events evenly, both in time and space across the entire region (or important events that take place there).
+
+## Date and location
+
+Most of our events are held in conjunction with another major Ethereum event in the region (e.g. Devcon(nect), EthCC, ETHBerlin, ETHPrague, etc.).
+
+Our aim is to cover these big events and offer an alternative to expand the numbers of our supporters.
+
+We are also preparing a couple of separate events within the season, which are intended to complement our event portfolio. These may be events that fill in the less popular periods (eq. Barcelona meetup in winter) or it may be our own Web3Privacy Now hackathon or team building.
+
+## Event types
+
+We divide events into the following types according to their length and goal:
+
+* [Hackathon](./types#hackathon) - a multi-day event including hacking
+* [Summit](./types#summit) -  a day-long gathering
+* [Meetup](./types#meetup) - shorter gatherings for a few hours
+
+[List of event types →](./types)
+
+## Slots
+
+Each event is composed of a predetermined number of slots.
+
+Slots serves as a basic breakdown of the programme of each event. Each slot can be occupied by a talk, workshop, panel debate, etc. (see [Program formats](#program-formats)).
+
+The standard duration of one slot is 30 minutes.
+
+## Program formats
+
+At each event, the program is made up of [slots](#slots) that are filled with different formats.
+
+[List of program formats →](./formats)
+
+## Production
+
+### Catering
+
+The food and drink provided at a particular event is based on other circumstances, such as the amount of admission or duration of the event. Basically, we try to provide our visitors with as much comfort as possible without spending too much.
+
+On the shortest Meetups there is minimal catering water and snacks like fruit, bagels, pizza or similar.
+
+At longer Summits or Hackathons (or paid events) we try to offer a full range of food and drink, including lunch, dinner and various desserts and drinks (incl. beer).
+
+### Content recording
+
+All content at all our events (Meetup, Summit, Hackathon) is recorded (unless stated otherwise). For this purpose we use our own low-cost [Recording setup](./recording).
+
+Larger events such as the Summits can also be streamed online.
+
+## Visitors
+
+### Admission
+
+Whether a particular event is free or we charge admission will depend on the context. The entrance fee and its amount are mainly taken as a tool for self-regulation of the number and quality of visitors.
+
+We will apply admission fees where we expect a lot of interest and, on the contrary, events in less busy periods should be free of charge, which will serve as an incentive for visitors.
+
+### Pre-registration
+
+With the start of each [season](#seasons) we will start pre-registration for **all events** within that season. Potential visitors will be able to express their preferences for when and where they want to attend our events.
+
+The only private information we collect for pre-registration will be name and email. Visitors are advised to use a [privacy email provider](https://www.privacytools.io/privacy-email) like [Skiff Mail](https://skiff.com/mail) or [Proton Mail](https://proton.me/mail).
+
+Pre-registration will be done through temporary event profiles on the [lu.ma platform](https://lu.ma/web3privacy).
+
+Approximately 2-3 months prior to the event, the final registration will open and all people will be notified via the email they entered during pre-registration (see [Ticketing](#ticketing)).
+
+### Ticketing
+
+Final ticketing (registration) starts the moment we have a confirmed date and location, usually 2-3 months before the event.
+
+* Free admission - profile and registration on lu.ma
+* Paid admission - lu.ma OR special website and custom payment gateway (like Pretix)
+
+All those who have pre-registered are notified of final registration via email.
+
+#### Payment methods
+
+We usually accept these payment methods:
+* fiat
+  * payment cards
+* cryptocurrencies
+  * BTC, BTC (Lightning)
+  * ETH and stablecoins (also L2s)
+  * XMR
+
+## Contributors
+
+### Speakers
+
+We are looking for speakers for all events combined using a single [Call for Proposal (CfP)](/events/cfp) form.
+
+Within this form, speakers are able to choose the months and locations that suit them. This will offer speakers great flexibility in when and where they can present their ideas or projects.
+
+### Sponsors
+
+For information about sponsorship options, continue to page [Event sponsoring](./sponsors).
+
+### Volunteers
+
+TODO
+
+## Privacy
+
+We respect the privacy of our visitors and are therefore guided by the following principles.
+
+**Please respect the privacy of others!**
+
+### No-photo policy
+
+It is forbidden to take any photographs or video recordings of visitors at our events (except on stage) unless they give their express permission.
+
+As organizers, we don't share any such photos, and if we do - it's only with anonymized faces of visitors.
+
+### No personal data sharing
+
+We do not provide the personal information about visitors or other involved people to any other party.
+
+## Code of Conduct
+
+Our events are guided by our community [Code of Conduct](/code-of-conduct).
\ No newline at end of file
diff --git a/docs/events/recording.md b/docs/events/recording.md
new file mode 100644
index 00000000..ea2a6d91
--- /dev/null
+++ b/docs/events/recording.md
@@ -0,0 +1,7 @@
+# Recording setup
+
+All content at our events is recorded (unless stated otherwise).
+
+We use our own low-cost setup to record these talks, panel discussions and other content at our events.
+
+TODO
\ No newline at end of file
diff --git a/docs/events/regional-teams.md b/docs/events/regional-teams.md
new file mode 100644
index 00000000..d63c71bc
--- /dev/null
+++ b/docs/events/regional-teams.md
@@ -0,0 +1,13 @@
+---
+sidebar_position: 4
+---
+
+# Regional teams
+
+The regional team is responsible for organising [events](/events) in a [specific region](/events/concept#regions) (e.g. Europe, LATAM, etc.).
+
+## Teams overview
+
+| Region | Lead | Contributors | Base(s) |
+| --- | --- | --- | --- |
+| 🇪🇺 **Europe** | Tree | PG, Mykola, Coinmandeer, Alina | 🇨🇿 Prague, 🇪🇸 Barcelona, 🇮🇹 Rome |
\ No newline at end of file
diff --git a/docs/events/seasons/2023.md b/docs/events/seasons/2023.md
new file mode 100644
index 00000000..4453e8e5
--- /dev/null
+++ b/docs/events/seasons/2023.md
@@ -0,0 +1,7 @@
+# 2023 Season
+
+This was our first season for which we had no plan or concept. Our community was just beginning.
+
+We hosted 3 events this season, 2 summits and 1 meetup.
+
+All the events were held in Europe because we only had a basic European team.
\ No newline at end of file
diff --git a/docs/events/seasons/2024.md b/docs/events/seasons/2024.md
new file mode 100644
index 00000000..abc7955e
--- /dev/null
+++ b/docs/events/seasons/2024.md
@@ -0,0 +1 @@
+# 2024 Season
\ No newline at end of file
diff --git a/docs/events/seasons/index.md b/docs/events/seasons/index.md
new file mode 100644
index 00000000..ffc613cd
--- /dev/null
+++ b/docs/events/seasons/index.md
@@ -0,0 +1,20 @@
+---
+sidebar_position: 1
+---
+
+# Seasons
+
+## List of seasons
+
+| Season | Regions | Events | Countries | Cities |
+| --- | --- | --- | --- | --- |
+| [2024](./2024) | Europe, Devcon | 17 | 12 | 16 |
+| [2023](./2023) | Europe | 3 | 2 | 2 |
+
+## Season details
+
+```mdx-code-block
+import DocCardList from '@theme/DocCardList';
+
+<DocCardList />
+```
\ No newline at end of file
diff --git a/docs/events/sponsors.md b/docs/events/sponsors.md
index cc27d6ed..63fd53fb 100644
--- a/docs/events/sponsors.md
+++ b/docs/events/sponsors.md
@@ -1,4 +1,4 @@
-# Event Sponsoring
+# Event sponsoring
 
 For those interested in promoting their own brand and supporting our efforts, we offer the opportunity to sponsor our events.
 
diff --git a/docs/events/types.md b/docs/events/types.md
new file mode 100644
index 00000000..2cfa169e
--- /dev/null
+++ b/docs/events/types.md
@@ -0,0 +1,36 @@
+---
+sidebar_position: 2
+---
+
+# Event types
+
+We divide events into the following types according to their length and goal:
+
+## Overview
+
+| Type | [Slots](/events/concept#slots) | Description |
+| --- | --- | --- |
+| [Hackathon](#hackathon) | *variable* | a multi-day event including hacking |
+| [Summit](#summit) | 10 - 16 | a day-long gathering |
+| [Meetup](#meetup) | 3 - 5 | shorter gatherings for a few hours |
+
+## Details of types
+### Hackathon
+
+A hackathon is usually a multi-day event focused on creation. What makes it different from other types is that it should end with some work being done, whether it's some privacy-focused projects or pushing our own projects forward.
+
+A Hackathon is usually accompanied by one or more Meetups, or possibly a Summit.
+
+The number of slots at the hackathon is very flexible.
+
+### Summit
+
+The Summit is an all-day event, usually followed by an afterparty.
+
+Summit is usually made up of 10-16 slots.
+
+### Meetup
+
+A meetup is a shorter type of event for 2-6 hours (usually afternoon/evening).
+
+The number of slots at a meetup is usually 3-5.
\ No newline at end of file