-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathspeak.html
92 lines (85 loc) · 4.04 KB
/
speak.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
<!doctype html>
<html>
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="chrome=1">
<title>Bleeding Edge Web: Speaking</title>
<link rel="stylesheet" href="stylesheets/styles.css?240330">
<link rel="icon" type="image/x-icon" href="/favicon.ico" />
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no">
<!--[if lt IE 9]>
<script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
<style>
.note {
font-size: .8em;
border: 1px solid #dddddd;
background: #f6f6f6;
padding: 10px 20px;
border-radius: 5px;
font-style: italic;
}
</style>
</head>
<body>
<div class="wrapper">
<header>
<h1><a href="/">Bleeding Edge Web</a></h1>
<p class="subhead">A meetup for the discerning web app developer</p>
<img src="images/bleeding-edge.png" alt="Bleeding Edge Web">
<p><a href="./">← Home</a></p>
</header>
<section>
<h2>Speaking Opportunities</h2>
<p>To volunteer to speak, or if you have any questions about speaking, please <a
href="mailto:bleedingedgeatx@gmail.com?subject=Speaking%20Inquiry">email us</a>.
<p>Bleeding Edge Web events follow a consistent format:</p>
<ol>
<li>Welcome & Announcements</li>
<li>Bleeding Edge Update (20 minutes)</li>
<li><b>Lightning Talks</b> (1-2 talks, 5-10 mins each)</li>
<li><b>Deep Dive/Primary Talk</b> (~30 minutes)</li>
<li>Meetup formally ends by 9pm.</li>
</ol>
<p id="speaker-guide"><em><strong>Speaker Guide</strong></em></p>
<p>If you are ready to present at the meetup, we have a <a href="./speaker-guide.html">handy speaker
guide</a> that includes what we'll need from you and some tips that might help with your talk.
Still considering it? Read on.
</p>
<p id="what"><em><strong>What to Talk About</strong></em></p>
<p class="note">If you'd like to talk but don't think you can fill 30 minutes, consider
giving a lightning talk (see below)!</p>
<p>We like to discuss all things web + mobile. We've had a number of talks about Node.js,
HTML/JS/CSS, web servers, libraries & frameworks, etc. We've also had talks about
Google Glass, "Internet of things", etc. Bottom line: <strong>if you think it would
interest other web app developer types, it's likely a good fit</strong>.
<p>If you are part of a meetup organized around a specific technology you might be a good candidate
for speaking to our group. Overview talks about languages and franeworks generally make for
perfect topics for our members who might not otherwise attend a meetup specific to them.</p>
<p id="lightning-talks"><em><strong>Lightning Talks</strong></em></p>
<p>There aren't any formal guidelines for these, other than trying to keep it to 5-10 minutes.
Some people use 3-5 slides, some just talk. Topics can be anything of interest
to the group. You know what the group is interested in because you're a part of
it (what interests you?).</p>
<ul>
<li>A project you're working on at work or for fun (show & tell)</li>
<li>A new (or new-to-you) code library/framework that excites you (mini-lesson)</li>
</ul>
<p>Lightning talks in the past have covered things like Vue.js, RiotJS, functional programming,
mobile apps, CSS Pointer Events, Node.js utilities, developer services, personal project,
hackathons, etc.</p>
</section>
</div>
<script src="javascripts/scale.fix.js"></script>
<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
</script>
<script type="text/javascript">
try {
var pageTracker = _gat._getTracker("UA-18103207-9");
pageTracker._trackPageview();
} catch(err) {}
</script>
</body>
</html>