front-end-conferences: a plain Markdown list of front-end events

A repository with exactly one file in it

The top level of this repository contains README.md and nothing else. There is no build script, no package manifest, no CI configuration and no site generator. Whatever value the project has is in the text of that single file.

That makes it easy to read and easy to contribute to. The contribution rule stated in the file is one sentence: if you know of a conference that has not been listed, fork the repository and open a pull request. There is no schema to learn and no tooling to run before sending a change.

It also means there is no stability contract. There are no GitHub releases for this project, so there is no version to pin, no changelog and no migration story. The only maintenance signal available is the date of the last push to the repository, which was on 2026-09-01. Nothing in the repository says who reviews pull requests or how quickly they are merged, so a contributor cannot tell from the repository alone whether an entry will be accepted.

The content is also duplicated elsewhere. The file notes that the same list is published at https://frontendfront.com/conferences, so the website and the repository are two views of the same editorial work, and the website is the friendlier place to consume it.

The entry format is three lines of Markdown per event

Each conference is written as a linked title, a date line and a location line, with the location naming the city and the country and then indicating whether the event is available online. The formatting uses Markdown line breaks to hold the three lines together as one paragraph.

Reading the date lines alone shows the structure of the data:

25-28 November 2024  
7-10 September 2026  
12-16 October 2026  
23 & 26 October 2026  

The date conventions are not uniform. Some entries use a hyphenated range, some use an ampersand between two separate days, and one uses a hyphen written as a word with spaces around it. The regional spelling of countries also varies. One entry writes The Netherlands while another writes Netherlands, and one North American entry uses a two letter state abbreviation rather than spelling out a region.

This is a hand-maintained list formatted by convention rather than a validated data source. If you plan to parse it, you have to accept the inconsistencies instead of assuming a schema, and if you contribute, matching the local style of the section you edit is more likely to produce an accepted pull request than imposing a new one.

Four headings divide the list, and one of them is thin

Events are grouped under four headings: Asia, Europe, North America and Online. Europe carries the bulk of the list, with entries from Freiburg, Berlin, London, Munich, Torremolinos in Málaga, Vienna, Amsterdam and Düsseldorf. North America covers New York twice over in late November 2026, Phoenix and Montreal. The Online heading holds a single entry.

Asia is the weak spot. The section contains one entry, the International JavaScript Conference Singapore, dated 25-28 November 2024, and that date is already in the past relative to the rest of the list. So the list is not only unevenly distributed by region, its one Asian entry is stale in a way that is visible from the data alone.

The Online heading has the opposite problem. One event listed under Online is not the same thing as every event being online-capable, because the location lines of most entries already carry an Online option. The heading therefore covers events hosted purely online, not the full set of events with a streaming option. Anyone filtering for remote availability has to read each location line rather than relying on the heading structure.

Two recurring series dominate the European entries

The International JavaScript Conference appears more than once, in the Singapore entry under Asia and in the Munich entry under Europe, plus a separate New York edition under North America. Two other entries belong to the HalfStack series, one in Vienna in November 2026 and one in Phoenix in February 2027.

The practical consequence is that a reader looking for a specific track or a specific organiser will find multiple rows rather than one. Filtering the file by conference name to see all dates for a series is a reasonable thing to do, and it is the clearest use case for the flat text format.

There is also a recurring pattern in how the dates cluster. The densest part of the list is the second half of September 2026 through the end of October 2026, where Berlin, London, Munich, Torremolinos and New York all land within about six weeks of each other. Booking travel around that window means the venues are competing for the same attendee budgets and dates.

Where this list stops being a planning tool

The repository answers one question, which upcoming front-end events exist and roughly when and where they run. It does not answer the questions you normally need before booking. There are no ticket prices, no agenda or speaker information, no CFP deadlines and no CFP submission details. There is also no record of past events, so the file cannot tell you how a conference ran last year or whether it is worth attending for the first time.

Every entry does link to the conference's own site, and those links are the place the missing detail lives. The list is best treated as an index into those sites rather than a substitute for them.

Two further limits are worth stating plainly. The last push was on 2026-09-01, so a conference announced after that date may simply not be in the file yet. And there is no LICENSE file among the top level entries, so the terms for copying the list text into your own tooling are not stated by the project.

For anyone automating this, the right pattern is to treat the file as a lead list, open the linked site for each entry, and keep your own record of what you verified.

Editorial conclusion

Treat front-end-conferences as a lightweight reference and a place to contribute rather than as a booking source. It works if you want a quick scan of upcoming events and are comfortable verifying dates on the conference sites themselves, and it does not work if you need confirmed schedules, pricing or historical data. Before relying on any entry, open the linked conference page, because the Singapore entry still shows a 2024 date while the rest of the list runs into 2027, and note that the repository carries no licence file, so reuse of the list text needs your own decision.

Frequently asked questions

Official sources

1. frontendfront/front-end-conferences on GitHub
2. Issues
3. README