@@ -10,24 +10,26 @@ <h1>{{ .Site.Data.definitions.jamstack | markdownify }}</h1>
<div>{{ .Site.Data.definitions.explanation | markdownify }}</div>
<div>
<h1>FAQ</h1>
<a class="text-link scrolling-link" href="#what"><h4>What is the JAMstack?</h4></a>
<a class="text-link scrolling-link" href="#why"><h4>Why the JAMstack?</h4></a>
<a class="text-link scrolling-link" href="#what"><h4>What is the Jamstack?</h4></a>
<a class="text-link scrolling-link" href="#why"><h4>Why the Jamstack?</h4></a>
<a class="text-link scrolling-link" href="#how"><h4>How do I get started?</h4></a>
</div>
</div>
</section>

<section id="what" class="jam-breakdown">
<div class="contained intro">
<h1>What is the JAMstack?</h1>
<h1>What is the Jamstack?</h1>
<p>
You may have already seen or worked on a JAMstack site! They do not have to include <em>all</em> attributes of JavaScript, APIs, and Markup. They might be built using by hand, or with Jekyll, Hugo, Nuxt, Next, Gatsby, or another <a href="https://www.staticgen.com">static site generator</a>...
You may have already seen or worked on a Jamstack site! They might be built using by hand, or with Jekyll, Hugo, Nuxt, Next, Gatsby, or another <a href="https://www.staticgen.com">static site generator</a>...
</p>
<p>
The thing that they all have in common is that they don’t depend on a web server.
</p>
</div>
<div class="letter-definition">

<!--
<div class="letter-definition">
<img class="letter" src="/img/j.svg"/>
<h1>JavaScript</h1>
<p>{{ .Site.Data.definitions.javascript | markdownify }}</p>
@@ -42,11 +44,12 @@ <h1>APIs</h1>
<h1>Markup</h1>
<p>{{ .Site.Data.definitions.markup | markdownify }}</p>
</div>
-->
</section>

<section class="jam-disqualifications contained">
<h1>When is your site <em>not</em> built with the JAMstack?</h1>
<p>Any project that relies on a tight coupling between client and server is not built with the JAMstack. This would include:</p>
<h1>When is your site <em>not</em> built with the Jamstack?</h1>
<p>Any project that relies on a tight coupling between client and server is not built with the Jamstack. This would include:</p>
<div class="disqualifications">
{{ range .Site.Data.definitions.disqualifications }}
<h4 class="disqualification">{{ .disqualification | markdownify }}</h4>
@@ -55,7 +58,7 @@ <h4 class="disqualification">{{ .disqualification | markdownify }}</h4>
</section>

<section id="why" class="advantages contained">
<h1>Why the JAMstack?</h1>
<h1>Why the Jamstack?</h1>
<div class="advantages-grid">
{{ range .Site.Data.definitions.advantages }}
<div class="advantage">
@@ -2,7 +2,7 @@
<div class="best-practices">
<div class="contained">
<h1 class="headline">Best Practices</h1>
<p class ="cta">When building JAMstack projects, you can really get the most out of the stack if you stick to a few best practices.</p>
<p class ="cta">When building Jamstack projects, you can really get the most out of the stack if you stick to a few best practices.</p>
<div class="grid">
{{ range .Site.Data.bestpractices.bestpractices }}
<div class="best-practice">
@@ -3,7 +3,7 @@

<section class="hero">
<div class="contained">
<h1 class="community-headline">Join your local JAMstack Chapter.</h1>
<h1 class="community-headline">Join your local Jamstack Chapter.</h1>
</div>
</section>

@@ -24,11 +24,11 @@ <h1>{{ .name }}</h1>
<h1>Chat on Slack.</h1>
<p>
<strong>Got a question or just want to chat?</strong>
Speak with leaders in the space about all things JAMstack in the <a href="{{ .Site.Data.community.slackurl }}" target="_blank" class="text-link">JAMstack community Slack</a>.
Speak with leaders in the space about all things Jamstack in the <a href="{{ .Site.Data.community.slackurl }}" target="_blank" class="text-link">Jamstack community Slack</a>.
</p>
</div>
<a href="{{ .Site.Data.community.slackurl }}" target="_blank" class="event-card">
<h4>Join the JAMstack Slack for...</h4>
<h4>Join the Jamstack Slack for...</h4>
<p>
<strong>• Expert advice on best practices</strong>
<strong>• Resource recommendations</strong>
@@ -84,7 +84,7 @@ <h4>Join the JAMstack Slack for...</h4>
})
</script>

<h1>Come hang out at the next JAMstack event.</h1>
<h1>Come hang out at the next Jamstack event.</h1>
{{ range .Site.Data.events.events }}
<a href='{{ if .link }}{{ .link }}{{ end }}' class='event-card{{ if .link }} with-link{{ end }}'>
<div class="event-date">{{ dateFormat "Jan 02" .date }}</div>
@@ -117,7 +117,7 @@ <h1>{{ .Site.Data.community.bottomcta.headline }}</h1>
</div>

<section class="chatter">
<h1>Spread the JAM by tweeting <span><img src="/img/twitter.svg"/>#JAMstack</span></h1>
<h1>Spread the JAM by tweeting <span><img src="/img/twitter.svg"/>#Jamstack</span></h1>
<div class="tweets">
<div class="contained">
<ul class="juicer-feed" data-feed-id="jamstack" data-pages="1" data-overlay="false" data-per="3"></ul>
@@ -14,7 +14,7 @@ <h4><img src="/img/thumbs-up.svg" /> {{ .title }}</h4>

<div class="contained">
<h4>Anti-Harassment Policy</h4>
JAMstack meetups are dedicated to providing a harassment-free experiences for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion (or lack thereof), or technology choices. We do not tolerate harassment of participants in any form. Sexual language and imagery is not appropriate for any meetup venue, including talks, workshops, parties, Twitter and other online media. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organisers.
Jamstack meetups are dedicated to providing a harassment-free experiences for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion (or lack thereof), or technology choices. We do not tolerate harassment of participants in any form. Sexual language and imagery is not appropriate for any meetup venue, including talks, workshops, parties, Twitter and other online media. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organisers.
<br>
<ul>
<li>Sponsors and speakers should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.</li>
@@ -53,7 +53,7 @@ <h4>Reporting</h4>
After filing a report, a representative will contact you personally, review the incident, follow up with any additional questions, and make a decision as to how to respond. If the person who is harassing you is part of the response team, they will recuse themselves from handling your incident. If the complaint originates from a member of the response team, it will be handled by a different member of the response team. We will respect confidentiality requests for the purpose of protecting victims of abuse.
<br><br>
<h4>Enforcement</h4>
Adherence to and acceptance of this Code of Conduct is a condition of entry to all JAMstack events. Participants asked to stop any harassing behavior are expected to comply immediately. This includes all attendees, sponsors, speakers, organizers, volunteers, and venue or vendor staff.
Adherence to and acceptance of this Code of Conduct is a condition of entry to all Jamstack events. Participants asked to stop any harassing behavior are expected to comply immediately. This includes all attendees, sponsors, speakers, organizers, volunteers, and venue or vendor staff.
If a participant engages in harassing behaviour, event organizers retain the right to take any actions to keep the event a welcoming environment for all participants. This includes, but is not limited to, warning the offender, expulsion from the event with no refund, and a ban on attending future events.
<br><br>
</div>
@@ -2,10 +2,10 @@
<div class="examples">
<div class="contained">
<div class="cta grid">
<h1>If you can use it on the web, you can probably build it with the JAMstack. Millions already do. Check out the JAMstacks of these examples below:</h1>
<h1>If you can use it on the web, you can probably build it with the Jamstack. Millions already do. Check out the Jamstacks of these examples below:</h1>
<p>
<strong>Want to get your site listed here?</strong>
Submit a Pull Request with your JAMstack project’s information <a href="https://github.com/jamstack/jamstack.org" class="text-link">here</a>.
Submit a Pull Request with your Jamstack project’s information <a href="https://github.com/jamstack/jamstack.org" class="text-link">here</a>.
</p>
</div>
<div class="grid">
@@ -3,8 +3,8 @@
<div class="resources">
<h1 class="contained">Resources</h1>
<p class="contained">
<strong>Have a great JAMstack resource to share?</strong>
Submit a Pull Request with your JAMstack resource's information <a
<strong>Have a great Jamstack resource to share?</strong>
Submit a Pull Request with your Jamstack resource's information <a
href="https://github.com/jamstack/jamstack.org">here</a>.
</p>

@@ -23,19 +23,19 @@ <h4>{{ .title }}</h4>
{{ end }}
</div>
</section>

<section class="contained">
<h1>Modern Web Development on the JAMstack eBook</h1>
<h1>Modern Web Development on the Jamstack eBook</h1>
<p>New Techniques for Ultra Fast Sites and Web Applications by Mathias Biilmann & Phil Hawksworth - <a href="https://www.netlify.com/oreilly-jamstack/" target="_blank" class="text-link">Get a free copy of eBook</a></p>

<p>
<strong>• Methods for solving web development challenges — from architecture to microservices</strong>
<strong>• Why the JAMstack’s cleaner architecture eliminates the need to scale sites up front</strong>
<strong>• Best practices for adopting the JAMstack in your organization</strong>
<strong>• Why the Jamstack’s cleaner architecture eliminates the need to scale sites up front</strong>
<strong>• Best practices for adopting the Jamstack in your organization</strong>
</p>

<a href="https://www.netlify.com/oreilly-jamstack/" target="_blank" class="text-link">
<h2>Download the JAMstack eBook →</h2>
<h2>Download the Jamstack eBook →</h2>
</a>
</section>

@@ -61,14 +61,14 @@ <h3>{{ .title }}</h3>
</div>
<div class="teaser">
<h1>Tune into the Podcast</h1>
<p>Every week, Brian Douglas from Netlify talks with special guests about all things pertaining to the JAMstack.
<p>Every week, Brian Douglas from Netlify talks with special guests about all things pertaining to the Jamstack.
</p>
</div>
</div>
</section>

<section class="chatter">
<h1>Spread the JAM by tweeting <span><img src="/img/twitter.svg" />#JAMstack</span></h1>
<h1>Spread the JAM by tweeting <span><img src="/img/twitter.svg" />#Jamstack</span></h1>
<div class="tweets">
<div class="contained">
<ul class="juicer-feed" data-feed-id="jamstack" data-pages="1" data-overlay="false" data-per="3"></ul>
@@ -1,7 +1,7 @@
<div class="promo-banner">
<p>
<strong>New!</strong>
The first O'Reilly report on the JAMstack.
The first O'Reilly report on the Jamstack.
<a href="https://www.netlify.com/oreilly-jamstack/" target="_blank">Get&nbsp;the&nbsp;free&nbsp;eBook</a>
</p>
</div>
363 yarn.lock

Large diffs are not rendered by default.