Skip to content

Commit 06a24f0

Browse files
author
Hugues Tennier
authored
Merge pull request #371 from jamstack/pnh/what-is-jamstack-expansion
Pnh/what is jamstack expansion
2 parents 0d80406 + d241aff commit 06a24f0

File tree

7 files changed

+31
-19
lines changed

7 files changed

+31
-19
lines changed

src/site/_data/glossary.yaml

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -33,14 +33,15 @@
3333

3434
- term: 'Decoupling'
3535
id: 'decoupling'
36+
definition: 'Decoupling is the process of creating a clean separation between systems or services. By decoupling the services needed to operate a site, each component part can become easier to reason about, can by independantly swapped out or upgraded, and can be designated the purvue of dedicated specialsts either within an organisation, or as a third party.'
3637

3738
- term: 'Dynamic server'
3839
id: 'dynamic-server'
39-
40+
4041
- term: 'API'
4142
id: 'api'
4243
definition: 'API is the acronym for Application Programming Interface. It defines interactions that allows two applications to talk to each other.'
43-
44+
4445
- term: 'API Economy'
4546
id: 'api-economy'
4647
definition: 'A term that has come to mean the depth and breadth of APIs that are available for developers to use in the current landscape.'
@@ -53,12 +54,12 @@
5354
id: 'monolith'
5455

5556
- term: 'Monorepo'
56-
id: 'monorepo'
57+
id: 'monorepo'
5758

5859
- term: 'Markup'
5960
id: 'Markup'
6061

6162
- term: 'Markdown'
6263
id: 'Markdown'
6364

64-
65+

src/site/_includes/footer.njk

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
<ul class="text-left md:flex justify-between">
44
<li class="p-2">&copy; {{ page.date | formatDate('yyyy') }} Netlify </li>
55
<li class="p-2"><a href="https://jamstack.org/slack">Chat on Slack</a></li>
6-
<li class="p-2"><a href="">Netlify Support</a></li>
6+
<li class="p-2"><a href="https://community.netlify.com/">Netlify Support</a></li>
77
<li class="p-2"><a href="{{ pkg.repository.url }}">Code on GitHub</a></li>
88
</ul>
99
</footer>

src/site/examples.njk

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ layout: layouts/base.njk
4545
<section class="my-12">
4646
<h2 class="text-white font-semi-bold text-3xl">Contribute</h2>
4747
<p>
48-
Should your site be featured here in this gallery? Let us know about it by <a href="{{ pkg.repository.url }}" target="_BLANK" rel="noopener">opening a pull request</a>.
48+
Should your site be featured here in this gallery? Let us know about it by <a href="{{ pkg.repository.url }}/pulls" target="_BLANK" rel="noopener">opening a pull request</a>.
4949
</p>
5050
</section>
5151

src/site/glossary-pages.njk

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ eleventyComputed:
2525
{{- item.definition | safe }}
2626
{% endmarkdown %}
2727
</div>
28-
<p class="mt-12 mb-20">You can help us to expand and improve this glossary <a href="#">by creating an issue</a>.</p>
28+
<p class="mt-12 mb-20">You can help us to expand and improve this glossary <a href="{{ pkg.repository.url }}/issues">by creating an issue</a>.</p>
2929
</section>
3030

3131
{% include "components/join-the-movement.njk" %}

src/site/glossary.njk

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ layout: layouts/base.njk
2020

2121
<section class="border-gray-400 border-b mb-10">
2222
{{ content | safe }}
23-
<p class="mt-12 mb-20">You can help us to expand and improve this glossary <a href="#">by creating an issue</a>.</p>
23+
<p class="mt-12 mb-20">You can help us to expand and improve this glossary <a href="{{ pkg.repository.url }}/issues">by creating an issue</a>.</p>
2424
</section>
2525

2626
{% include "components/join-the-movement.njk" %}

src/site/what-is-jamstack.njk

Lines changed: 14 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -19,22 +19,31 @@ layout: layouts/base.njk
1919
<section>
2020
<h2>Pre-rendering</h2>
2121
<p>
22-
With Jamstack, the entire front end is prebuilt into highly optimized static pages and assets during a build process. This process of pre-rending results in sites which can be served directly from a <a href="/glossary/cdn">CDN</a>, reducing the cost, complexity and risk, of dynamic servers as cirticial infrastructure.
22+
With Jamstack, the entire front end is prebuilt into highly optimized static pages and assets during a build process. This process of pre-rending results in sites which can be served directly from a <a href="/glossary/cdn/">CDN</a>, reducing the cost, complexity and risk, of dynamic servers as cirticial infrastructure.
2323
</p>
2424
<p>
25-
With so many popular tools for generating sites</a>, like Gatsby, Hugo, Jekyll, Eleventy, NextJS, <a href="/generators">and very many more</a>, most web developers are already familiar with the tools needed to become productive Jamstack developers.
25+
With so many popular tools for generating sites</a>, like <a href="/generators/gatsby/">Gatsby</a>, <a href="/generators/hugo/">Hugo</a>, <a href="/generators/jekyll/">Jekyll</a>, <a href="/generators/eleventy/">Eleventy</a>, <a href="/generators/next/">NextJS</a>, <a href="/generators/">and very many more</a>, many web developers are already familiar with the tools needed to become productive Jamstack developers.
2626
</p>
2727
</section>
28-
<section class="mb-12 pb-20 border-gray-400 border-b ">
28+
<section>
2929
<h2>Enhancing with JavaScript</h2>
3030
<p>
31-
With the <a href="/glossary/markup">markup</a> and other user interface assets of Jamstack sites served directly from a CDN, they can be delivered very quickly and securely. On this foundation, Jamstack sites can use JavaScript and APIs to talk to backend services, allowing experiences to be enhanced and personalized.
31+
With the <a href="/glossary/markup/">markup</a> and other user interface assets of Jamstack sites served directly from a CDN, they can be delivered very quickly and securely. On this foundation, Jamstack sites can use JavaScript and APIs to talk to backend services, allowing experiences to be enhanced and personalized.
32+
</p>
33+
</section>
34+
<section class="mb-12 pb-20 border-gray-400 border-b ">
35+
<h2>Supercharging with services</h2>
36+
<p>
37+
The thriving <a hred="/glossary/api-economy/">API economy</a> has become a significant enabler for Jamstack sites. The ability to leverage domain experts who offer their products and service via APIs has allowed teams to build for more complex applications than if they were to take on the risk and burden of such capabilities themselves. Now we can outsource things like authentication and identity, payments, content management, data services, search, and much more.
38+
</p>
39+
<p>
40+
Jamstack sites might utilise such services at build time, and also at run time directly from the browser via JavaScript. And the clean <a href="/glossary/decoupling/">decoupling</a> of these services allows for greater portability and flexibility, as well as significanlty reduced risk.
3241
</p>
3342
</section>
3443
<section class="mb-20 pb-20 border-gray-400 border-b ">
3544
<h2>Named to help the conversation</h2>
3645
<p>
37-
The name "Jamstack" came about because as Matt Biilmann and Chris Bach were creating modern web development workflows and capabilities at Netlify, they found there was no easy way to refer to the architectural approach in conversation. Jamstack embraces many existing fundamentals of web architectures, and so they created the term Jamstack to help us talk about it more succinctly.
46+
The name "Jamstack" came about because as Matt Biilmann and Chris Bach were creating modern web development workflows and capabilities at <a href="https://netlify.com">Netlify</a>, they found there was no easy way to refer to the architectural approach in conversation. Jamstack embraces many existing fundamentals of web architectures, and so they created the term Jamstack to help us talk about it more succinctly.
3847
</p>
3948
<p>
4049
You can learn more about the background, benefits, and case studies of Jamstack in the book <a href="https://www.netlify.com/oreilly-jamstack/">Modern web development on the Jamstack</a>, (Biilmann & Hawksworth, O'Reilly, 2019)

src/site/why-jamstack.njk

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -15,14 +15,16 @@ layout: layouts/base.njk
1515
<h2>Security</h2>
1616
<p>
1717
The Jamstack removes multiple moving parts and systems from the hosting infrastructure resulting in fewer servers and systems to harden against attack.
18-
Serving pages and assets as pre-generated 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.
18+
</p>
19+
<p>
20+
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.
1921
</p>
2022
</section>
2123

2224
<section>
2325
<h2>Scale</h2>
2426
<p>
25-
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 CDN there is no complex logic or workflow to determine what assets can be cached and when.
27+
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.
2628
</p>
2729
<p>
2830
With Jamstack sites everything can be cached in a content delivery network. With simpler deployments, built-in redundancy and incredible load capacity.
@@ -35,14 +37,14 @@ layout: layouts/base.njk
3537
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.
3638
</p>
3739
<p>
38-
With all the pages are already available on a CDN close to the user and ready to serve, very high performance is possible without introducing expensive or complex infrastructure.
40+
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.
3941
</p>
4042
</section>
4143

4244
<section>
4345
<h2>Maintainability</h2>
4446
<p>
45-
When hosting complexity is reduced, so are maintenance tasks. A pre-generated 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".
47+
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".
4648
</p>
4749
<p>
4850
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.
@@ -52,7 +54,7 @@ layout: layouts/base.njk
5254
<section>
5355
<h2>Portability</h2>
5456
<p>
55-
Jamstack sites are pre-generated. 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.
57+
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.
5658
</p>
5759
<p>
5860
Bye-bye infrastructure lock-in.
@@ -62,7 +64,7 @@ layout: layouts/base.njk
6264
<section class="mb-20 pb-20 border-gray-400 border-b ">
6365
<h2>Developer Experience</h2>
6466
<p>
65-
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
67+
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 propser.
6668
</p>
6769
</section>
6870

0 commit comments

Comments
 (0)