Post 899090 by acrylicjam@mastodon.sdf.org
 (DIR) More posts by acrylicjam@mastodon.sdf.org
 (DIR) Post #899090 by acrylicjam@mastodon.sdf.org
       2018-11-01T07:39:53Z
       
       0 likes, 0 repeats
       
       I'm a total newbie re web design. I was wondering: is it such a bad idea to have a static website with no CMS (not even pelican)? If the site is just updated now-and-then so can be pushed to easily by git, etc.I haven't yet come across the 'best practice' for turning sites (HTML/CSS/JS) into something digestible by a CMS whilst retaining the design in this way (or is this actually possible/easy?) #webdesign #web #bootstrap #html #css
       
 (DIR) Post #899091 by tomasino@mastodon.sdf.org
       2018-11-01T10:02:20Z
       
       0 likes, 0 repeats
       
       @acrylicjam yes. No CMS is perfectly fine. I'd say it's the case with 90% of the sites I build. A CMS is handy if the site needs to be regularly updated by non technical people, but it introduces a lot of overhead and (in the case of server side CMS) security concerns. You don't need it by default
       
 (DIR) Post #899112 by acrylicjam@mastodon.sdf.org
       2018-11-01T10:05:30Z
       
       0 likes, 0 repeats
       
       @tomasino you are an endless source of useful support and info, tomasino - thx so much for the reply! I also like how assuring you are re my own 'DIY' approach to these things. I often do them a certain way thinking to myself "I'm sure it can't be done like this in industry..." but likewise thinking "...but this solution seems the simplest and most effective for my needs" so I'm constantly a bit torn between those two tensions - but you help reassure me to keep it as simple as I need.