1
00:00:01,050 --> 00:00:13,110
So now we're going to go into writing your
pitch. Okay, so in this section, we are

2
00:00:13,110 --> 00:00:18,990
going to talk about what a proposal AKA
pitch is, coming up with a great title,

3
00:00:19,050 --> 00:00:24,510
and a little writing exercise. That's
actually switched around... Writing your

4
00:00:24,510 --> 00:00:35,970
bio, writing exercise, and then optionally
anybody who wants to present their titles

5
00:00:36,000 --> 00:00:45,420
into pitches. Okay, so, whatever your
motivation is for speaking, you first need

6
00:00:45,420 --> 00:00:50,070
to get selected to speak. And for that,
you need to create a proposal or pitch.

7
00:00:50,400 --> 00:00:54,870
And we'll use those terms interchangeably.
And one will that will get your talk

8
00:00:54,870 --> 00:01:00,000
selected. And also, since your proposal
defines the scope of your talk, it can be

9
00:01:00,030 --> 00:01:03,750
a good early step in the overall process
of developing your talk.

10
00:01:04,710 --> 00:01:11,730
What makes a great pitch? So first, here's
an example of a good one. Responsify all

11
00:01:11,730 --> 00:01:16,050
the Things. In our new web multiverse,
it's more important than ever to make your

12
00:01:16,050 --> 00:01:20,400
valuable content available to all users,
regardless of how they access your site.

13
00:01:20,940 --> 00:01:27,540
In this talk, we'll cover how responsive
web design came about, the latest RWD news

14
00:01:27,540 --> 00:01:31,680
and trends, and some basic and not so
basic techniques you can use to make your

15
00:01:31,680 --> 00:01:36,330
next WordPress theme a responsive one.
Intended for developers and designers who

16
00:01:36,330 --> 00:01:39,180
aren't afraid to get their hands dirty
with a little code.

17
00:01:42,180 --> 00:01:49,470
So this is a good length. It tells you
what the talk will cover and it tells you

18
00:01:49,470 --> 00:01:53,670
who it's aimed at. In some cases, you
might also want to say what people will

19
00:01:53,670 --> 00:02:01,410
walk away with from this talk. On the
topic of the title, beware of too clever

20
00:02:01,410 --> 00:02:06,390
titles. The title should stand on its own
without a blurb. Here's an example of a

21
00:02:06,390 --> 00:02:14,820
bad one, "CSS dreams and elephants." What
do you think makes this a good or bad

22
00:02:14,850 --> 00:02:20,820
title? And this is a question for
discussion right now. Aurooba?

23
00:02:20,940 --> 00:02:25,350
It doesn't really tell me what I will be
getting out of this talk.

24
00:02:25,570 --> 00:02:30,460
Right? So in that title we have no idea
what it's about, what you'll be getting

25
00:02:30,490 --> 00:02:39,700
out of it. Anyone else have anything to
add? Okay, great. Yeah, that's pretty much

26
00:02:39,700 --> 00:02:43,450
it. That's, it's it's a cute title, but it
is too vague.

27
00:02:47,290 --> 00:02:51,190
Generally, your talk proposal and the
introduction of your outline will be quite

28
00:02:51,190 --> 00:02:56,860
similar. A good introduction should have
all the things a good pitch would have.

29
00:02:57,220 --> 00:03:01,570
However, in a pitch, you might want to
spice it up a bit. Ultimately, both the

30
00:03:01,570 --> 00:03:09,550
introduction and pitch should contain some
more content. For a pitch, you want to

31
00:03:09,550 --> 00:03:13,120
tailor the tone of your writing and
vocabulary to the specific audience and

32
00:03:13,120 --> 00:03:17,920
event that you're applying to. This is
very important. Some ideas of how you may

33
00:03:17,920 --> 00:03:22,780
tailor your pitch for specific audiences
and events: The tone may be different. A

34
00:03:22,780 --> 00:03:27,700
business crowd may be formal, a Meetup may
be more casual, so customize the tone of

35
00:03:27,700 --> 00:03:32,200
your pitch to your specific audience. At
WordPress events, in general, we tend to

36
00:03:32,200 --> 00:03:37,180
be pretty casual. You might want to use
different vocabulary depending on the

37
00:03:37,180 --> 00:03:41,890
audience. And you might want to stress
different talks or points of interest

38
00:03:41,920 --> 00:03:43,780
depending on the audience or event.

39
00:03:45,910 --> 00:03:51,070
There are six important points to take
note of when writing both your outline and

40
00:03:51,070 --> 00:03:54,730
your pitch. And this comes from the site
that is written on the screen:

41
00:03:56,740 --> 00:04:06,670
weareallaweso.me/for_speakers/how-to-write-a-compelling-proposal.html.
Point number one: Direct the proposal to

42
00:04:06,670 --> 00:04:12,760
the attendees, not the curators. Many
conferences use your talk proposal as the

43
00:04:12,760 --> 00:04:17,770
description of the talk in their program.
With that in mind, your target reader is

44
00:04:17,770 --> 00:04:22,090
the conference attendee who is reading the
program. Tell the reader why your talk

45
00:04:22,090 --> 00:04:26,260
will interest them and what they will
learn. The curators want to put together a

46
00:04:26,260 --> 00:04:30,610
great conference with compelling talks for
their attendees. The talk will be part of

47
00:04:30,610 --> 00:04:35,200
the package they offer so sell it! Make
sure you research the event. Are there

48
00:04:35,200 --> 00:04:39,430
different tracks? Is the audience. Are
there lots of devs? Is it mostly for

49
00:04:39,430 --> 00:04:44,890
users? Is it design heavy? Different
WordCamps have different personalities.

50
00:04:45,130 --> 00:04:48,520
Are they short on really technical
presentations? Light on talks for

51
00:04:48,520 --> 00:04:52,120
beginners? Try to fill a need, such as
podcasting.

52
00:04:54,250 --> 00:04:59,560
Number two: Be specific about the focus
that your talk will have. Generally

53
00:04:59,560 --> 00:05:03,790
speaking, a shallow introduction to many
things is not as interesting as an in

54
00:05:03,790 --> 00:05:08,620
depth introduction to one thing. If you
discuss the broader topic, do so only to

55
00:05:08,620 --> 00:05:10,660
set the context for what you'll focus on.

56
00:05:13,150 --> 00:05:18,880
Number three: One strategy is pose the
question that your talk will answer. Often

57
00:05:18,880 --> 00:05:24,580
talks answer questions that start with
how, why, when, and so on. An easy trick

58
00:05:24,580 --> 00:05:28,870
is to directly ask these questions in your
proposal, leaving the reader wondering the

59
00:05:28,870 --> 00:05:29,320
answer.

60
00:05:29,290 --> 00:05:36,070
Number four: Make your point as simply as
you can. If your first draft requires more

61
00:05:36,070 --> 00:05:41,620
than two paragraphs to get to the point of
your topic, edit to narrow things down.

62
00:05:42,130 --> 00:05:46,330
Take out any words that can be removed
without changing the meaning. You may have

63
00:05:46,330 --> 00:05:50,950
a lot of competition so try to make a good
impression quickly. If your proposal is

64
00:05:50,950 --> 00:05:54,670
too much work to read or understand, i
might get skipped during the selectio

65
00:05:54,670 --> 00:06:03,040
 process. 

66
00:06:01,130 --> 00:06:06,920
Number five: Use proper grammar, spelling,
and punctuation. If you submit a sloppily

67
00:06:06,920 --> 00:06:10,880
written proposal, you appear careless and
as if you're not taking the opportunity

68
00:06:10,880 --> 00:06:15,650
seriously. You risk being rejected on
those grounds outright. Speaking requires

69
00:06:15,650 --> 00:06:19,160
a lot of thoughtful preparation, and
curators can only assume it will be as

70
00:06:19,160 --> 00:06:21,470
careless when preparing the talk itself.

71
00:06:23,070 --> 00:06:27,900
And number six: Have your proposal
reviewed by someone with experience. Just

72
00:06:27,900 --> 00:06:32,160
as you might ask a friend to critique a
draft of your CV, an essay or the talk

73
00:06:32,160 --> 00:06:37,140
itself, ask someone, ideally a writer,
speaker or curator to review your talk

74
00:06:37,140 --> 00:06:41,850
proposal. They'll catch typos as well as
verify whether your proposal explains the

75
00:06:41,850 --> 00:06:45,690
scope of your talk, and explains its
benefits to your audience.

76
00:06:48,030 --> 00:06:52,620
Next, we're going to talk about coming up
with a great title. We need a good title

77
00:06:52,620 --> 00:06:57,480
for your talk. You're going to want to try
to think of something catchy but

78
00:06:57,480 --> 00:07:02,970
explanatory. Be aware of too clever titles
and create a title that can stand on its

79
00:07:02,970 --> 00:07:07,260
own without a blurb. For example, don't
use something like "CSS and Elephants."

80
00:07:09,300 --> 00:07:14,760
We're also going to talk right now about
writing your bio. When you submit a

81
00:07:14,760 --> 00:07:19,890
proposal or pitch to an event, you'll most
often be asked to include a short bio.

82
00:07:20,370 --> 00:07:24,990
Bios are often the hardest to write well,
but here are some pointers to follow. It

83
00:07:24,990 --> 00:07:26,580
should be written in the third person.

84
00:07:27,980 --> 00:07:32,720
It should be succinct, but descriptive. It
should only be a short paragraph and go

85
00:07:32,720 --> 00:07:37,430
for economy of words. Try to say the most
you possibly can with the fewest possible

86
00:07:37,430 --> 00:07:42,590
words. Mention what your position or job
is, and include any credentials that might

87
00:07:42,590 --> 00:07:47,150
be relevant. Mention how many years you've
been in this field, or if it hasn't been

88
00:07:47,150 --> 00:07:51,860
that many, tell a short story about how
you've ended up in your new field. Look at

89
00:07:51,860 --> 00:07:55,700
past examples for the conference you're
submitting to. Why are you the right

90
00:07:55,700 --> 00:08:00,500
person to give this talk and tailor your
bio so your topic makes sense. You might

91
00:08:00,500 --> 00:08:05,570
want to tweak it differently for different
topics and different events. Be human.

92
00:08:05,870 --> 00:08:10,940
WordCamps are usually not too formal. And
feel free to add something about your non

93
00:08:10,940 --> 00:08:14,150
professional interests at the end, but
don't make it your entire bio.

94
00:08:15,320 --> 00:08:19,580
So what we're going to do now is we're
going to have 15 minutes to try drafting a

95
00:08:19,580 --> 00:08:23,870
talk proposal for the idea that you
brainstormed earlier, the title, and your

96
00:08:23,870 --> 00:08:27,770
bio, There'll be a chance to read the
title and pitch to the group after if you

97
00:08:27,770 --> 00:08:31,610
wish. We'll see if we have time for
reading it to each other today or that'll

98
00:08:31,610 --> 00:08:38,570
be part of tomorrow's session. But let's
go ahead and do the 15 minutes. If you

99
00:08:38,570 --> 00:08:43,190
need me to flip back and forth between any
of the slides, you can write that in the

100
00:08:43,190 --> 00:08:49,340
chat; I'll watch for that. I'll also grab
a link from our Slack. I put the link to

101
00:08:49,340 --> 00:08:52,940
the slides if you want to grab them and be
able to refer to those sections because

102
00:08:52,940 --> 00:08:58,040
we're working on three things at once
right now. So go ahead and start that. If

103
00:08:58,040 --> 00:09:03,080
you've any questions about it, put it into
the chat. I'll check that as well. So I'm

104
00:09:03,080 --> 00:09:06,290
going to go ahead and start 15 minutes.

105
00:23:43,920 --> 00:24:19,290
There's about 30 seconds left. All right.
If anyone needs more time, you can always

106
00:24:19,290 --> 00:24:25,410
keep writing while we're going through
with presentations. So what I'd like to do

107
00:24:25,410 --> 00:24:33,030
now is hear from anybody who would like to
share some titles and pitches. You'll have

108
00:24:33,060 --> 00:24:38,160
about two minutes or less for a mini
presentation. There's no expectations;

109
00:24:38,190 --> 00:24:42,120
it's not a chance to practice being great.
It's just an opportunity to practice being

110
00:24:42,120 --> 00:24:47,940
in front of people. And you may request
proceeding feedback if you wish. And if

111
00:24:47,940 --> 00:24:56,310
you do, they'll be about time for a minute
of feedback. So would anybody like to

112
00:24:56,400 --> 00:25:09,600
share their pitch? Title and pitch?
Miriam? Don't feel guilty for being

113
00:25:09,690 --> 00:25:10,530
awesome.

114
00:25:12,910 --> 00:25:18,940
All right, so, my title is "The Big
Transition: Moving from an Office to a

115
00:25:18,940 --> 00:25:25,390
Remote Work Culture." And the pitch I have
is, "Traditionally people have gone to an

116
00:25:25,390 --> 00:25:30,070
office building for a typical nine to five
job. But more and more people, myself

117
00:25:30,070 --> 00:25:36,340
included, make the transition to remote,
whether it's by their choice or not. So

118
00:25:36,340 --> 00:25:40,870
find out about the successes and struggles
that this transition may cause and tips to

119
00:25:40,870 --> 00:25:42,430
help you flourish going forth."

120
00:25:44,650 --> 00:25:45,700
Would you like feedback?

121
00:25:46,000 --> 00:25:46,630
Yes, please.

122
00:25:47,140 --> 00:25:51,760
Awesome. That sounds great to me.
Everything was clear. It didn't leave me

123
00:25:51,760 --> 00:25:57,820
with any questions. I was clear of what
I'd be getting out of it. And it sounds

124
00:25:57,880 --> 00:26:04,060
pretty engaging to me. Does anybody else
have any other thoughts? And if you do,

125
00:26:04,060 --> 00:26:09,250
just to reminder that be sure to say
something that you liked about it before

126
00:26:09,250 --> 00:26:10,870
suggesting improvements.

127
00:26:14,830 --> 00:26:19,570
It's it's really clear medium, what the
topic is, and it's really nice.

128
00:26:22,420 --> 00:26:22,900
Thank you.

129
00:26:23,460 --> 00:26:26,130
I don't really have any edits. That was
really solid.

130
00:26:29,510 --> 00:26:38,780
Awesome. Okay, would anybody else like to
share theirs? Aurooba.

131
00:26:40,490 --> 00:26:48,680
Okay.And yes, I'm absolutely open to
feedback. The title is "Extending Existing

132
00:26:48,680 --> 00:26:56,210
Gutenberg blocks." And then the pitch is,
"Instead of creating entirely new blocks

133
00:26:56,210 --> 00:27:00,290
to add a few features, learn how to save
time by extending existing Gutenberg

134
00:27:00,290 --> 00:27:05,780
blocks. We'll cover basic JSX syntax, how
to create block variations, and how to add

135
00:27:05,780 --> 00:27:10,820
custom attributes and controls to any
block. This is intended for intermediate

136
00:27:10,820 --> 00:27:14,300
WordPress developers getting started with
native Gutenberg development."

137
00:27:15,410 --> 00:27:25,220
Awesome. Great. That, to me, also seems
super solid. I have nothing to add or

138
00:27:25,220 --> 00:27:29,990
change on it. It is very clear. I think
it's something that people are going to

139
00:27:29,990 --> 00:27:35,810
want to hear about. And like you said,
really well in the pitch, you know, kind

140
00:27:35,810 --> 00:27:41,060
of, you address the difference between
writing a whole new one and extending. So

141
00:27:41,060 --> 00:27:46,970
I really like that. Bhargav, are you
giving feedback or sharing yours?

142
00:27:48,800 --> 00:27:49,730
Sharing mine?

143
00:27:50,090 --> 00:27:54,110
Okay, well, I'm just gonna see if anybody
has feedback for Aurooba before

144
00:27:54,140 --> 00:28:01,850
continuing. Okay, I'm

145
00:28:02,050 --> 00:28:03,970
Also very clear, so excellent job.

146
00:28:07,810 --> 00:28:12,610
Awesome.Great work, everybody so far. All
right, Bhargav. Thanks for volunteering.

147
00:28:15,030 --> 00:28:22,140
"Try to lose career opportunity that I
grabbed." Title two like, I thought, "A

148
00:28:23,130 --> 00:28:28,080
journey of transformation from developer
to functional consultant: Challenges and

149
00:28:28,080 --> 00:28:35,580
Outcomes." That is the title. And the
pitch decks is, "In the current market

150
00:28:35,580 --> 00:28:41,700
scenario, everyone is trying to become a
developer. He also wanted to be one. But

151
00:28:41,700 --> 00:28:49,410
destiny had other options in favor, and he
wanted him to try other career options. To

152
00:28:49,410 --> 00:28:54,420
break the notion that 'once a developer is
always a developer,' he switched his

153
00:28:54,420 --> 00:29:00,810
career to become one which he was
comfortable with. And which given him more

154
00:29:01,110 --> 00:29:06,120
respect and reputation in the company.
Know his struggle and his journey of

155
00:29:06,120 --> 00:29:10,350
switching the career. Everyone who is
confused in choosing their career path

156
00:29:10,380 --> 00:29:11,610
must join this session."

157
00:29:14,190 --> 00:29:15,750
Thanks, would you like feedback?

158
00:29:16,470 --> 00:29:16,890
Yeah.

159
00:29:17,460 --> 00:29:20,280
Awesome. Does anybody have some feedback
to give?

160
00:29:24,570 --> 00:29:31,110
I vote for title number two. I thought
that was like more clear. And aside from

161
00:29:31,110 --> 00:29:38,430
that, maybe the pitch could be slightly
shorter, but I felt like it also covered

162
00:29:38,430 --> 00:29:44,310
everything. So maybe like some parts could
be shortened a little bit but otherwise,

163
00:29:44,310 --> 00:29:48,390
it was pretty solid. I kind of knew what I
would be getting in for.

164
00:29:50,070 --> 00:29:50,820
What else?

165
00:29:52,160 --> 00:29:55,790
I also vote for the second title. I think
that's much better.

166
00:29:57,200 --> 00:29:57,590
Awesome.

167
00:29:59,180 --> 00:30:00,560
Everything else sounds good.

168
00:30:07,400 --> 00:30:12,050
All right. Anybody else for feedback or
sharing their pitch?

169
00:30:17,070 --> 00:30:20,730
Mine is still a pretty rough draft. So I..

170
00:30:22,110 --> 00:30:23,070
Are you willing to share it?

171
00:30:26,040 --> 00:30:27,150
I'm not sure though.

172
00:30:27,870 --> 00:30:33,300
Okay. Angela?

173
00:30:34,530 --> 00:30:42,060
Yeah, I can share mine. So my title is
"Building WordPress: Tips for

174
00:30:42,060 --> 00:30:48,600
collaborating across time and space." And
the pitch is, "The WordPress open source

175
00:30:48,600 --> 00:30:53,730
project is built by a global diverse
community. If you've contributed in the

176
00:30:53,730 --> 00:30:58,350
past, perhaps something got lost in
translation. timezones made it impossible

177
00:30:58,350 --> 00:31:03,720
to connect. In this session, Angela will
share some tips for stronger global

178
00:31:03,720 --> 00:31:07,920
collaboration when it comes to
contributing to WordPress. She'll share

179
00:31:07,920 --> 00:31:12,300
personal stories where things didn't quite
go as planned, and how the global teams

180
00:31:12,300 --> 00:31:16,830
were still able to move forward, all in
the hope that you'll feel more prepared to

181
00:31:16,830 --> 00:31:20,550
collaborate asynchronously and with a
greater shared understanding."

182
00:31:21,690 --> 00:31:29,520
Awesome. Feedback?Are you willing? Great!
So the pitch is super solid. I...

183
00:31:30,510 --> 00:31:37,170
everything was clear. It sounded really
engaging to me. Can you repeat the title?

184
00:31:37,170 --> 00:31:39,210
For some reason? I did not hear it.

185
00:31:39,930 --> 00:31:45,630
I called it "Building WordPress: Tips for
collaborating across time and space."

186
00:31:48,030 --> 00:31:56,460
So I like it. But some refinements I would
suggest, I think "building WordPress"

187
00:31:56,490 --> 00:32:02,370
doesn't address the fact that we are
talking about the distributed part. And

188
00:32:02,370 --> 00:32:05,670
the the part about "across time and
space." I mean, I'm always thinking

189
00:32:05,700 --> 00:32:11,400
"Doctor Who". And also I think I'm not
really clear from the title, like, from

190
00:32:11,400 --> 00:32:15,570
the pitch its totally clear what it is.
And from the title, I don't quite get it.

191
00:32:15,840 --> 00:32:21,210
I think I might use some of the words from
the pitch in your title instead.

192
00:32:23,190 --> 00:32:28,890
I'm struggling to... I feel like my...
what I want to put into this talk is too

193
00:32:28,890 --> 00:32:31,170
broad so I really would like to condense
more.

194
00:32:31,290 --> 00:32:35,820
Okay, yeah. Um, is that something you want
help with now? Or do you want to just work

195
00:32:35,820 --> 00:32:37,980
on that before our session tomorrow?

196
00:32:38,490 --> 00:32:41,430
Oh, nope. Not now. My time is expired.

197
00:32:41,750 --> 00:32:48,470
We have we have an extra minute or two.
But yeah. Great. Yeah. So yeah, I think

198
00:32:48,470 --> 00:32:51,380
you're really onto it. And I think it's
just the title just needs a bit of

199
00:32:51,380 --> 00:32:54,860
tweaking, or like you said it could be
reining in the whole thing in a bit. But

200
00:32:54,860 --> 00:32:59,120
from the description itself, it sounded
that part sounds fine to me.

201
00:33:00,440 --> 00:33:07,640
I have a question. So can I work on mine?
And do we have time to go over that

202
00:33:07,640 --> 00:33:08,780
tomorrow? Or...?

203
00:33:08,810 --> 00:33:12,350
Yeah, we absolutely could go over them
again tomorrow.

204
00:33:13,220 --> 00:33:13,670
Okay.

205
00:33:14,750 --> 00:33:20,390
In our last few minutes, I'd actually love
to hear bios from anybody who had the time

206
00:33:20,390 --> 00:33:27,380
and wants to share theirs. I'll let
Aurooba go first, and then Miriam, and

207
00:33:27,380 --> 00:33:31,160
then Bhargav. It'll be about a minute each
and we'll see if we have time to get

208
00:33:31,160 --> 00:33:31,760
through everybody.

209
00:33:33,590 --> 00:33:37,820
Okay, I am terrible at bios and I hate
writing them and every single time I have

210
00:33:37,820 --> 00:33:40,490
to write them I want to kill myself a
little bit.

211
00:33:40,520 --> 00:33:42,050
Thank doing it today!

212
00:33:43,080 --> 00:33:48,450
No, but that I need help. So any feedback
you guys give, you folks give, that will

213
00:33:48,450 --> 00:33:53,550
be helpful. "Aurooba was the co founder of
design and development studio Wanderoak.

214
00:33:53,580 --> 00:33:58,800
She has been developing bespoke WordPress
solutions for five plus years and is

215
00:33:58,800 --> 00:34:02,490
currently writing a course on WordPress
theme development. She's the co-organizer

216
00:34:02,520 --> 00:34:06,180
of the Calgary WordPress meetup and has
been helping organize WordCamp Calgary for

217
00:34:06,180 --> 00:34:09,660
three years. She loves putting together
dinner parties and getting lost in a

218
00:34:09,660 --> 00:34:13,320
really good book." This is the longest bio
I've ever written in my life and all I can

219
00:34:13,320 --> 00:34:15,720
think is, like "Oh my God, this is too
braggy."

220
00:34:17,370 --> 00:34:25,650
I love it. I have no changes. It is
succinct. It's really clear. It's

221
00:34:25,650 --> 00:34:33,360
friendly. It's... Ship it, in my opinion.
And I'm seeing Angela's nodding. Any any

222
00:34:33,360 --> 00:34:38,010
other thoughts on that? Everyone is
nodding. Does anybody have any changes to

223
00:34:38,010 --> 00:34:43,530
suggest? We all love it. Ship it! Good
work!

224
00:34:43,770 --> 00:34:49,530
Is it maybe like too many things to say or
no? No,

225
00:34:49,560 --> 00:34:53,520
I don't know. I don't think so either. It.
It sounds good.

226
00:34:53,750 --> 00:34:59,330
It felt like the right length. It didn't
feel like you're going on and on. A lot of

227
00:34:59,330 --> 00:35:04,400
people put a lot of stuff in their bio,
but I felt like it was, you know, economy

228
00:35:04,400 --> 00:35:07,730
of words, not too many sentences. It just
covered everything.

229
00:35:08,300 --> 00:35:10,760
Okay. Thank you. I always also feel
nervous.

230
00:35:10,760 --> 00:35:17,240
Bios need to be a bit braggy which is one
of those things that folks from

231
00:35:17,240 --> 00:35:21,170
underrepresented groups tend to not like
to do that as much. There's a bit of

232
00:35:21,170 --> 00:35:27,200
conditioning in the world around that. And
the over represented population tends, not

233
00:35:27,200 --> 00:35:32,210
always, but in general tends to be more
okay with it. So it's a great opportunity

234
00:35:32,210 --> 00:35:37,970
to practice leaning into that, and owning
some of the awesome shit you've done.

235
00:35:40,070 --> 00:35:41,060
Fair enough.

236
00:35:43,250 --> 00:35:48,920
We have time for maybe one or two more,
probably one. Miriam was next.

237
00:35:54,570 --> 00:35:59,880
I decided to write a totally new bio other
the one I've been using, so we'll see how

238
00:35:59,880 --> 00:36:06,780
well this one is. So, "Miriam is a web
developer with 15 years experience and

239
00:36:06,780 --> 00:36:09,960
currently works for Pondstone Digital
marketing. She's been working with

240
00:36:09,960 --> 00:36:14,730
WordPress since 2008 and fell in love with
the community in 2016. Passionate about

241
00:36:14,730 --> 00:36:18,930
giving back, she's an organizer for both
the Ottawa WordPress meetup and WordCamp

242
00:36:18,960 --> 00:36:24,180
Ottawa. When not in front of a computer,
Miriam is either a karate sensei, ballroom

243
00:36:24,180 --> 00:36:27,960
dancer, or clarinetist, just not all at
once, but she's working on it.

244
00:36:31,050 --> 00:36:33,600
Awesome. Feedback? Open to it?

245
00:36:34,200 --> 00:36:35,190
Oh, you always,

246
00:36:35,700 --> 00:36:44,370
Always. Um, again, it is super clear,
succinct. I am friendly. I liked it. My

247
00:36:44,370 --> 00:36:48,570
only feedback is you didn't mention your
work in our group. And I want you to

248
00:36:48,570 --> 00:36:50,190
always mention our group,

249
00:36:50,750 --> 00:36:56,210
I didn't know. I have that written down.
"And she is also involved with the diverse

250
00:36:56,210 --> 00:37:00,260
speaker training group as
between-the-trainers lead." Yeah, I think

251
00:37:00,260 --> 00:37:03,590
maybe that's a bit too wordy. Maybe I'll
just say "she's involved with the diverse

252
00:37:03,590 --> 00:37:06,050
speakers training group."

253
00:37:08,090 --> 00:37:10,940
That or saying "a leadership position."

254
00:37:11,020 --> 00:37:15,010
Leadership position. Yeah. Instead of
going specific? Yeah.

255
00:37:15,390 --> 00:37:19,110
I just want you to be mentioning it.
Because anytime you're speaking, we'll

256
00:37:19,110 --> 00:37:23,640
have at least one spot to have a shout out
and get our name out there.

257
00:37:24,080 --> 00:37:26,330
Now, I mentioned it in Niagara last
weekend.

258
00:37:26,360 --> 00:37:32,180
Yes. Any other comments for Miriam?

259
00:37:34,610 --> 00:37:35,300
That's good.

260
00:37:37,940 --> 00:37:40,910
Great! I'm sorry, Angela?

261
00:37:41,770 --> 00:37:51,790
I agree. It's great. And I think.. add a
little bit, a little bit more to your

262
00:37:51,790 --> 00:37:56,560
experience, because you say you have like
15 years of experience as a web developer

263
00:37:57,220 --> 00:38:01,150
but you didn't specify like one
experience. You can add, you can add a

264
00:38:01,150 --> 00:38:05,620
little more in there. It's 15 years,
you've got a lot to share.

265
00:38:11,390 --> 00:38:16,220
Okay, so where we left off in our session
was Bhargav was going to share his bio.

266
00:38:16,250 --> 00:38:17,270
Did you still want to do that?

267
00:38:20,159 --> 00:38:25,439
Yes. We'll proceed with it. Just Yes.

268
00:38:26,520 --> 00:38:27,030
Great.

269
00:38:27,120 --> 00:38:28,590
So should I stand?

270
00:38:29,070 --> 00:38:31,350
Yes. Thanks.

271
00:38:33,460 --> 00:38:39,520
I'm currently working as a functional
consultant at KrishaWeb. Ecommerce

272
00:38:39,520 --> 00:38:47,170
increases my dopamine levels. He says
humming to the melodies of A.R. Rahman is

273
00:38:47,830 --> 00:38:53,350
his full time job. Expanding the horizons
of knowledge by reading is what people

274
00:38:53,350 --> 00:38:57,970
will always find him doing. Bhargav is a
co-organizer for the Ahmedabad WordPress

275
00:38:57,970 --> 00:38:59,470
meetup and also WordCamp.

276
00:39:01,640 --> 00:39:04,760
Nice! I think... did you want feedback?

277
00:39:08,810 --> 00:39:09,710
Yes

278
00:39:10,290 --> 00:39:14,220
Awesome. I thought you had some really
good points in there. It illustrated a lot

279
00:39:14,220 --> 00:39:18,240
of, you know, what you do and a little bit
of your personality. And I think probably

280
00:39:18,240 --> 00:39:23,160
just tightening it up a bit. Maybe
starting with some of your big roles and

281
00:39:23,160 --> 00:39:30,480
just saying just a little bit. Probably.
It'll depend a bit on where you're

282
00:39:30,480 --> 00:39:36,090
submitting the bio to. Some of them can be
more and a little bit more playful and

283
00:39:36,090 --> 00:39:44,700
some of them should be really short and
tight. Any other thoughts? Aurooba!

284
00:39:44,480 --> 00:39:50,150
I love the reference to A.R. Rahman. I
would like to see maybe another sentence

285
00:39:50,150 --> 00:39:57,470
about your work. Just to make it a little
more balanced. I I felt had the feeling

286
00:39:57,470 --> 00:40:03,080
that it's the doesn't really share a lot
about your experience as much. So maybe

287
00:40:03,080 --> 00:40:06,260
another sentence about that might help but
otherwise really good.

288
00:40:10,100 --> 00:40:17,180
Anyone else? Great, thanks very much
Bhargav. And Chandrika, did you work on

289
00:40:17,180 --> 00:40:19,340
your pitch and want to share it with us?

290
00:40:24,080 --> 00:40:28,700
Okay, my pitch is not ready yet, I tried
to work on it yesterday, but I just

291
00:40:28,700 --> 00:40:36,290
couldn't get it. I just don't like it. So
I think it's, I know what I want to say,

292
00:40:36,290 --> 00:40:38,990
but I just can't put it in words yet. So,

293
00:40:39,059 --> 00:40:44,249
okay. Yeah. If you want it to run it past
us now or another time of whatever you

294
00:40:44,249 --> 00:40:46,889
have currently, that's totally fine. And
otherwise,

295
00:40:47,860 --> 00:41:02,890
I could do it. What I have now but it's...
I really don't like it. Okay, so the title

296
00:41:02,890 --> 00:41:14,440
is "Building custom WordPress sites with
ACF blocks." Um, "ACF provides an easy way

297
00:41:14,440 --> 00:41:18,790
to build custom functionalities and
templates in WordPress sites. Combining

298
00:41:18,790 --> 00:41:24,850
this with Gutenberg gives more power to
the users, your clients. This talk is

299
00:41:24,850 --> 00:41:28,690
geared towards beginner developers who
build custom WordPress sites for their

300
00:41:28,690 --> 00:41:35,740
clients. You'll learn how to build ACF
blocks and how these blocks can be used on

301
00:41:35,740 --> 00:41:37,540
multiple sites in different ways."

302
00:41:38,770 --> 00:41:42,790
Nice. Did you want  thoughts from us once?
Are you done?

303
00:41:43,180 --> 00:41:45,340
No, no, I was done. I was done. I'm done.

304
00:41:45,660 --> 00:41:45,990
Awesome

305
00:41:45,990 --> 00:41:47,760
It's early. I would love to get feedback.

306
00:41:47,970 --> 00:41:54,150
Great. I loved the last few sentences. I
loved the like, where you specified what

307
00:41:54,150 --> 00:41:58,800
people are getting out of it and who the
talk is for and all those things. And

308
00:41:58,800 --> 00:42:01,680
yeah, I think just working on that first
part, but you already said it was kind of

309
00:42:01,680 --> 00:42:13,110
rough. Yeah. Maybe something around? I'm
not sure right now. It's kind of tough.

310
00:42:13,140 --> 00:42:14,670
Does anybody else have thoughts on that?

311
00:42:14,480 --> 00:42:17,660
It looks like Aurooba does.

312
00:42:19,130 --> 00:42:19,730
Oh, sorry.

313
00:42:23,600 --> 00:42:31,550
I think that maybe including who it's for?
Something about who it's for in the first

314
00:42:31,550 --> 00:42:36,860
part will help. And the other thing I
would probably personally suggest is

315
00:42:36,860 --> 00:42:41,240
mentioning that it's ACF Pro, because you
can't build blocks with the free version

316
00:42:41,240 --> 00:42:41,540
way.

317
00:42:41,780 --> 00:42:47,600
Okay. Sure. Thank you.

318
00:42:48,830 --> 00:42:54,470
I will look forward to hearing the rest of
that when it's done. Does anybody else

319
00:42:54,470 --> 00:42:58,220
have anything they wanted to cover before
we move on to section number four?