Skip to content

Commit 85ba519

Browse files
Normalized links in the side nav and removed routes to individual pages for benefits of the Jamstack.
1 parent a3f0d46 commit 85ba519

File tree

4 files changed

+75
-85
lines changed

4 files changed

+75
-85
lines changed

src/site/_includes/header.njk

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,10 @@
22
{%
33
set linkList = [
44
{ "url": "/", "text": "Home", "children": [
5-
{ "url": "/what-is-jamstack", "text": "What is the Jamstack?" },
6-
{ "url": "/why-jamstack/", "text": "Why Jamstack?" },
7-
{ "url": "/best-practices/", "text": "Jamstack best practices" },
8-
{ "url": "/glossary/", "text": "Glossary" }
5+
{ "url": "#what-is-jamstack", "text": "What is the Jamstack?" },
6+
{ "url": "#why-jamstack/", "text": "Why Jamstack?" }
97
]},
8+
{ "url": "/glossary/", "text": "Glossary" },
109
{ "url": "/women-of-jamstack/", "text": "Women of Jamstack"},
1110
{ "url": "/tv/", "text": "Jamstack TV" },
1211
{ "url": "/generators/", "text": "Site Generators" },
@@ -60,8 +59,7 @@
6059
<a href="https://github.com/jamstack/jamstack.org" target="_BLANK" rel="noopener" class="flex items-center justify-center p-4 hover:text-pink-500">
6160
<svg role="img" aria-label="GitHub" focusable="false" width="36" height="36" class="fill-current"><use xlink:href="#logo-github"></use></svg>
6261
</a>
63-
</div>
64-
<a href="https://jamstackconf.com/" class="block p-4 mt-4 bg-gradient-jams hover:bg-gradient-pink-orange font-bold text-center">Jamstack Conf</a>
62+
</div>
6563
</div>
6664
</nav>
6765
</details>

src/site/_includes/layouts/base.njk

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,6 @@ ogimage: "/img/og/default-og-image.png"
5353
{% include "header.njk" %}
5454
</div>
5555
<div>
56-
{% include "banner.njk" %}
5756
{{ content | safe }}
5857
<div class="border-blue-800 border-t">
5958
{% include "footer.njk" %}

src/site/best-practices.njk

Lines changed: 0 additions & 68 deletions
This file was deleted.

src/site/index.njk

Lines changed: 71 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -8,28 +8,89 @@ layout: layouts/base.njk
88
{% import "components/zinger-cta.njk" as zinger %}
99

1010

11-
<section class="mb-10 p-0">
11+
<section class="my-10 p-0">
1212
{{ ticker.icons() }}
1313
{{ ticker.main() }}
1414
</section>
1515

16+
<section >
17+
<a name="what-is-jamstack">
18+
<h1>What is Jamstack?</h1>
19+
</a>
20+
<p>Pre-generated assets which are highly portable and may be served from a wide variety of hosting platforms. Elevated by modern developer tooling.</p>
21+
</section>
22+
23+
<section>
24+
25+
<h1><a name="why-jamstack">Why Jamstack?</a></h1>
26+
27+
<p >
28+
A Jamstack architecture can bring all sorts of benefits to the sites and to project workflows. Some of the key benefits are:
29+
</p>
30+
</section>
31+
32+
<section>
33+
<h2>Security</h2>
34+
<p>
35+
The Jamstack removes multiple moving parts and systems from the hosting infrastructure resulting in fewer servers and systems to harden against attack.
36+
</p>
37+
<p>
38+
Serving pages and assets as <a href="/glossary/pre-render/">pre-generated</a> files allows read-only hosting reducing attack vectors even further. Meanwhile dynamic tools and services can be provided by vendors with teams dedicated to securing their specific systems and providing high levels of service.
39+
</p>
40+
</section>
41+
42+
<section>
43+
<h2>Scale</h2>
44+
<p>
45+
Popular architectures deal with heavy traffic loads by adding logic to cache popular views and resources. The Jamstack provides this by default. When sites can be served entirely from a <a href="/glossary/cdn/">CDN</a> there is no complex logic or workflow to determine what assets can be cached and when.
46+
</p>
47+
<p>
48+
With Jamstack sites everything can be cached in a content delivery network. With simpler deployments, built-in redundancy and incredible load capacity.
49+
</p>
50+
</section>
51+
52+
<section>
53+
<h2>Performance</h2>
54+
<p>
55+
Page loading speeds have an impact on user experience and conversion. Jamstack sites remove the need to generate page views on a server at request time by instead generating pages ahead of time during a build.
56+
</p>
57+
<p>
58+
With all the pages are already available on a <a href="/glossary/cdn/">CDN</a> close to the user and ready to serve, very high performance is possible without introducing expensive or complex infrastructure.
59+
</p>
60+
</section>
61+
62+
<section>
63+
<h2>Maintainability</h2>
64+
<p>
65+
When hosting complexity is reduced, so are maintenance tasks. A <a href="/glossary/pre-render/">pre-generated</a> site, being served directly from a simple host or directly from a CDN does not need a team of experts to "keep the lights on".
66+
</p>
67+
<p>
68+
The work was done during the build, so now the generated site is stable and can be hosted without servers which might require patching, updating and maintain.
69+
</p>
70+
</section>
71+
1672
<section>
17-
<h1 class="hero-text">What is the Jamstack?</h1>
18-
<p class="mb-8">Pre-generated assets which are highly portable and may be served from a wide variety of hosting platforms. Elevated by modern developer tooling.</p>
73+
<h2>Portability</h2>
74+
<p>
75+
Jamstack sites are <a href="/glossary/pre-render/">pre-generated</a>. That means that you can host them from a wide variety of hosting services and have greater ability to move them to your preferred host. Any simple static hosting solution should be able to serve a Jamstack site.
76+
</p>
77+
<p>
78+
Bye-bye infrastructure lock-in.
79+
</p>
1980
</section>
2081

21-
<section class="mb-20">
22-
<h2>Why Jamstack</h2>
23-
<p class="w-2/3 mb-12">
24-
The Jamstack architecture has many benefits, whether you’re building a large e-commerce site, SaaS application or personal blog.
82+
<section class="mb-20 pb-20 border-gray-400 border-b ">
83+
<h2>Developer Experience</h2>
84+
<p>
85+
Jamstack sites can be built with a wide variety of tools. They do not depend on the proprietary technologies or exotic and little known frameworks. Instead, they build on widely available tools and conventions. As a result, it's not hard to find enthusiastic and talented developers who have the right skills to build with the Jamstack. Efficiency and effectiveness can prosper.
2586
</p>
87+
</section>
2688

27-
<a href="/why-jamstack" class="cta">Read more about the benefits of Jamstack</a>
2889
</section>
2990

30-
<section class="text-center mb-20">
91+
<section class=" mb-16">
3192
<div class="md:w-8/12 mx-auto">
32-
<h2>Rise of the Jamstack</h2>
93+
<h2>The Roots of the Jamstack</h2>
3394
<p class="mt-6 mb-8">
3495
<a href="https://www.netlify.com/authors/matt-biilmann/">Matt Biilmann</a> took the concept of Jamstack mainstream with his presentation at Smashing Conf 2016. Watch the quintessential introduction to the Jamstack.
3596
</p>

0 commit comments

Comments
 (0)