Time for a new website

This commit is contained in:
Don Goodman-Wilson
2022-06-13 14:15:54 +02:00
parent 6fe30f9f18
commit be7c1817d2
44 changed files with 237 additions and 436 deletions

3
.gitignore vendored Normal file
View File

@@ -0,0 +1,3 @@
.DSStore
dev
public

9
404.md
View File

@@ -1,9 +0,0 @@
---
layout: default
---
# 404
Page not found :(
The requested page could not be found.

27
Gemfile
View File

@@ -1,27 +0,0 @@
source "https://rubygems.org"
# Hello! This is where you manage which Jekyll version is used to run.
# When you want to use a different version, change it below, save the
# file and run `bundle install`. Run Jekyll with `bundle exec`, like so:
#
# bundle exec jekyll serve
#
# This will help ensure the proper Jekyll version is running.
# Happy Jekylling!
gem "jekyll", "~> 3.6.3"
# This is the default theme for new Jekyll sites. You may change this to anything you like.
gem "minima", "~> 2.0"
# If you want to use GitHub Pages, remove the "gem "jekyll"" above and
# uncomment the line below. To upgrade, run `bundle update github-pages`.
# gem "github-pages", group: :jekyll_plugins
# If you have any plugins, put them here!
group :jekyll_plugins do
gem "jekyll-feed", "~> 0.6"
end
# Windows does not include zoneinfo files, so bundle the tzinfo-data gem
gem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw, :jruby]

View File

@@ -1,45 +0,0 @@
# Welcome to Jekyll!
#
# This config file is meant for settings that affect your whole blog, values
# which you are expected to set up once and rarely edit after that. If you find
# yourself editing this file very often, consider using Jekyll's data files
# feature for the data you need to update frequently.
#
# For technical reasons, this file is *NOT* reloaded automatically when you use
# 'bundle exec jekyll serve'. If you change this file, please restart the server process.
# Site settings
# These are used to personalize your new site. If you look in the HTML files,
# you will see them accessed via {{ site.title }}, {{ site.email }}, and so on.
# You can create any custom variable you would like, and they will be accessible
# in the templates via {{ site.myvariable }}.
title: The DevRel Salon
email: howdy@devrel.salon
description: >- # this means to ignore newlines until "baseurl:"
You practice developer relations or developer marketing. Perhaps youve been doing it for a while,
and want to share stories. Perhaps you are new and arent yet sure what it is you do. Either way,
you have a story to share, and an urge to hear the stories of others. Same here; Ive got a lot of
questions, and a lot of stories. Lets you and me and the others do something together.
But not a meetup.
baseurl: "/" # the subpath of your site, e.g. /blog
url: "https://www.devrel.salon" # the base hostname & protocol for your site, e.g. http://example.com
twitter_username: DevRelSalon
github_username: DevRelSalon
# Build settings
markdown: kramdown
theme: minima
plugins:
- jekyll-feed
# Exclude from processing.
# The following items will not be processed, by default. Create a custom list
# to override the default setting.
# exclude:
# - Gemfile
# - Gemfile.lock
# - node_modules
# - vendor/bundle/
# - vendor/cache/
# - vendor/gems/
# - vendor/ruby/

View File

@@ -1,6 +0,0 @@
---
title: "DevRel Salon № 14"
when: "Tuesday, 28 May 2019"
where: "Patrick's (Le Ballon Vert), 33 rue de Montreuil, 75011 Paris"
location: "https://www.google.com/maps/embed?pb=!1m18!1m12!1m3!1d2625.4023526059245!2d2.3842484163009017!3d48.850537509212685!2m3!1f0!2f0!3f0!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s0x47e6720b80fe224b%3A0x70962b4d3e82aaac!2sPatrick's+Green+Balloon!5e0!3m2!1sen!2sfr!4v1558437561165!5m2!1sen!2sfr"
content: "<p>The May 2019 Paris edition will be in our \"informal\" format. No slides, no microphonesjust us, some drinks, and some fun discussion.<br><br>Our location: <a href=\"https://patricks-le-ballon-vert.business.site/\">Patrick's (Le Ballon Vert)</a>, located in the 11th near Place de la Nation.<br><br>If you're planning to come, please <a href=\"https://www.meetup.com/Paris-DevRel-Salon/events/259153869/\">RSVP</a> so we can get a big enough table. 🙂"

View File

@@ -1,10 +0,0 @@
<!-- Bootstrap core JavaScript
================================================== -->
<!-- Placed at the end of the document so the pages load faster -->
<!-- Latest compiled and minified JavaScript -->
<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js"></script>
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js"
integrity="sha384-Tc5IQib027qvyjSMfHjOMaLkfuWVxZxUPnCJA7l2mCWNIpG9mGCD8wGNIcPD7Txa"
crossorigin="anonymous"></script>
</body>
</html>

View File

@@ -1,92 +0,0 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta name="description" content="">
<meta name="author" content="">
<link rel="icon" href="favicon.ico">
<title>{{ site.title }}</title>
<!-- Fontawesome CSS -->
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css">
<!-- Bootstrap core CSS -->
<!-- Latest compiled and minified CSS -->
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css"
integrity="sha384-BVYiiSIFeK1dGmJRAkycuHAHRg32OmUcww7on3RYdg4Va+PmSTsz/K68vbdEjh4u" crossorigin="anonymous">
<!-- Custom styles for this template -->
<link href="https://fonts.googleapis.com/css?family=Crimson+Text|Libre+Baskerville:400,400i,700" rel="stylesheet">
<link href="/css/site.css" rel="stylesheet">
<!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries -->
<!--[if lt IE 9]>
<script src="https://oss.maxcdn.com/html5shiv/3.7.3/html5shiv.min.js"></script>
<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
<![endif]-->
<!-- Twitter cards -->
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:site" content="@DevRelSalon">
<meta name="twitter:creator" content="@DEGoodmanWilson">
<meta name="twitter:title" content="The DevRel Salon">
<meta name="twitter:description"
content="You practice developer relations or developer marketing. Let's gather and learn from and support each other.">
<meta name="twitter:image" content="https://devrel.salon/images/paris1739%20twitter.jpg">
<script>
(function (i, s, o, g, r, a, m) {
i['GoogleAnalyticsObject'] = r;
i[r] = i[r] || function () {
(i[r].q = i[r].q || []).push(arguments)
}, i[r].l = 1 * new Date();
a = s.createElement(o),
m = s.getElementsByTagName(o)[0];
a.async = 1;
a.src = g;
m.parentNode.insertBefore(a, m)
})(window, document, 'script', 'https://www.google-analytics.com/analytics.js', 'ga');
ga('create', 'UA-101258282-1', 'auto');
ga('send', 'pageview');
</script>
</head>
<body>
<!-- Fixed navbar -->
<nav class="navbar navbar-default navbar-fixed-top">
<div class="container">
<div class="navbar-header">
<button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar" aria-expanded="false" aria-controls="navbar">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
</div>
<div id="logo"><a href="/"><img src="/images/logo.png"></a></div>
<div id="navbar" class="navbar-collapse collapse">
<ul class="nav navbar-nav">
<li><a href="/">Home</a></li>
<li><a href="https://medium.com/the-devrel-salon">Blog</a></li>
<li role="presentation" class="dropdown">
<a class="dropdown-toggle" data-toggle="dropdown" href="#" role="button" aria-haspopup="true" aria-expanded="false">
Past Meetings <span class="caret"></span>
</a>
<ul class="dropdown-menu">
{% for post in site.posts %}
<li><a href="{{ post.url }}">{{ post.title }}</a></li>
{% endfor %}
</ul>
</li>
<li><a href="mailto:howdy@devrel.salon">Contact</a></li>
<li><a href="https://twitter.com/DevRelSalon"><i class="fa fa-twitter" aria-hidden="true"></i> @DevRelSalon</a></li>
</ul>
</div><!--/.nav-collapse -->
</div>
</nav>

View File

@@ -1,13 +0,0 @@
{% include header.html %}
<div class="container">
<div class="col-md-8 col-md-offset-2 panel panel-default event-listing">
<div class="panel-heading">{{ page.title }}</div>
<div class="panel-body">
{{ content }}
</div>
</div>
</div> <!-- /container -->
{% include footer.html %}

View File

@@ -1,22 +0,0 @@
{% include header.html %}
<div class="container">
<div class="panel panel-default event">
<div class="panel-heading">{{ site.data.latest["title"] }}</div>
<div class="panel-body">
<p>When: {{ site.data.latest["when"] }}</p>
<p>Where: {{ site.data.latest["where"] }}</p>
<iframe src="{{ site.data.latest["location"] }}" width="600" height="450" frameborder="0" style="border:0" allowfullscreen></iframe>
{{ site.data.latest["content"] }}
</div>
</div>
<!-- Main component for a primary marketing message or call to action -->
<div class="jumbotron">
{{ content }}
</div>
</div> <!-- /container -->
{% include footer.html %}

View File

@@ -1,14 +0,0 @@
{% include header.html %}
<div class="container">
<div class="col-md-8 col-md-offset-2 panel panel-default event-listing">
<div class="panel-heading">{{ page.title }}</div>
<div class="panel-body">
{{ content }}
</div>
</div>
</div> <!-- /container -->
{% include footer.html %}

View File

@@ -1,58 +0,0 @@
---
layout: meeting
title: Event № 1
categories: meetings
---
Our premier event was everything we'd hoped it would be: Thirteen people of various backgrounds came together at the Delaville Café in Paris's 10th for an evening of discussing developer relations and marketing.
The two topics of the evening:
* Effective marketing of developer tools, and the best channels to use.
* Methods for collecting survey data from developers
## Marketing developer tools, and the channels to use
* **Identify the customer pain.** The best marketing efforts know where the customer's pain is, and effectively demonstrates that this pain can be solved.
* **Find potential customers suffering from this pain**, and have a conversation with them.
* **Emphasize that this tool represents the _right way_ to get things done.** Developers take pride in crafstmanship, and like the feeling of knowing they are doing things the right way.
* **Open Source makes a great gateway**, whether its related to your product (like PM2 to Keymetrics) or not (like web application boilerplate). Great OSS is a way to demonstrate to developers that you can provide real value.
* **Influencer marketing** is another avenue to pursue: Find individuals who understand the value of the tool, and who are willing to share their usage of the tool. Make the people you reach out to feel special and cool.
* **Offer something new to learn.** Developers are more likely to examine your content if you are genuinely helping them to expand their skillsets and expertise.
* **Obviously branded content is bad.** This is the converse of the last point. If your primary goal in content marketing is to sell, you will fail. Developers require real value to build goodwill with them. Selling and branding destroy goodwill.
* **Facebook Groups** are a surprisingly good channel for finding developer communities to have a conversation with. Also, you don't have to have a developed network to take advantage of Facebook, unlike Twitter.
* **Always be demoing.** This is a great way to get feedback, and to identify potential influencers.
* **Connect your customers to each other.** Pair up experienced customers with new or potential customers, so the one can help the other. This increases the feeling of empowerment, and makes the newer customer feel welcomed into a community.
* **Integrate community support/forums directly into the tool.** Let customers find each other. This provides a sense of community, and social proof that the tool is valuable.
## Collecting survey data from developers
* **Wrap it in code.** Create a short-lifespan repo somehow linked to the survey/whatever and present it as a coding challenge.
* **Standard incentives.** Developers are not immune to dinner-for-two or Amazon-gift-card offers.
* **Face-to-face.** MeetUps and IRL social gatherings encourage a higher level of engagement; in that context, asking someone for 5 minutes of their time ain't no thang (but asking a stranger for 5 minutes is an awful lot).
* **Don't underestimate FB groups.** Facebook is not usually regarded as a "den of dev" but everyone is on it, so it logically follows that developers are there too. They're a bit trickier to find is all. There are large FB groups devoted to DevOps, Python, and so on. Respect group rules, but beyond that, it's a great way to plead to a whole bunch of developers.
* **Public Slack.** Another place we often forget where developers hang out is the ever-growing number of public Slack channels. There is no definitive global directory of these, but [Slacklist (a curated list)](http://www.slacklist.info/) is a pretty good place to start.
* **Hacker News.** We all know: Quora, Slashdot, StackOverflow etc. but we tend to forget
Y-Combinator's very old-school soapbox/bulletin board known as [Hacker News](https://news.ycombinator.com/). The signal/noise ratio is not always great, but a shout-out that catches someone's interest can spread quickly into other channels.
* **Remember phone calls?** Human psychology 101: chatting on the phone for 5 minutes is nothing. Filling in a form on a computer for 5 minutes is eternity. If your survey is long-ish, try outbound calling (many inexpensive services available) and have the outbound caller fill in the form on the interviewee's behalf. Just switching the user experience to conversation will make it a whole new thing.
* **Give them their motivation.** Like movie stars, developers benefit from being reminded why they should do this or that. Putting the effort in context, reminding them of the value of responding, is helpful.

View File

@@ -1,7 +0,0 @@
---
layout: meeting
title: Event № 2
categories: meetings
---
Our sophomore event was everything we'd expected it to be, given that it was held in August, in Paris. Unfortunately, only two folks showed up on the banks of the Seine, and one wasn't a local, but both had a great time swapping stories and enjoying the view of the river.

View File

@@ -1,7 +0,0 @@
---
layout: meeting
title: Event № 3
categories: meetings
---
For the final summer evening in Paris, four devrellers gathered once more on the banks of the Seine for our third event. The small size, and the fair weather meant that conversation was far less structured, but talk centered around [Briq](https://www.givebriq.com), and how to convince developers to invest in a new platform.

View File

@@ -1,7 +0,0 @@
---
layout: meeting
title: Event № 4
categories: meetings
---
For the final 2017 event in Paris, several folks from Sqreen and Algolia gathered in the warmness of Delaville cafe for conversation, and eventually dinner. Once again, the small size meant that conversation was fairly unstructured, so there are no notes on this meeting.

View File

@@ -1,9 +0,0 @@
---
layout: meeting
title: Event № 5
categories: meetings
---
<img src="/images/Salon 2018-01-24 at 19.48.00.jpeg" alt="Selfie of nine attendees of the DevRel Salon taken on 24 January 2018"/>
By far the largest salon so far, over a dozen folks came together at the Delaville Cafe in Paris to talk DevRel strategy. The meeting notes are still being compiled, please excuse the delay.

View File

@@ -1,7 +0,0 @@
---
layout: meeting
title: Event № 6
categories: meetings
---
For Salon № 6, we headed to Amsterdam to enjoy great conversation and great beer at De Zotte. Although this month's group was small, we hope it will grow as we begin to host events in Amsterdam more regularly!

View File

@@ -1,7 +0,0 @@
---
layout: meeting
title: Event № 7
categories: meetings
---
For Salon № 7, we met at Le Bloc, in Paris, over drinks and snacks. And, best of all, we now have a core committee that isn't just [Don](http://twitter.com/DEGoodmanWilson)! Please welcome and [Valériane Venance](https://www.linkedin.com/in/valeriane-venance-03a4b7139/) & [Josh Dzielak](https://twitter.com/dzello) to the team!

View File

@@ -1,7 +0,0 @@
---
layout: meeting
title: Event № 9
categories: meetings
---
After a lull, we have emerged invigorated and empowered heading into 2019 - and a big part of that new vision was our final event of 2018! For Salon № 9, we met at [Datadog (Paris)](https://www.datadoghq.com), and while surrounded by old friends and new faces, we discussed a tough but important topic: Ethics in Developer Relations. Following that round-table, the Paris DevRel Salon braintrust (now including [Dan "phrawzty" Maher](https://twitter.com/phrawzty)) agreed on a new format and rhythm for our 2019 meetups. All in all an important step forward for our burgeoning local community.

View File

@@ -1,7 +0,0 @@
---
layout: meeting
title: Event № 11
categories: meetings
---
First off, thanks to everybody who came out: this was our best-attended meet-up of 2019 yet! Held at the [SFEIR](https://www.sfeir.com/) offices, just outside of Paris in Neuilly-sur-Seine, we had a great presentation by [J-F Garreau](https://twitter.com/jefbinomed) on the talk selection process for [DevFest Nantes](https://devfest.gdgnantes.com/). This was followed by a great discussion group around how to select events to sponsor (from the sponsor's perspective).

6
archetypes/default.md Normal file
View File

@@ -0,0 +1,6 @@
---
title: "{{ replace .Name "-" " " | title }}"
date: {{ .Date }}
draft: true
---

5
build_for_dev.sh Executable file
View File

@@ -0,0 +1,5 @@
#!/bin/bash
rm -rf dev/*
hugo -w -d dev --config config.toml,development.toml

3
config.toml Normal file
View File

@@ -0,0 +1,3 @@
baseURL = 'https://devrel.salon/'
languageCode = 'en-us'
title = 'The DevRel Salon'

13
content/jobs/axiom-2.md Normal file
View File

@@ -0,0 +1,13 @@
---
company: Axiom
companylink: https://www.axiom.co/
jobtitle: Developer Relations Engineer
joblink: https://www.axiom.co/careers/5976907002
contact: Neil Patel
contactlink: mailto:neil@axiom.co
salaryrange: market
location: remote
travel: unknown
PublishDate: 2022-06-13
ExpiryDate: 2022-07-13
---

13
content/jobs/axiom.md Normal file
View File

@@ -0,0 +1,13 @@
---
company: Axiom
companylink: https://www.axiom.co/
jobtitle: Community Manager
joblink: https://www.axiom.co/careers/5976769002
contact: Neil Patel
contactlink: mailto:neil@axiom.co
salaryrange: market
location: remote
travel: unknown
PublishDate: 2022-06-13
ExpiryDate: 2022-07-13
---

13
content/jobs/cerbos.md Normal file
View File

@@ -0,0 +1,13 @@
---
company: Cerbos
companylink: https://cerbos.dev/
jobtitle: Developer Relations Manager
joblink: https://dynamitejobs.com/company/Cerbos/remote-job/developer-relations-manager
contact: Emre Baran
contactlink: mailto:emre@cerbos.dev
salaryrange: 40k USD -150k USD
location: remote
travel: as much as needed
PublishDate: 2022-06-13
ExpiryDate: 2022-07-13
---

View File

@@ -0,0 +1,13 @@
---
company: encore.dev
companylink: https://encore.dev/
jobtitle: Developer Relations Lead
joblink: https://jobs.encore.dev/jobs/1265422-developer-relations-lead
contact: Marcus Johlberg
contactlink: mailto:marcus@encore.dev
salaryrange: market
location: fully remote
travel: unknown
PublishDate: 2022-06-13
ExpiryDate: 2022-07-13
---

13
content/jobs/zenml.md Normal file
View File

@@ -0,0 +1,13 @@
---
company: ZenML
companylink: https://www.zenml.io/home
jobtitle: Developer Relations
joblink: https://zenml.notion.site/ZenML-Open-Positions-dfdb796b738a4e52b202db6e799a665c?p=56e9050193364d4c88f2c86b2609edf2
contact: Adam Probst
contactlink: mailto:careers@zenml.io
salaryrange: 80k USD - 110k USD
location: remote-friendly
travel: unknown
PublishDate: 2022-06-13
ExpiryDate: 2022-07-13
---

View File

@@ -1,54 +0,0 @@
body {
min-height: 1000px;
padding-top: 120px;
font-family: 'Crimson Text', serif;
}
h1, h2, h3, h4, .navbar {
font-family: 'Libre Baskerville', serif;
}
.navbar {
padding-top: 0px;
}
.jumbotron > h1 {
font-size: 40px;
text-align: center;
}
.event-listing {
font-size: 20px;
text-align: left;
}
.event-listing > .panel-heading {
font-family: 'Libre Baskerville', serif;
margin-top: 30px;
font-size: 30px;
text-align: center;
}
.event {
margin-top: 30px;
font-size: 20px;
text-align: center;
}
.event > .panel-heading {
font-family: 'Libre Baskerville', serif;
font-size: 30px;
text-align: center;
}
.navbar-header {
float: right;
}
#logo {
text-align: center;
}
#logo img {
width: 40%;
}

View File

@@ -1,28 +0,0 @@
---
# You don't need to edit this file, it's empty on purpose.
# Edit theme's home layout instead if you wanna make some changes
# See: https://jekyllrb.com/docs/themes/#overriding-theme-defaults
layout: home
---
# ❧ A Call to Action ❧
You practice developer relations or developer marketing. Perhaps youve been doing it for a while, and want to share stories. Perhaps you are new and arent yet sure what it is you do. Either way, you have a story to share, and an urge to hear the stories of others. Same here; Ive got a lot of questions, and a lot of stories.
Lets you and me and the others do something together.
But not a meetup.
> Cause what the world needs now <br />
> is another tech meetup <br />
> like I need a hole in my head
So lets not. Lets do something else instead. This started in Paris—lets do something more egalitarian, something…I don't know, Parisian.
Like a salon. The salons of 17th and 18th century Paris were the most important forum for intellectual discourse of the era, and were the primary conduit for the Renaissance from Italy to the rest of Western Europe. This sounds fun.
What would a modern-day salon look like? More like an <a href="https://www.forbes.com/sites/rebeccabagley/2014/08/18/how-unconferences-unleash-innovative-ideas/#7069e618645b">unconference</a>. No fixed schedule, no lineup of speakers with prepared talks. Instead, well come with topics that have been on our minds of late, and find people who want to discuss them.
There might be a topic of the month. There will be places to sit in quiet conversation with your peers, and meet new people. There will absolutely be a chance for you to be heard, and for you to learn from others, regardless of your ability or desires to get up in front of a room and speak.
What do you think? Will you come join us?

View File

@@ -0,0 +1,65 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta name="description" content="">
<meta name="author" content="">
<link rel="icon" href="favicon.ico">
<title>{{ .Site.Title }}</title>
<!-- Fontawesome CSS -->
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css">
<!-- Custom styles for this template -->
<link href="https://fonts.googleapis.com/css?family=Crimson+Text|Libre+Baskerville:400,400i,700" rel="stylesheet">
<link href="/css/site.css" rel="stylesheet">
<!-- Twitter cards -->
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:site" content="@DevRelSalon">
<meta name="twitter:creator" content="@DEGoodmanWilson">
<meta name="twitter:title" content="The DevRel Salon">
<meta name="twitter:description"
content="You practice developer relations or developer marketing. Let's gather and learn from and support each other.">
<meta name="twitter:image" content="https://devrel.salon/images/paris1739%20twitter.jpg">
<!-- Matomo -->
<script>
var _paq = window._paq = window._paq || [];
/* tracker methods like "setCustomDimension" should be called before "trackPageView" */
_paq.push(['trackPageView']);
_paq.push(['enableLinkTracking']);
(function() {
var u="//analytics.goodman-wilson.com/";
_paq.push(['setTrackerUrl', u+'matomo.php']);
_paq.push(['setSiteId', '5']);
var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
g.async=true; g.src=u+'matomo.js'; s.parentNode.insertBefore(g,s);
})();
</script>
<!-- End Matomo Code -->
</head>
<body>
<div id="logo">
<img src="images/logo.png" />
</div>
<div id="content">
{{ block "main" . }}
<!-- The part of the page that begins to differ between templates -->
{{ end }}
</div>
<div id="#footer">
</div>
</body>
</html>

View File

@@ -0,0 +1,52 @@
{{ define "main" }}
<p>A mostly regular meetup for developer relations professionals (and aspiring professionals) to meet, learn, and grow together.</p>
<h2>Come hang out with us!</h2>
<p>We currently meet in three cities across Europe. Each location has its own Meetup page where you can connect and RSVP:</p>
<ul>
<li><a href="https://www.meetup.com/Paris-DevRel-Salon/">Paris</a> (the OG)</li>
<li><a href="https://www.meetup.com/Amsterdam-DevRel-Salon/">Amsterdam</a></li>
<li>Lisbon (coming soon)</li>
</ul>
<h2>Contact us</h2>
<ul>
<li>email: <a href="mailto:howdy@devrel.salon">howdy@devrel.salon</a></li>
<li>twitter: <a href="https://twitter.com/DevRelSalon">@DevRelSalon</a></li>
</ul>
<h2>DevRel Jobs</h2>
<p>Have a job you'd like to see listed here? <a href="mailto:howdy@devrel.salon?subject=DRS%20job%20listing">Drop us a line</a> and let us know.</p>
<div id="listings">
{{ range (where .Site.Pages "Section" "jobs") }}
{{ range .Pages }}
<hr />
<div>
<a id="{{ .Params.company }}-{{ .Params.jobtitle }}" />
<h3>{{ .Params.jobtitle }} — <a href="{{ .Params.companylink }}">{{ .Params.company }}</a></h3>
<ul>
<li>Job title: {{ .Params.jobtitle }}</li>
<li>Salary range: {{ .Params.salaryrange }}</li>
<li>Location: {{ .Params.location }}</li>
<li>Travel: {{ .Params.travel }}</li>
<li>Contact: <a href="{{ .Params.contactlink }}">{{ .Params.contact }}</a>
</ul>
<p><a href="{{ .Params.joblink }}">More information</a></p>
</div>
{{ end }}
{{ end }}
<hr />
</div>
<div id="footer">
</div>
{{ end }}

View File

@@ -0,0 +1,3 @@
{{ define "main" }}
{{ .Content }}
{{ end }}

View File

@@ -0,0 +1,3 @@
{{ define "main" }}
{{ .Content }}
{{ end }}

32
static/css/site.css Normal file
View File

@@ -0,0 +1,32 @@
body {
font-family: 'Crimson Text', serif;
font-size: 2em;
}
h1, h2, h3, h4 {
font-family: 'Libre Baskerville', serif;
text-align: center;
}
#content {
width: 66vw;
margin: 0 auto;
}
#logo {
/*text-align: center;*/
}
#logo img {
width: max(66vw, 500px);
display: block;
margin: 0 auto;
}
#listings {
font-size: 1em;
width: 60vw;
margin: 0 auto;
}

Binary file not shown.

After

Width:  |  Height:  |  Size: 674 KiB

View File

Before

Width:  |  Height:  |  Size: 218 KiB

After

Width:  |  Height:  |  Size: 218 KiB

View File

Before

Width:  |  Height:  |  Size: 456 KiB

After

Width:  |  Height:  |  Size: 456 KiB

View File

Before

Width:  |  Height:  |  Size: 50 KiB

After

Width:  |  Height:  |  Size: 50 KiB

BIN
static/images/logo.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 50 KiB

View File

Before

Width:  |  Height:  |  Size: 914 KiB

After

Width:  |  Height:  |  Size: 914 KiB

View File

Before

Width:  |  Height:  |  Size: 6.4 MiB

After

Width:  |  Height:  |  Size: 6.4 MiB

View File

Before

Width:  |  Height:  |  Size: 2.0 MiB

After

Width:  |  Height:  |  Size: 2.0 MiB

View File

Before

Width:  |  Height:  |  Size: 825 KiB

After

Width:  |  Height:  |  Size: 825 KiB

View File

Before

Width:  |  Height:  |  Size: 1.3 MiB

After

Width:  |  Height:  |  Size: 1.3 MiB