0:00:01.050,0:00:13.110
So now we're going to go into writing your[br]pitch. Okay, so in this section, we are

0:00:13.110,0:00:18.990
going to talk about what a proposal AKA[br]pitch is, coming up with a great title,

0:00:19.050,0:00:24.510
and a little writing exercise. That's[br]actually switched around... Writing your

0:00:24.510,0:00:35.970
bio, writing exercise, and then optionally[br]anybody who wants to present their titles

0:00:36.000,0:00:45.420
into pitches. Okay, so, whatever your[br]motivation is for speaking, you first need

0:00:45.420,0:00:50.070
to get selected to speak. And for that,[br]you need to create a proposal or pitch.

0:00:50.400,0:00:54.870
And we'll use those terms interchangeably.[br]And one will that will get your talk

0:00:54.870,0:01:00.000
selected. And also, since your proposal[br]defines the scope of your talk, it can be

0:01:00.030,0:01:03.750
a good early step in the overall process[br]of developing your talk.

0:01:04.710,0:01:11.730
What makes a great pitch? So first, here's[br]an example of a good one. Responsify all

0:01:11.730,0:01:16.050
the Things. In our new web multiverse,[br]it's more important than ever to make your

0:01:16.050,0:01:20.400
valuable content available to all users,[br]regardless of how they access your site.

0:01:20.940,0:01:27.540
In this talk, we'll cover how responsive[br]web design came about, the latest RWD news

0:01:27.540,0:01:31.680
and trends, and some basic and not so[br]basic techniques you can use to make your

0:01:31.680,0:01:36.330
next WordPress theme a responsive one.[br]Intended for developers and designers who

0:01:36.330,0:01:39.180
aren't afraid to get their hands dirty[br]with a little code.

0:01:42.180,0:01:49.470
So this is a good length. It tells you[br]what the talk will cover and it tells you

0:01:49.470,0:01:53.670
who it's aimed at. In some cases, you[br]might also want to say what people will

0:01:53.670,0:02:01.410
walk away with from this talk. On the[br]topic of the title, beware of too clever

0:02:01.410,0:02:06.390
titles. The title should stand on its own[br]without a blurb. Here's an example of a

0:02:06.390,0:02:14.820
bad one, "CSS dreams and elephants." What[br]do you think makes this a good or bad

0:02:14.850,0:02:20.820
title? And this is a question for[br]discussion right now. Aurooba?

0:02:20.940,0:02:25.350
It doesn't really tell me what I will be[br]getting out of this talk.

0:02:25.570,0:02:30.460
Right? So in that title we have no idea[br]what it's about, what you'll be getting

0:02:30.490,0:02:39.700
out of it. Anyone else have anything to[br]add? Okay, great. Yeah, that's pretty much

0:02:39.700,0:02:43.450
it. That's, it's it's a cute title, but it[br]is too vague.

0:02:47.290,0:02:51.190
Generally, your talk proposal and the[br]introduction of your outline will be quite

0:02:51.190,0:02:56.860
similar. A good introduction should have[br]all the things a good pitch would have.

0:02:57.220,0:03:01.570
However, in a pitch, you might want to[br]spice it up a bit. Ultimately, both the

0:03:01.570,0:03:09.550
introduction and pitch should contain some[br]more content. For a pitch, you want to

0:03:09.550,0:03:13.120
tailor the tone of your writing and[br]vocabulary to the specific audience and

0:03:13.120,0:03:17.920
event that you're applying to. This is[br]very important. Some ideas of how you may

0:03:17.920,0:03:22.780
tailor your pitch for specific audiences[br]and events: The tone may be different. A

0:03:22.780,0:03:27.700
business crowd may be formal, a Meetup may[br]be more casual, so customize the tone of

0:03:27.700,0:03:32.200
your pitch to your specific audience. At[br]WordPress events, in general, we tend to

0:03:32.200,0:03:37.180
be pretty casual. You might want to use[br]different vocabulary depending on the

0:03:37.180,0:03:41.890
audience. And you might want to stress[br]different talks or points of interest

0:03:41.920,0:03:43.780
depending on the audience or event.

0:03:45.910,0:03:51.070
There are six important points to take[br]note of when writing both your outline and

0:03:51.070,0:03:54.730
your pitch. And this comes from the site[br]that is written on the screen:

0:03:56.740,0:04:06.670
weareallaweso.me/for_speakers/how-to-write-a-compelling-proposal.html.[br]Point number one: Direct the proposal to

0:04:06.670,0:04:12.760
the attendees, not the curators. Many[br]conferences use your talk proposal as the

0:04:12.760,0:04:17.770
description of the talk in their program.[br]With that in mind, your target reader is

0:04:17.770,0:04:22.090
the conference attendee who is reading the[br]program. Tell the reader why your talk

0:04:22.090,0:04:26.260
will interest them and what they will[br]learn. The curators want to put together a

0:04:26.260,0:04:30.610
great conference with compelling talks for[br]their attendees. The talk will be part of

0:04:30.610,0:04:35.200
the package they offer so sell it! Make[br]sure you research the event. Are there

0:04:35.200,0:04:39.430
different tracks? Is the audience. Are[br]there lots of devs? Is it mostly for

0:04:39.430,0:04:44.890
users? Is it design heavy? Different[br]WordCamps have different personalities.

0:04:45.130,0:04:48.520
Are they short on really technical[br]presentations? Light on talks for

0:04:48.520,0:04:52.120
beginners? Try to fill a need, such as[br]podcasting.

0:04:54.250,0:04:59.560
Number two: Be specific about the focus[br]that your talk will have. Generally

0:04:59.560,0:05:03.790
speaking, a shallow introduction to many[br]things is not as interesting as an in

0:05:03.790,0:05:08.620
depth introduction to one thing. If you[br]discuss the broader topic, do so only to

0:05:08.620,0:05:10.660
set the context for what you'll focus on.

0:05:13.150,0:05:18.880
Number three: One strategy is pose the[br]question that your talk will answer. Often

0:05:18.880,0:05:24.580
talks answer questions that start with[br]how, why, when, and so on. An easy trick

0:05:24.580,0:05:28.870
is to directly ask these questions in your[br]proposal, leaving the reader wondering the

0:05:28.870,0:05:29.320
answer.

0:05:29.290,0:05:36.070
Number four: Make your point as simply as[br]you can. If your first draft requires more

0:05:36.070,0:05:41.620
than two paragraphs to get to the point of[br]your topic, edit to narrow things down.

0:05:42.130,0:05:46.330
Take out any words that can be removed[br]without changing the meaning. You may have

0:05:46.330,0:05:50.950
a lot of competition so try to make a good[br]impression quickly. If your proposal is

0:05:50.950,0:05:54.670
too much work to read or understand, i[br]might get skipped during the selectio

0:05:54.670,0:06:03.040
process.

0:06:01.130,0:06:06.920
Number five: Use proper grammar, spelling,[br]and punctuation. If you submit a sloppily

0:06:06.920,0:06:10.880
written proposal, you appear careless and[br]as if you're not taking the opportunity

0:06:10.880,0:06:15.650
seriously. You risk being rejected on[br]those grounds outright. Speaking requires

0:06:15.650,0:06:19.160
a lot of thoughtful preparation, and[br]curators can only assume it will be as

0:06:19.160,0:06:21.470
careless when preparing the talk itself.

0:06:23.070,0:06:27.900
And number six: Have your proposal[br]reviewed by someone with experience. Just

0:06:27.900,0:06:32.160
as you might ask a friend to critique a[br]draft of your CV, an essay or the talk

0:06:32.160,0:06:37.140
itself, ask someone, ideally a writer,[br]speaker or curator to review your talk

0:06:37.140,0:06:41.850
proposal. They'll catch typos as well as[br]verify whether your proposal explains the

0:06:41.850,0:06:45.690
scope of your talk, and explains its[br]benefits to your audience.

0:06:48.030,0:06:52.620
Next, we're going to talk about coming up[br]with a great title. We need a good title

0:06:52.620,0:06:57.480
for your talk. You're going to want to try[br]to think of something catchy but

0:06:57.480,0:07:02.970
explanatory. Be aware of too clever titles[br]and create a title that can stand on its

0:07:02.970,0:07:07.260
own without a blurb. For example, don't[br]use something like "CSS and Elephants."

0:07:09.300,0:07:14.760
We're also going to talk right now about[br]writing your bio. When you submit a

0:07:14.760,0:07:19.890
proposal or pitch to an event, you'll most[br]often be asked to include a short bio.

0:07:20.370,0:07:24.990
Bios are often the hardest to write well,[br]but here are some pointers to follow. It

0:07:24.990,0:07:26.580
should be written in the third person.

0:07:27.980,0:07:32.720
It should be succinct, but descriptive. It[br]should only be a short paragraph and go

0:07:32.720,0:07:37.430
for economy of words. Try to say the most[br]you possibly can with the fewest possible

0:07:37.430,0:07:42.590
words. Mention what your position or job[br]is, and include any credentials that might

0:07:42.590,0:07:47.150
be relevant. Mention how many years you've[br]been in this field, or if it hasn't been

0:07:47.150,0:07:51.860
that many, tell a short story about how[br]you've ended up in your new field. Look at

0:07:51.860,0:07:55.700
past examples for the conference you're[br]submitting to. Why are you the right

0:07:55.700,0:08:00.500
person to give this talk and tailor your[br]bio so your topic makes sense. You might

0:08:00.500,0:08:05.570
want to tweak it differently for different[br]topics and different events. Be human.

0:08:05.870,0:08:10.940
WordCamps are usually not too formal. And[br]feel free to add something about your non

0:08:10.940,0:08:14.150
professional interests at the end, but[br]don't make it your entire bio.

0:08:15.320,0:08:19.580
So what we're going to do now is we're[br]going to have 15 minutes to try drafting a

0:08:19.580,0:08:23.870
talk proposal for the idea that you[br]brainstormed earlier, the title, and your

0:08:23.870,0:08:27.770
bio, There'll be a chance to read the[br]title and pitch to the group after if you

0:08:27.770,0:08:31.610
wish. We'll see if we have time for[br]reading it to each other today or that'll

0:08:31.610,0:08:38.570
be part of tomorrow's session. But let's[br]go ahead and do the 15 minutes. If you

0:08:38.570,0:08:43.190
need me to flip back and forth between any[br]of the slides, you can write that in the

0:08:43.190,0:08:49.340
chat; I'll watch for that. I'll also grab[br]a link from our Slack. I put the link to

0:08:49.340,0:08:52.940
the slides if you want to grab them and be[br]able to refer to those sections because

0:08:52.940,0:08:58.040
we're working on three things at once[br]right now. So go ahead and start that. If

0:08:58.040,0:09:03.080
you've any questions about it, put it into[br]the chat. I'll check that as well. So I'm

0:09:03.080,0:09:06.290
going to go ahead and start 15 minutes.

0:23:43.920,0:24:19.290
There's about 30 seconds left. All right.[br]If anyone needs more time, you can always

0:24:19.290,0:24:25.410
keep writing while we're going through[br]with presentations. So what I'd like to do

0:24:25.410,0:24:33.030
now is hear from anybody who would like to[br]share some titles and pitches. You'll have

0:24:33.060,0:24:38.160
about two minutes or less for a mini[br]presentation. There's no expectations;

0:24:38.190,0:24:42.120
it's not a chance to practice being great.[br]It's just an opportunity to practice being

0:24:42.120,0:24:47.940
in front of people. And you may request[br]proceeding feedback if you wish. And if

0:24:47.940,0:24:56.310
you do, they'll be about time for a minute[br]of feedback. So would anybody like to

0:24:56.400,0:25:09.600
share their pitch? Title and pitch?[br]Miriam? Don't feel guilty for being

0:25:09.690,0:25:10.530
awesome.

0:25:12.910,0:25:18.940
All right, so, my title is "The Big[br]Transition: Moving from an Office to a

0:25:18.940,0:25:25.390
Remote Work Culture." And the pitch I have[br]is, "Traditionally people have gone to an

0:25:25.390,0:25:30.070
office building for a typical nine to five[br]job. But more and more people, myself

0:25:30.070,0:25:36.340
included, make the transition to remote,[br]whether it's by their choice or not. So

0:25:36.340,0:25:40.870
find out about the successes and struggles[br]that this transition may cause and tips to

0:25:40.870,0:25:42.430
help you flourish going forth."

0:25:44.650,0:25:45.700
Would you like feedback?

0:25:46.000,0:25:46.630
Yes, please.

0:25:47.140,0:25:51.760
Awesome. That sounds great to me.[br]Everything was clear. It didn't leave me

0:25:51.760,0:25:57.820
with any questions. I was clear of what[br]I'd be getting out of it. And it sounds

0:25:57.880,0:26:04.060
pretty engaging to me. Does anybody else[br]have any other thoughts? And if you do,

0:26:04.060,0:26:09.250
just to reminder that be sure to say[br]something that you liked about it before

0:26:09.250,0:26:10.870
suggesting improvements.

0:26:14.830,0:26:19.570
It's it's really clear medium, what the[br]topic is, and it's really nice.

0:26:22.420,0:26:22.900
Thank you.

0:26:23.460,0:26:26.130
I don't really have any edits. That was[br]really solid.

0:26:29.510,0:26:38.780
Awesome. Okay, would anybody else like to[br]share theirs? Aurooba.

0:26:40.490,0:26:48.680
Okay.And yes, I'm absolutely open to[br]feedback. The title is "Extending Existing

0:26:48.680,0:26:56.210
Gutenberg blocks." And then the pitch is,[br]"Instead of creating entirely new blocks

0:26:56.210,0:27:00.290
to add a few features, learn how to save[br]time by extending existing Gutenberg

0:27:00.290,0:27:05.780
blocks. We'll cover basic JSX syntax, how[br]to create block variations, and how to add

0:27:05.780,0:27:10.820
custom attributes and controls to any[br]block. This is intended for intermediate

0:27:10.820,0:27:14.300
WordPress developers getting started with[br]native Gutenberg development."

0:27:15.410,0:27:25.220
Awesome. Great. That, to me, also seems[br]super solid. I have nothing to add or

0:27:25.220,0:27:29.990
change on it. It is very clear. I think[br]it's something that people are going to

0:27:29.990,0:27:35.810
want to hear about. And like you said,[br]really well in the pitch, you know, kind

0:27:35.810,0:27:41.060
of, you address the difference between[br]writing a whole new one and extending. So

0:27:41.060,0:27:46.970
I really like that. Bhargav, are you[br]giving feedback or sharing yours?

0:27:48.800,0:27:49.730
Sharing mine?

0:27:50.090,0:27:54.110
Okay, well, I'm just gonna see if anybody[br]has feedback for Aurooba before

0:27:54.140,0:28:01.850
continuing. Okay, I'm

0:28:02.050,0:28:03.970
Also very clear, so excellent job.

0:28:07.810,0:28:12.610
Awesome.Great work, everybody so far. All[br]right, Bhargav. Thanks for volunteering.

0:28:15.030,0:28:22.140
"Try to lose career opportunity that I[br]grabbed." Title two like, I thought, "A

0:28:23.130,0:28:28.080
journey of transformation from developer[br]to functional consultant: Challenges and

0:28:28.080,0:28:35.580
Outcomes." That is the title. And the[br]pitch decks is, "In the current market

0:28:35.580,0:28:41.700
scenario, everyone is trying to become a[br]developer. He also wanted to be one. But

0:28:41.700,0:28:49.410
destiny had other options in favor, and he[br]wanted him to try other career options. To

0:28:49.410,0:28:54.420
break the notion that 'once a developer is[br]always a developer,' he switched his

0:28:54.420,0:29:00.810
career to become one which he was[br]comfortable with. And which given him more

0:29:01.110,0:29:06.120
respect and reputation in the company.[br]Know his struggle and his journey of

0:29:06.120,0:29:10.350
switching the career. Everyone who is[br]confused in choosing their career path

0:29:10.380,0:29:11.610
must join this session."

0:29:14.190,0:29:15.750
Thanks, would you like feedback?

0:29:16.470,0:29:16.890
Yeah.

0:29:17.460,0:29:20.280
Awesome. Does anybody have some feedback[br]to give?

0:29:24.570,0:29:31.110
I vote for title number two. I thought[br]that was like more clear. And aside from

0:29:31.110,0:29:38.430
that, maybe the pitch could be slightly[br]shorter, but I felt like it also covered

0:29:38.430,0:29:44.310
everything. So maybe like some parts could[br]be shortened a little bit but otherwise,

0:29:44.310,0:29:48.390
it was pretty solid. I kind of knew what I[br]would be getting in for.

0:29:50.070,0:29:50.820
What else?

0:29:52.160,0:29:55.790
I also vote for the second title. I think[br]that's much better.

0:29:57.200,0:29:57.590
Awesome.

0:29:59.180,0:30:00.560
Everything else sounds good.

0:30:07.400,0:30:12.050
All right. Anybody else for feedback or[br]sharing their pitch?

0:30:17.070,0:30:20.730
Mine is still a pretty rough draft. So I..

0:30:22.110,0:30:23.070
Are you willing to share it?

0:30:26.040,0:30:27.150
I'm not sure though.

0:30:27.870,0:30:33.300
Okay. Angela?

0:30:34.530,0:30:42.060
Yeah, I can share mine. So my title is[br]"Building WordPress: Tips for

0:30:42.060,0:30:48.600
collaborating across time and space." And[br]the pitch is, "The WordPress open source

0:30:48.600,0:30:53.730
project is built by a global diverse[br]community. If you've contributed in the

0:30:53.730,0:30:58.350
past, perhaps something got lost in[br]translation. timezones made it impossible

0:30:58.350,0:31:03.720
to connect. In this session, Angela will[br]share some tips for stronger global

0:31:03.720,0:31:07.920
collaboration when it comes to[br]contributing to WordPress. She'll share

0:31:07.920,0:31:12.300
personal stories where things didn't quite[br]go as planned, and how the global teams

0:31:12.300,0:31:16.830
were still able to move forward, all in[br]the hope that you'll feel more prepared to

0:31:16.830,0:31:20.550
collaborate asynchronously and with a[br]greater shared understanding."

0:31:21.690,0:31:29.520
Awesome. Feedback?Are you willing? Great![br]So the pitch is super solid. I...

0:31:30.510,0:31:37.170
everything was clear. It sounded really[br]engaging to me. Can you repeat the title?

0:31:37.170,0:31:39.210
For some reason? I did not hear it.

0:31:39.930,0:31:45.630
I called it "Building WordPress: Tips for[br]collaborating across time and space."

0:31:48.030,0:31:56.460
So I like it. But some refinements I would[br]suggest, I think "building WordPress"

0:31:56.490,0:32:02.370
doesn't address the fact that we are[br]talking about the distributed part. And

0:32:02.370,0:32:05.670
the the part about "across time and[br]space." I mean, I'm always thinking

0:32:05.700,0:32:11.400
"Doctor Who". And also I think I'm not[br]really clear from the title, like, from

0:32:11.400,0:32:15.570
the pitch its totally clear what it is.[br]And from the title, I don't quite get it.

0:32:15.840,0:32:21.210
I think I might use some of the words from[br]the pitch in your title instead.

0:32:23.190,0:32:28.890
I'm struggling to... I feel like my...[br]what I want to put into this talk is too

0:32:28.890,0:32:31.170
broad so I really would like to condense[br]more.

0:32:31.290,0:32:35.820
Okay, yeah. Um, is that something you want[br]help with now? Or do you want to just work

0:32:35.820,0:32:37.980
on that before our session tomorrow?

0:32:38.490,0:32:41.430
Oh, nope. Not now. My time is expired.

0:32:41.750,0:32:48.470
We have we have an extra minute or two.[br]But yeah. Great. Yeah. So yeah, I think

0:32:48.470,0:32:51.380
you're really onto it. And I think it's[br]just the title just needs a bit of

0:32:51.380,0:32:54.860
tweaking, or like you said it could be[br]reining in the whole thing in a bit. But

0:32:54.860,0:32:59.120
from the description itself, it sounded[br]that part sounds fine to me.

0:33:00.440,0:33:07.640
I have a question. So can I work on mine?[br]And do we have time to go over that

0:33:07.640,0:33:08.780
tomorrow? Or...?

0:33:08.810,0:33:12.350
Yeah, we absolutely could go over them[br]again tomorrow.

0:33:13.220,0:33:13.670
Okay.

0:33:14.750,0:33:20.390
In our last few minutes, I'd actually love[br]to hear bios from anybody who had the time

0:33:20.390,0:33:27.380
and wants to share theirs. I'll let[br]Aurooba go first, and then Miriam, and

0:33:27.380,0:33:31.160
then Bhargav. It'll be about a minute each[br]and we'll see if we have time to get

0:33:31.160,0:33:31.760
through everybody.

0:33:33.590,0:33:37.820
Okay, I am terrible at bios and I hate[br]writing them and every single time I have

0:33:37.820,0:33:40.490
to write them I want to kill myself a[br]little bit.

0:33:40.520,0:33:42.050
Thank doing it today!

0:33:43.080,0:33:48.450
No, but that I need help. So any feedback[br]you guys give, you folks give, that will

0:33:48.450,0:33:53.550
be helpful. "Aurooba was the co founder of[br]design and development studio Wanderoak.

0:33:53.580,0:33:58.800
She has been developing bespoke WordPress[br]solutions for five plus years and is

0:33:58.800,0:34:02.490
currently writing a course on WordPress[br]theme development. She's the co-organizer

0:34:02.520,0:34:06.180
of the Calgary WordPress meetup and has[br]been helping organize WordCamp Calgary for

0:34:06.180,0:34:09.660
three years. She loves putting together[br]dinner parties and getting lost in a

0:34:09.660,0:34:13.320
really good book." This is the longest bio[br]I've ever written in my life and all I can

0:34:13.320,0:34:15.720
think is, like "Oh my God, this is too[br]braggy."

0:34:17.370,0:34:25.650
I love it. I have no changes. It is[br]succinct. It's really clear. It's

0:34:25.650,0:34:33.360
friendly. It's... Ship it, in my opinion.[br]And I'm seeing Angela's nodding. Any any

0:34:33.360,0:34:38.010
other thoughts on that? Everyone is[br]nodding. Does anybody have any changes to

0:34:38.010,0:34:43.530
suggest? We all love it. Ship it! Good[br]work!

0:34:43.770,0:34:49.530
Is it maybe like too many things to say or[br]no? No,

0:34:49.560,0:34:53.520
I don't know. I don't think so either. It.[br]It sounds good.

0:34:53.750,0:34:59.330
It felt like the right length. It didn't[br]feel like you're going on and on. A lot of

0:34:59.330,0:35:04.400
people put a lot of stuff in their bio,[br]but I felt like it was, you know, economy

0:35:04.400,0:35:07.730
of words, not too many sentences. It just[br]covered everything.

0:35:08.300,0:35:10.760
Okay. Thank you. I always also feel[br]nervous.

0:35:10.760,0:35:17.240
Bios need to be a bit braggy which is one[br]of those things that folks from

0:35:17.240,0:35:21.170
underrepresented groups tend to not like[br]to do that as much. There's a bit of

0:35:21.170,0:35:27.200
conditioning in the world around that. And[br]the over represented population tends, not

0:35:27.200,0:35:32.210
always, but in general tends to be more[br]okay with it. So it's a great opportunity

0:35:32.210,0:35:37.970
to practice leaning into that, and owning[br]some of the awesome shit you've done.

0:35:40.070,0:35:41.060
Fair enough.

0:35:43.250,0:35:48.920
We have time for maybe one or two more,[br]probably one. Miriam was next.

0:35:54.570,0:35:59.880
I decided to write a totally new bio other[br]the one I've been using, so we'll see how

0:35:59.880,0:36:06.780
well this one is. So, "Miriam is a web[br]developer with 15 years experience and

0:36:06.780,0:36:09.960
currently works for Pondstone Digital[br]marketing. She's been working with

0:36:09.960,0:36:14.730
WordPress since 2008 and fell in love with[br]the community in 2016. Passionate about

0:36:14.730,0:36:18.930
giving back, she's an organizer for both[br]the Ottawa WordPress meetup and WordCamp

0:36:18.960,0:36:24.180
Ottawa. When not in front of a computer,[br]Miriam is either a karate sensei, ballroom

0:36:24.180,0:36:27.960
dancer, or clarinetist, just not all at[br]once, but she's working on it.

0:36:31.050,0:36:33.600
Awesome. Feedback? Open to it?

0:36:34.200,0:36:35.190
Oh, you always,

0:36:35.700,0:36:44.370
Always. Um, again, it is super clear,[br]succinct. I am friendly. I liked it. My

0:36:44.370,0:36:48.570
only feedback is you didn't mention your[br]work in our group. And I want you to

0:36:48.570,0:36:50.190
always mention our group,

0:36:50.750,0:36:56.210
I didn't know. I have that written down.[br]"And she is also involved with the diverse

0:36:56.210,0:37:00.260
speaker training group as[br]between-the-trainers lead." Yeah, I think

0:37:00.260,0:37:03.590
maybe that's a bit too wordy. Maybe I'll[br]just say "she's involved with the diverse

0:37:03.590,0:37:06.050
speakers training group."

0:37:08.090,0:37:10.940
That or saying "a leadership position."

0:37:11.020,0:37:15.010
Leadership position. Yeah. Instead of[br]going specific? Yeah.

0:37:15.390,0:37:19.110
I just want you to be mentioning it.[br]Because anytime you're speaking, we'll

0:37:19.110,0:37:23.640
have at least one spot to have a shout out[br]and get our name out there.

0:37:24.080,0:37:26.330
Now, I mentioned it in Niagara last[br]weekend.

0:37:26.360,0:37:32.180
Yes. Any other comments for Miriam?

0:37:34.610,0:37:35.300
That's good.

0:37:37.940,0:37:40.910
Great! I'm sorry, Angela?

0:37:41.770,0:37:51.790
I agree. It's great. And I think.. add a[br]little bit, a little bit more to your

0:37:51.790,0:37:56.560
experience, because you say you have like[br]15 years of experience as a web developer

0:37:57.220,0:38:01.150
but you didn't specify like one[br]experience. You can add, you can add a

0:38:01.150,0:38:05.620
little more in there. It's 15 years,[br]you've got a lot to share.

0:38:11.390,0:38:16.220
Okay, so where we left off in our session[br]was Bhargav was going to share his bio.

0:38:16.250,0:38:17.270
Did you still want to do that?

0:38:20.159,0:38:25.439
Yes. We'll proceed with it. Just Yes.

0:38:26.520,0:38:27.030
Great.

0:38:27.120,0:38:28.590
So should I stand?

0:38:29.070,0:38:31.350
Yes. Thanks.

0:38:33.460,0:38:39.520
I'm currently working as a functional[br]consultant at KrishaWeb. Ecommerce

0:38:39.520,0:38:47.170
increases my dopamine levels. He says[br]humming to the melodies of A.R. Rahman is

0:38:47.830,0:38:53.350
his full time job. Expanding the horizons[br]of knowledge by reading is what people

0:38:53.350,0:38:57.970
will always find him doing. Bhargav is a[br]co-organizer for the Ahmedabad WordPress

0:38:57.970,0:38:59.470
meetup and also WordCamp.

0:39:01.640,0:39:04.760
Nice! I think... did you want feedback?

0:39:08.810,0:39:09.710
Yes

0:39:10.290,0:39:14.220
Awesome. I thought you had some really[br]good points in there. It illustrated a lot

0:39:14.220,0:39:18.240
of, you know, what you do and a little bit[br]of your personality. And I think probably

0:39:18.240,0:39:23.160
just tightening it up a bit. Maybe[br]starting with some of your big roles and

0:39:23.160,0:39:30.480
just saying just a little bit. Probably.[br]It'll depend a bit on where you're

0:39:30.480,0:39:36.090
submitting the bio to. Some of them can be[br]more and a little bit more playful and

0:39:36.090,0:39:44.700
some of them should be really short and[br]tight. Any other thoughts? Aurooba!

0:39:44.480,0:39:50.150
I love the reference to A.R. Rahman. I[br]would like to see maybe another sentence

0:39:50.150,0:39:57.470
about your work. Just to make it a little[br]more balanced. I I felt had the feeling

0:39:57.470,0:40:03.080
that it's the doesn't really share a lot[br]about your experience as much. So maybe

0:40:03.080,0:40:06.260
another sentence about that might help but[br]otherwise really good.

0:40:10.100,0:40:17.180
Anyone else? Great, thanks very much[br]Bhargav. And Chandrika, did you work on

0:40:17.180,0:40:19.340
your pitch and want to share it with us?

0:40:24.080,0:40:28.700
Okay, my pitch is not ready yet, I tried[br]to work on it yesterday, but I just

0:40:28.700,0:40:36.290
couldn't get it. I just don't like it. So[br]I think it's, I know what I want to say,

0:40:36.290,0:40:38.990
but I just can't put it in words yet. So,

0:40:39.059,0:40:44.249
okay. Yeah. If you want it to run it past[br]us now or another time of whatever you

0:40:44.249,0:40:46.889
have currently, that's totally fine. And[br]otherwise,

0:40:47.860,0:41:02.890
I could do it. What I have now but it's...[br]I really don't like it. Okay, so the title

0:41:02.890,0:41:14.440
is "Building custom WordPress sites with[br]ACF blocks." Um, "ACF provides an easy way

0:41:14.440,0:41:18.790
to build custom functionalities and[br]templates in WordPress sites. Combining

0:41:18.790,0:41:24.850
this with Gutenberg gives more power to[br]the users, your clients. This talk is

0:41:24.850,0:41:28.690
geared towards beginner developers who[br]build custom WordPress sites for their

0:41:28.690,0:41:35.740
clients. You'll learn how to build ACF[br]blocks and how these blocks can be used on

0:41:35.740,0:41:37.540
multiple sites in different ways."

0:41:38.770,0:41:42.790
Nice. Did you want  thoughts from us once?[br]Are you done?

0:41:43.180,0:41:45.340
No, no, I was done. I was done. I'm done.

0:41:45.660,0:41:45.990
Awesome

0:41:45.990,0:41:47.760
It's early. I would love to get feedback.

0:41:47.970,0:41:54.150
Great. I loved the last few sentences. I[br]loved the like, where you specified what

0:41:54.150,0:41:58.800
people are getting out of it and who the[br]talk is for and all those things. And

0:41:58.800,0:42:01.680
yeah, I think just working on that first[br]part, but you already said it was kind of

0:42:01.680,0:42:13.110
rough. Yeah. Maybe something around? I'm[br]not sure right now. It's kind of tough.

0:42:13.140,0:42:14.670
Does anybody else have thoughts on that?

0:42:14.480,0:42:17.660
It looks like Aurooba does.

0:42:19.130,0:42:19.730
Oh, sorry.

0:42:23.600,0:42:31.550
I think that maybe including who it's for?[br]Something about who it's for in the first

0:42:31.550,0:42:36.860
part will help. And the other thing I[br]would probably personally suggest is

0:42:36.860,0:42:41.240
mentioning that it's ACF Pro, because you[br]can't build blocks with the free version

0:42:41.240,0:42:41.540
way.

0:42:41.780,0:42:47.600
Okay. Sure. Thank you.

0:42:48.830,0:42:54.470
I will look forward to hearing the rest of[br]that when it's done. Does anybody else

0:42:54.470,0:42:58.220
have anything they wanted to cover before[br]we move on to section number four?