The latest articles on DEV Community by Matt Bryant (@t_mattb). https://dev.to/t_mattb https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F62231%2Fbe9a95d2-2885-43f4-ac08-f9a3bcb8d543.jpg https://dev.to/t_mattb en Matt Bryant Tue, 13 Mar 2018 12:14:09 +0000 https://dev.to/t_mattb/explain-static-generated-vs-pure-html-sites-like-im-five--4c18 https://dev.to/t_mattb/explain-static-generated-vs-pure-html-sites-like-im-five--4c18 <p>Good people of the interwebs, please sort me out here. So, if the ultimate goal of static site generators (SSGs) is to output html files, then wouldn't it make sense to just create/write and then upload the HTML, CSS, and Javascript files directly to a host server vs. creating them in some kind of markdown language and framework first? Is the only reason for using markdown and using a generator like Jekyll, Hugo, etc, is because of readability issues when it comes to writing and reading the code? In other words, I could just create straight up HTML, CSS, and Javascript files, them load them to a server. Why should I go through the extra effort, time, etc. to introduce another language and framework into this when the ultimate output is the same?</p> explainlikeimfive html ssg markdown