Skip to main content

Return to Answer

Second iteration [<https://en.wikipedia.org/wiki/WordPress> <https://en.wikipedia.org/wiki/Markdown>].
Source Link
Peter Mortensen
Peter Mortensen
  • 31.6k
  • 22
  • 109
  • 133

  1. "Markup" is for a markup language such as Markdown, but maybe also all other languages, AsciiDoc, etc. With JAMstack we have the constraint, and advantage, that it is static rendered, as opposite to other CMSes, like wordpressWordPress

  2. I discovered with you the JAMstack principle, the most important is that it is statically rendered, using Git as backup. So:

  • if you are using React in the runtime phase, it is not JAMstack,
  • but if you use it at compile time and deliver rendered HTML content to your production HTTP server, it is JAMstack.

Here is an article stating that the most important is having static files, not only JavaScript, calling "SHAMstack": JAMstack? More like SHAMstack

I have used, for example, static pages of GitHub using Jekyll (the default on GitHub) and markdownMarkdown. The HTML content is rendered on the commit.

  1. "Markup" is for a markup language such as Markdown, but maybe also all other languages, AsciiDoc, etc. With JAMstack we have the constraint, and advantage, that it is static rendered, as opposite to other CMSes, like wordpress

  2. I discovered with you the JAMstack principle, the most important is that it is statically rendered, using Git as backup. So:

  • if you are using React in the runtime phase, it is not JAMstack,
  • but if you use it at compile time and deliver rendered HTML content to your production HTTP server, it is JAMstack.

Here is an article stating that the most important is having static files, not only JavaScript, calling "SHAMstack": JAMstack? More like SHAMstack

I have used, for example, static pages of GitHub using Jekyll (the default on GitHub) and markdown. The HTML content is rendered on the commit.

  1. "Markup" is for a markup language such as Markdown, but maybe also all other languages, AsciiDoc, etc. With JAMstack we have the constraint, and advantage, that it is static rendered, as opposite to other CMSes, like WordPress

  2. I discovered with you the JAMstack principle, the most important is that it is statically rendered, using Git as backup. So:

  • if you are using React in the runtime phase, it is not JAMstack,
  • but if you use it at compile time and deliver rendered HTML content to your production HTTP server, it is JAMstack.

Here is an article stating that the most important is having static files, not only JavaScript, calling "SHAMstack": JAMstack? More like SHAMstack

I have used, for example, static pages of GitHub using Jekyll (the default on GitHub) and Markdown. The HTML content is rendered on the commit.

Active reading [<en.wikipedia.org/wiki/AsciiDoc> <en.wikipedia.org/wiki/Netlify#Jamstack> <en.wikipedia.org/wiki/Git> <en.wikipedia.org/wiki/React_(JavaScript_library)> <en.wikipedia.org/wiki/HTML> <en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>]. Dressed the naked link. Added some context.
Source Link
Peter Mortensen
Peter Mortensen
  • 31.6k
  • 22
  • 109
  • 133

  1. "Markup" is for a markup language such as Markdown, but maybe also all other languagelanguages, ascidocAsciiDoc, etc. . With jamstackJAMstack we have the constraint, and advantage, that it is static rendered, as opposite to other CMSCMSes, like wordpress

  2. I discovered with you the jamstakJAMstack principle, the most important is that it is staticlystatically rendered, using gitGit as backup. So:

  • if you are using reactReact in the runtime phase, it is not jamstackJAMstack,
  • but if you use it at compile time and deliver rendered htmlHTML content to your production httpHTTP server, it is jamstackJAMstack.

Here is a linkan article stating that the most important is having static files, not only JSJavaScript, calling "shamstack" "SHAMstack": https://css-tricks.com/jamstack-more-like-shamstack/JAMstack? More like SHAMstack

I have used, for example, static pages of githubGitHub using jekyllJekyll (the default on githubGitHub) and markdown. The htmlHTML content is rendered on the commit.

  1. "Markup" is for markup language such as Markdown, but maybe also all other language, ascidoc, etc. . With jamstack we have the constraint, and advantage, that it is static rendered, as opposite to other CMS like wordpress

  2. I discovered with you the jamstak principle, the most important is that it is staticly rendered, using git as backup. So:

  • if you are using react in runtime phase it is not jamstack,
  • but if you use it at compile time and deliver rendered html to your production http server, it is jamstack.

Here is a link stating that the most important is having static files, not only JS, calling "shamstack" : https://css-tricks.com/jamstack-more-like-shamstack/

I have used for example static pages of github using jekyll (the default on github) and markdown. The html is rendered on the commit.

  1. "Markup" is for a markup language such as Markdown, but maybe also all other languages, AsciiDoc, etc. With JAMstack we have the constraint, and advantage, that it is static rendered, as opposite to other CMSes, like wordpress

  2. I discovered with you the JAMstack principle, the most important is that it is statically rendered, using Git as backup. So:

  • if you are using React in the runtime phase, it is not JAMstack,
  • but if you use it at compile time and deliver rendered HTML content to your production HTTP server, it is JAMstack.

Here is an article stating that the most important is having static files, not only JavaScript, calling "SHAMstack": JAMstack? More like SHAMstack

I have used, for example, static pages of GitHub using Jekyll (the default on GitHub) and markdown. The HTML content is rendered on the commit.

Formulation for jamstack
Source Link
pdem
pdem
  • 4k
  • 1
  • 26
  • 39

  1. "Markup" is for markup language such as Markdown, but maybe also all other language, ascidoc, etc. , with. With jamstack we have the contraintconstraint, and advantage, that it is static rendered, as opposite to other CMS like wordpress

  2. I discovered with you the jamstak principle, the most important is that it is staticly rendered, using git as backup. So:

  • if you are using react in runtime phase it is not jamstack,
  • but if you use it at compile time and deliver rendered html to your production http server, it is jamstack.

Here is a link stating that the most important is having static files, not only JS, calling "shamstack" : https://css-tricks.com/jamstack-more-like-shamstack/

I have used for example static pages of github using jekyll (the default on github) and markdown. The html is rendered on the commit.

  1. "Markup" is for markup language such as Markdown, but maybe also all other language, ascidoc, etc. , with the contraint, and advantage, that it is static rendered, as opposite to other CMS like wordpress

  2. I discovered with you the jamstak principle, the most important is that it is staticly rendered, using git as backup. So:

  • if you are using react in runtime phase it is not jamstack,
  • but if you use it at compile time and deliver rendered html to your production http server, it is jamstack.

Here is a link stating that the most important is having static files, not only JS, calling "shamstack" : https://css-tricks.com/jamstack-more-like-shamstack/

I have used for example static pages of github using jekyll (the default on github) and markdown. The html is rendered on the commit.

  1. "Markup" is for markup language such as Markdown, but maybe also all other language, ascidoc, etc. . With jamstack we have the constraint, and advantage, that it is static rendered, as opposite to other CMS like wordpress

  2. I discovered with you the jamstak principle, the most important is that it is staticly rendered, using git as backup. So:

  • if you are using react in runtime phase it is not jamstack,
  • but if you use it at compile time and deliver rendered html to your production http server, it is jamstack.

Here is a link stating that the most important is having static files, not only JS, calling "shamstack" : https://css-tricks.com/jamstack-more-like-shamstack/

I have used for example static pages of github using jekyll (the default on github) and markdown. The html is rendered on the commit.

Source Link
pdem
pdem
  • 4k
  • 1
  • 26
  • 39