Skip to content

Commit 8702a21

Browse files
committed
fix: publish curation post
1 parent ee6ea05 commit 8702a21

File tree

3 files changed

+53
-0
lines changed

3 files changed

+53
-0
lines changed

public/blog/_data.json

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4917,5 +4917,14 @@
49174917
"code"
49184918
],
49194919
"published": true
4920+
},
4921+
"curation-all-the-way": {
4922+
"title": "Curation all the way",
4923+
"date": "2018-10-05 14:27:47",
4924+
"modified": "2018-10-05 14:19:57",
4925+
"tags": [
4926+
"web"
4927+
],
4928+
"published": true
49204929
}
49214930
}
Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
# Curation all the way
2+
3+
Curation is massively important to ffconf, and as of last week, ffconf now has a complete line up of speakers and sessions for ffconf v10 in early November.
4+
5+
<!--more-->
6+
7+
The talks are:
8+
9+
1. The Future of JavaScript & Machine Learning
10+
- Mentoring: Being the help you wish you'd had
11+
- Practical Web Animation
12+
- Is it possible to build a truly diverse community?
13+
- Back to the future of JS: the next features and amazing proposals
14+
- WebXR: A New Dimension For The Web
15+
- Dear Developer, the Web Isn't About You
16+
- Weird Web & Curious Creation
17+
18+
You can get your ~~Friday (sold out)~~ **[Thursday ticket today](https://ffconf.org/tickets)**.
19+
20+
_Remember: it's the same line up, the same content, the same amazing day._
21+
22+
## How and why
23+
24+
Unlike a lot of other events, ffconf is carefully curated by me. Call For Papers (CFP) has typically only accounted for just one of the eight talks in previous years. As soon as the previous ffconf event is over, I start thinking about the _types of talks_ I want to hear right away 🧠⚡️
25+
26+
The process (since 2011) has been to list the topics I want to host at ffconf, then match that content up to a potential speaker.
27+
28+
My invitations to speakers are always asking if they would speak to a particular topic or specific question.
29+
30+
As a conference speaker myself, I find it a little frustrating to receive an invitation that simply says "can you speak at our event". Sure, I'd be happy to speak, but _why_ are you inviting me?
31+
32+
Again, as a speaker myself, I felt like a significant number of events would use the same speaker year after year. With that in mind, I made one of ffconf's golden rules: no speaker speaks again.
33+
34+
It's a blessing and a curse for curation! It's made curation harder and harder as the years have piled on! The huge positive upshot is that ffconf has hosted 78 unique individuals since 2009 🎉
35+
36+
[![Our attendees love the curation](/images/ffconf-curation.png)](https://ffconf.org)
37+
38+
Why don't we reveal speakers? Initially this was an accident back in 2014 they were going to be revealed - but I just forgot!
39+
40+
The following year, I realised that hiding (or blurring) the speakers only reinforced the idea that ffconf is content first. We do start to slowly reveal the speakers much closer to the time.
41+
42+
Painstakingly careful curation is absolutely one of the keys to the success of our event. If you're thinking of running an event yourself, I'd highly recommend it. And if you want to see how it works out, **[see it first hand at ffconf in November](https://ffconf.org/tickets)**.
43+
44+
If you want to find out more about the behind the scenes of ffconf, you can also [subscribe to our newsletter](https://ffconf.org/news)

public/images/ffconf-curation.png

112 KB
Loading

0 commit comments

Comments
 (0)