Re:JAMstack? More Like SHAMstack
by mc3 on Tuesday November 19, 2019 @05:38PM
(#21579089)
I am a big fan of JAMstack for side projects because you just upload them to Netlify or similar and leave them there for years without worrying about maintaining them too much.
I have a pet side project stack that consists of:
* Netlify for CI/hosting
* Github for Source Control hosting.
* Elm language for a sane language to compile to JS.
* Vanilla CSS and my favourite minimal CSS framework of the day e.g. milligram.
* Local storage and download/upload functions for backup. Good enough for an MVP.
* Longer term, for storage I am thinking about Dropbox integration, although I might give in and host a little service but this shouldn't need to change much between projects.
Calling it SHAMstack is odd, because the J as in JavaScript is more relevant than the fact it is statically hosted. JS is needed to do a lot of heavy lifting in lieu of having a back end. Although I guess APIs implies you must be using JS.
I have a pet side project stack that consists of:
* Netlify for CI/hosting
* Github for Source Control hosting.
* Elm language for a sane language to compile to JS.
* Vanilla CSS and my favourite minimal CSS framework of the day e.g. milligram.
* Local storage and download/upload functions for backup. Good enough for an MVP.
* Longer term, for storage I am thinking about Dropbox integration, although I might give in and host a little service but this shouldn't need to change much between projects.
Calling it SHAMstack is odd, because the J as in JavaScript is more relevant than the fact it is statically hosted. JS is needed to do a lot of heavy lifting in lieu of having a back end. Although I guess APIs implies you must be using JS.