I started my blog about python/django ( https://simpleisbetterthancomplex.com ) using Jekyll and hosting on Github Pages and it was pretty good to get started because back then I wasn't sure if I would keep it up or not. After a year or so I migrated to a 5 USD droplet on Digital Ocean (back then GH Pages didn't offer https for custom domains) and integrated with Github webhooks to automate the deployment when pushin…
Blog with Markdown and Git, and degrade gracefully through time
21–30 of 182 posts
Re: Blog with Markdown and Git, and degrade gracefully through time
#22I started my blog about python/django ( https://simpleisbetterthancomplex.com ) using Jekyll and hosting on Github Pages and it was pretty good to get started because back then I wasn't sure if I would keep it up or not. After a year or so I migrated to a 5 USD droplet on Digital Ocean (back then GH Pages didn't offer https for custom domains) and integrated with Github webhooks to automate the deployment when pushin…
Re: Blog with Markdown and Git, and degrade gracefully through time
#23I started my blog about python/django ( https://simpleisbetterthancomplex.com ) using Jekyll and hosting on Github Pages and it was pretty good to get started because back then I wasn't sure if I would keep it up or not. After a year or so I migrated to a 5 USD droplet on Digital Ocean (back then GH Pages didn't offer https for custom domains) and integrated with Github webhooks to automate the deployment when pushin…
Since that time I look for the people and community behind the project, and try to find signs of stability and long-term care. After that I look at open formats rather than open and flexible architecture-chains. For example, I'd rather use my LibreOffice HTML template and simple PHP controller on a more monolithic (but open) platform than connect a bunch of technologies together to create a build process with a bunch of moving, quickly developing, interdependent parts.
Not sure it's the best answer, but it has worked better to use more monolithic software, even blogging software that's been in steady, if slow development since the early 2000s...
Re: Blog with Markdown and Git, and degrade gracefully through time
#24https://github.com/mauidude/go-readability
This is the kind of thing pocket/instapaper do to extract the main content from a page in a format that's easier to read (and also probably to programmatically modify)
Re: Blog with Markdown and Git, and degrade gracefully through time
#25The real reason most websites disappear is a much more human one.
Re: Blog with Markdown and Git, and degrade gracefully through time
#26Earlier quoted context omitted.
why?
"free/opensource" -> !M$
[0] Also, thanksnotreally for cherry-picking and putting words in my mouth with your use of `!M$`, screw you too.
Re: Blog with Markdown and Git, and degrade gracefully through time
#27My co-author and I use Markdown and Git as the author suggests, and one of the best things is that between simple CI/CD pipelines and effortless scaling of a static site, we don't need to do any technical work so there's no friction on my lifestyle. We've been writing for almost a year now, 4+ posts a month, and 99% of that "work" has just been writing.
Writing with a partner helps a ton as well.
Re: Blog with Markdown and Git, and degrade gracefully through time
#28I wish people would stop using github as a swiss knife CDN (free hosting, hooks, history through git repo, etc) and build higher altitude solution that could leverage git/MD/whatever but with free/opensource/selfhosted/alternative tools (like gitea instead of github and minio instead of S3 for instance).
> build higher altitude solution that could leverage git/MD/whatever but with free/opensource/selfhosted/alternative tools Not that I disagree with this, but that goes almost directly against "Mak[ing] that source public via GitHub or another favorite long-lived, erosion-resistant host. Git’s portable, so copy or move repositories as you go." Any self-hosted service or solution is going to not be erosion-resistant by…
Of course the end-result is easy to move out but the build pipeline is more dependent on GH.
Not that it matters but it could be cool too to pipe SSG's output through a managed VPS just to show you don't need Github to host your static files.
Re: Blog with Markdown and Git, and degrade gracefully through time
#29I used to have my blog source on GitHub, but then it turned out I didn't want my half-finished works-in-progress public. To use a private repository would rather defeat the point; using a private repo and a public fork is inviting confusion. Now I just use a private repo on my own server, cloned to my dev machine. Does anyone have a usable solution for that problem?