Skip to content

Commit f7c4063

Browse files
JensRavensJensRavens
committed
new how to become a speaker page
1 parent 4f817f4 commit f7c4063

File tree

6 files changed

+134
-10
lines changed

6 files changed

+134
-10
lines changed

‎_includes/header.html

+1
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,7 @@
99
<a href="/">Meetup</a>
1010
<a href="#contact">Contact</a>
1111
<a href="/archive">Archive</a>
12+
<a href="/how-to-become-a-speaker">Become a Speaker</a>
1213
</div>
1314
</nav>
1415
</div>

‎_layouts/page.html

+52-8
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,58 @@
11
---
22
layout: default
33
---
4-
<div class="post">
4+
<div class="container">
5+
<div class="page">
6+
{{content}}
7+
</div>
8+
</div>
59

6-
<header class="post-header">
7-
<h1 class="post-title">{{ page.title }}</h1>
8-
</header>
10+
<div class="spacer"></div>
911

10-
<article class="post-content">
11-
{{ content }}
12-
</article>
12+
<section id="signup" class="signup">
13+
<form method="post" action="http://nerdgeschossberlin.us7.list-manage1.com/subscribe/post?u=908a2b4a2459206128cbf70df&id=882566a362" name="mc-embedded-subscribe-form">
14+
<div class="container">
15+
<div class="row">
16+
<div class="col-sm-8">
17+
<input type="text" name="EMAIL" placeholder="Enter your e-mail" spellcheck="false">
18+
</div>
19+
<div class="col-sm-4">
20+
<button class="btn btn-large btn-danger" type="submit">Subscribe to our newsletter</button>
21+
</div>
22+
</div>
23+
</div>
24+
</form>
25+
</section>
1326

14-
</div>
27+
<secion id="contact">
28+
<div class="container">
29+
<div class="row">
30+
<div class="col-sm-3">
31+
<h3>nerdgeschoss GmbH</h3>
32+
<p>
33+
Wilhelmstraße 41<br>
34+
D-10963 Berlin<br>
35+
+49 30 36 42 86 58
36+
</p>
37+
<p>
38+
<a href="http://nerdgeschoss.de/contact/">Impressum</a>
39+
</p>
40+
</div>
41+
<div class="col-sm-4">
42+
<h3>Help</h3>
43+
<p>Need help? Don’t hestiate to ask us something. Email us directly at
44+
<a href="#">[email protected]</a>.
45+
You can checkout our <a href="http://nerdgeschoss.de">website</a> or the <a href="http://www.meetup.com/swift-berlin/events/187497112/">meetup group</a>.
46+
</p>
47+
</div>
48+
<div class="col-sm-3">
49+
<h3 id="archive">Archive</h3>
50+
<p>
51+
{% for post in site.posts %}
52+
<a href="{{ post.url | prepend: site.baseurl }}">{{post.title}} @ {{post.location.name}}</a><br>
53+
{% endfor %}
54+
</p>
55+
</div>
56+
</div>
57+
</div>
58+
</secion>

‎_layouts/post.html

+1-2
Original file line numberDiff line numberDiff line change
@@ -67,8 +67,7 @@ <h3>{{speaker.name}}</h3>
6767
<div class="row text-center">
6868
<div class="col-md-8 col-md-offset-2">
6969
<h3>Speakers wanted!</h3>
70-
<p>Hey, do you want to propose a talk? Open an issue with your idea on our
71-
repo at <a href="https://github.com/swift-berlin/swift-berlin.github.io" target="new">GitHub</a>!</p>
70+
<p>Hey, do you want to propose a talk? Read here <a href="/how-to-become-a-speaker">how to become a speaker</a>!</p>
7271
</div>
7372
</div>
7473
{% endif %}

‎_sass/_base.scss

+13
Original file line numberDiff line numberDiff line change
@@ -42,3 +42,16 @@ a {
4242
color: $color-tint;
4343
}
4444
}
45+
46+
.page {
47+
max-width: 750px;
48+
49+
h1 {
50+
margin-bottom: 60px;
51+
}
52+
53+
h3 {
54+
margin-top: 40px;
55+
margin-bottom: 20px;
56+
}
57+
}

‎_sass/_layout.scss

+4
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,10 @@
3333
}
3434
}
3535

36+
.spacer {
37+
margin-top: 60px;
38+
}
39+
3640

3741
.bigHeader {
3842
img {

‎how-to-be-a-speaker.md

+63
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
---
2+
title: How to become a Speaker
3+
layout: page
4+
permalink: /how-to-become-a-speaker/
5+
---
6+
7+
# Become a Speaker at swift.berlin
8+
9+
We're always happy to have speakers from our community presenting their talks. Here are some notes on how to prepare for your talk and schedule your talk for a meetup.
10+
11+
Please be aware that we're completly organized by the community for the community. Therefore we cannot cover any travel expenses or hotel bookings.
12+
13+
### Step 1: Select a Format
14+
15+
We have both slots for full featured talks (25min + QA-Time) and Lightningtalks (5min + QA-Time).
16+
17+
If you want to talk about your or your company's product, please do a lightning talk instead of a full talk.
18+
19+
### Step 2: Select a Topic
20+
21+
Already have a topic? Great! If not, here are some examples of topics that have been requested by our members:
22+
23+
- Open Source Swift
24+
- Swift on Linux
25+
- Memory Management, Retain Cycles, Profiling
26+
- Monads and Functors
27+
- RxSwift
28+
- Application Architecture
29+
30+
You can also take a look at our [archives](/archive) about talks we've already seen.
31+
32+
### Step 3: Open an Issue
33+
34+
To coordinate all talks, we discuss them openly [here at GitHub](https://github.com/swift-berlin/swift-berlin.github.io/issues).
35+
Please open an issue and add this information to your proposal:
36+
37+
- your full name
38+
- your company's name if you want to have it mentioned
39+
- title of your talk
40+
- a short abstract
41+
- a short bio (optional)
42+
- your twitter handle, so we can mention you on all tweets regarding your talk
43+
- Which audience is your talk aimed at? Swift Beginners, Seniors or is it a general topic for everyone?
44+
45+
Please also note on which meetup (e.g. which date) you would like to give that talk.
46+
47+
### Step 4: Prepare your talk
48+
49+
Prepare everything for your talk. If you have any questions at that time, just update your issue at GitHub or write us on Slack.
50+
51+
### Step 5: The Meetup
52+
53+
Usually we give you a hint before the meetup at which time your talk will be. Please bring your own device. We try to provide a beamer or big screen with HDMI connection. If you need anything else, please ask us a few days before.
54+
55+
During the meetups we take some pictures and sometimes do video recordings of the talks. If that is not OK for you, please mention this in your issue on GitHub. Those videos will not be sold or used for any commercial uses and are only recorded for developers that cannot attend a meetup.
56+
57+
Your audience will be a group of about 60 to 90 swift developers from different backgrounds. After your talk there is some time for QA (about 5 minutes).
58+
59+
### Step 6: After the Meetup
60+
61+
You're done! Thank your for helping the swift.berlin community.
62+
63+
Please upload your slides and/or example code somewhere so we can share it with all members.

0 commit comments

Comments
 (0)