Skip to content

Commit 7c5de38

Browse files
domitriusclarkdomitriusclark
committed
Added some groupind and spacing to the why jamstack section.
1 parent 8230670 commit 7c5de38

File tree

2 files changed

+37
-57
lines changed

2 files changed

+37
-57
lines changed

‎src/css/tailwind.css‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,12 +18,11 @@
1818
}
1919
}
2020
h2 {
21-
@apply text-white text-3xl font-bold leading-none mb-8;
21+
@apply text-white text-3xl font-bold leading-none mb-2 underline;
2222
}
2323
@screen md {
2424
h2 {
2525
@apply text-3xl;
26-
@apply underline;
2726
}
2827
}
2928
}

‎src/site/index.njk‎

Lines changed: 36 additions & 55 deletions
Original file line numberDiff line numberDiff line change
@@ -7,89 +7,72 @@ layout: layouts/base.njk
77
{% import "components/section-heading.njk" as section %}
88
{% import "components/zinger-cta.njk" as zinger %}
99

10-
1110
<section class="my-10 p-0">
1211
{{ ticker.icons() }}
1312
{{ ticker.main() }}
1413
</section>
1514

16-
<section class="relative p-10 h-[200px]">
15+
<section class="relative p-10 mb-16">
1716
<div class="p-2 rounded-lg bg-gradient-jams" w-full>
1817
<div class="flex flex-col bg-blue-900 p-10">
1918
<a class="border-b-0" name="what-is-jamstack">
2019
<h1>What is <span class="font-extrabold text-transparent bg-clip-text bg-gradient-jams">Jamstack</span>?</h1>
2120
</a>
22-
21+
2322
<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>
2423
<h3 class="mt-3">Jamstack projects have:</h3>
2524
<ul class="list-disc ml-4">
2625
<li>
2726
Ready-to-serve assets
2827
</li>
2928
<li>
30-
Any interactivity provided <em>without a managed server</em>
29+
Any interactivity provided <em>without a managed server</em>
3130
</li>
3231
<li>
3332
Any interactivity provided by some combination of Javascript and decoupled services via APIs
3433
</li>
3534
</ul>
3635
</div>
37-
3836
</div>
3937
</section>
4038

41-
<div class="bg-gray-100">
42-
43-
44-
<section>
45-
<a name="why-jamstack">
46-
<h1>Why Jamstack?</h1>
47-
</a>
48-
<p>
49-
A Jamstack architecture can bring all sorts of benefits to the sites and to project workflows. Some of the key benefits are:
50-
</p>
51-
52-
<h2>Security</h2>
53-
<p>
54-
The Jamstack removes multiple moving parts and systems from the hosting infrastructure resulting in fewer servers and systems to harden against attack.
55-
</p>
56-
<p>
57-
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.
58-
</p>
59-
60-
<h2>Scale</h2>
61-
<p>
62-
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.
63-
</p>
64-
<p>
65-
With Jamstack sites everything can be cached in a content delivery network. With simpler deployments, built-in redundancy and incredible load capacity.
66-
</p>
39+
<div class="bg-gray-100 mb-16">
40+
<section class="py-10">
41+
<a name="why-jamstack">
42+
<h1>Why Jamstack?</h1>
43+
</a>
44+
<p>A Jamstack architecture can bring all sorts of benefits to the sites and to project workflows. Some of the key benefits are:</p>
45+
46+
<div class="my-10">
47+
<h2>Security</h2>
48+
<p>The Jamstack removes multiple moving parts and systems from the hosting infrastructure resulting in fewer servers and systems to harden against attack.</p>
49+
<p>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.</p>
50+
</div>
6751

68-
<h2>Performance</h2>
69-
<p>
70-
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.
71-
</p>
72-
<p>
73-
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.
74-
</p>
52+
<div class="my-10">
53+
<h2>Scale</h2>
54+
<p>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.</p>
55+
<p>With Jamstack sites everything can be cached in a content delivery network. With simpler deployments, built-in redundancy and incredible load capacity.</p>
56+
</div>
7557

76-
<h2>Maintainability</h2>
77-
<p>
78-
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".
79-
</p>
80-
<p>
81-
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.
82-
</p>
58+
<div class="my-10">
59+
<h2>Performance</h2>
60+
<p>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.</p>
61+
<p>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.</p>
62+
</div>
8363

84-
<h2>Developer Experience</h2>
85-
<p>
86-
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.
87-
</p>
88-
</section>
89-
</div>
64+
<div class="my-10">
65+
<h2>Maintainability</h2>
66+
<p>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".</p>
67+
<p>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.</p>
68+
</div>
9069

91-
<section class="mb-20 pb-20 border-gray-400 border-b ">
70+
<div class="my-10">
71+
<h2>Developer Experience</h2>
72+
<p>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.</p>
73+
</div>
9274
</section>
75+
</div>
9376

9477
<section class=" mb-16">
9578
<div class="md:w-8/12 mx-auto">
@@ -106,6 +89,4 @@ layout: layouts/base.njk
10689
</div>
10790
</section>
10891

109-
110-
{% include "components/join-the-movement.njk" %}
111-
92+
{% include "components/join-the-movement.njk" %}

0 commit comments

Comments
 (0)