[{"data":1,"prerenderedAt":17},["ShallowReactive",2],{"$fVLmqL4prwqtT7XRsSe2-vM7EB9ChDS5nqx3QpExuxUo":3},{"slug":4,"title":5,"date":6,"description":7,"tags":8,"cover":12,"source":13,"canonical":12,"link":12,"series":12,"draft":14,"readingTime":15,"html":16},"hello-world","Hello World!","2020-05-01T00:00:00.000Z","May the JAM spark curiosity at first sight!",[9,10,11],"jamstack","netlify","devlog",null,"hanselwei.dev",false,1,"\u003Cblockquote>\n\u003Cp>May the JAM spark curiosity at first sight!\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>Hello World! I'm using JAMStack for (specifically) journal entries now! This journal entry content is built in markdown, populates vue component and served on \u003Ca href=\"https:\u002F\u002Fnetlify.com\u002F\" target=\"_blank\" rel=\"noopener\">Netlify\u003C\u002Fa>!\u003C\u002Fp>\n\u003Cp>\u003Cem>What is JAMstack? - you might ask...\u003C\u002Fem>\nIt's JavaScript, APIs, and Markup. Any project that relies on a tight coupling between client and server is not built with the Jamstack This page is not built with a server-side CMS like WordPress, Drupal, Joomla, or Squarespace!\nYou might be surprised that the content management system (CMS) is completely headless.\u003C\u002Fp>\n\u003Cp>Reasons why:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>this is super easy to setup\u003C\u002Fli>\n\u003Cli>highly responsive\u003C\u002Fli>\n\u003Cli>API first (I can integrate this later with other things!)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>note to myself: \u003C\u002Fp>\n\u003Col>\n\u003Cli>explore \u003Ca href=\"https:\u002F\u002Fjamstack.org\u002Fbest-practices\u002F\" target=\"_blank\" rel=\"noopener\">JAMStack Best Practices\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>think of creative ways to use APIs with this personal portfolio site\u003C\u002Fli>\n\u003C\u002Fol>\n",1792273070915]