Skip to content

Commit f94eab1

Browse files
committed
chore: remove unused Community Events section from README
1 parent 5113577 commit f94eab1

1 file changed

Lines changed: 0 additions & 16 deletions

File tree

README.md

Lines changed: 0 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -94,22 +94,6 @@ To add a Kotlin User Group (KUG), proceed the following way:
9494
You can see the structure and types of the expected configuration in [the JSON schema](/data/schemas/user-groups.json).
9595
Once you publish a pull request, the changes will be validated by [GitHub Actions Workflow](.github/workflows/validate-user-groups-data.yml) to prevent misconfiguration.
9696
97-
### Community Events
98-
99-
To add an event to the Community Events, do the following:
100-
1. Fill the event info in the [events.yml](/data/events.yml) with the next:
101-
- `lang`, two-letter code considering [ISO 639-1 format](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes).
102-
- `startDate`, in the format 'yyyy-mm-dd'.
103-
- `endDate`, in the format 'yyyy-mm-dd'. For the on day event fill the same date as in the startDate.
104-
- `location`, in the form of 'City, Country'. You can omit it for an online event.
105-
- `online`, set this key with `true` value in case of online event.
106-
- `speaker`, the speaker's name.
107-
- `title`, event's title.
108-
- `subject`, a title of a talk.
109-
- `url`, link to the event web page.
110-
You can see the structure and types of the expected configuration in [the JSON schema](/data/schemas/events.json).
111-
2. Publish the changes creating a pull request. The changes will be validated by [GitHub Actions Workflow](.github/workflows/validate-events-data.yml) to prevent misconfiguration.
112-
11397
### Case Studies
11498
11599
To add a case study, do the following:

0 commit comments

Comments
 (0)