3 ms·
I've had sites where I just write in Markdown and rsync it to a webserver. All pages were rendered dynamically. The advantage was that I set it up once then lit
by suprjami 3y ago
I've had sites where I just write in Markdown and rsync it to a webserver. All pages were rendered dynamically. The advantage was that I set it up once then literally never care about a website again and just write in my beloved Markdown.
It was great. Until the webhost took away PHP anyway.
- flohofwoe 3y agoGH Actions (or any othe CI service) can do the same workflow though. Commit and push markdown, GH Action starts server-side, converts the markdown to html with a static site generator of choice, and uploads to webhoster. If you use Jekyll as static site generator and GH Pages for hosting, it even works out of the box (eg no GH Action tinkering needed, just flip a switch in the GH project settings) But arguably, a local static site generator workflow works just as well (convert to html locally and upload those files to web hoster instead).
- suprjami 3y agoI have since moved to GitHub Pages for my main site, but mine was even simpler than that: https://github.com/superjamie/emdee https://github.com/superjamie/emdee