At my age, degrading gracefully through time is about the best I can hope for
Blog with Markdown and Git, and degrade gracefully through time
61–70 of 182 posts
Re: Blog with Markdown and Git, and degrade gracefully through time
#62I 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…
If you use "bundle exec jekyll serve" you shouldn't have too much problems locally as it just rebuilds the pages that change on every save. A minute to deploy the finished version is not terrible by any stretch for a blog IMO.
I used to think the same until I tried Hugo and it generates my site in milliseconds. Deploying from there also takes less than a second.
It is really astonishing what power our devices have and how little that power is utilised by many tool chains.
Re: Blog with Markdown and Git, and degrade gracefully through time
#63MkDocs plus Material theme on GitHub pages is pretty sweet. Automatic dark mode, useful plugins. I migrated from WordPress, no looking back.
Never heard of this but now I'm in love.
Now to figure out what I can write about.
Though I'm definitely going to use this for internal docs at work probably. Very nice.
Re: Blog with Markdown and Git, and degrade gracefully through time
#64Earlier quoted context omitted.
There was a company on here the other day talking about their product, built on top of Docker. I wish I'd bookmarked it. Their secret sauce is, effectively, partial evaluation in Docker images. They run the code to detect if any of the changes in a layer have side effects that require that layer to be rebuilt (which invariably causes every layer after to be rebuilt) I mention this because if I'm editing a single page…
Can't good old make do partial recompilation with ease?
Correct me if I'm wrong, but don't you have to formally map out all of your inputs and outputs for partial recompilation to work?
I believe the last time I touched make was to fix an exceedingly badly mapped out chain of cause and effect that would consistently compile too much and yet occasionally miss the one thing you actually needed.
Partial evaluation works out the dependencies by evaluating all of the conditional logic and seeing which inputs interact with which outputs.
Re: Blog with Markdown and Git, and degrade gracefully through time
#65I 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…
Something similar happened to me when I was using static site generators. In fact one that I was really enjoying even switched programming languages between 1.x and 2.0. 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 LibreOf…
Just want to chime in that one can use a static site generator without upgrading it. Or upgrading it infrequently.
I’m currently on Hugo 0.80.0 and who knows, it might take years before I upgrade it.
Re: Blog with Markdown and Git, and degrade gracefully through time
#66For all the (deserved) complaints people have about wordpress, it's been around since before git or markdown was even a thing. For all its faults, its been pretty resilient to time. The real reason most websites disappear is a much more human one.
Yes, if you constantly update your installation, which is the exact opposite of what this blog post is about. Otherwise you run a pretty good risk of your installation being hijacked, overtaken by spam bots or similar after a few years.
Yep. I run a few WordPress sites and the amount of maintenance with them is crazy. The plugin model makes maintenance brutal too since it's all independent devs with different release cycles, testing practices, etc.
Re: Blog with Markdown and Git, and degrade gracefully through time
#67For all the (deserved) complaints people have about wordpress, it's been around since before git or markdown was even a thing. For all its faults, its been pretty resilient to time. The real reason most websites disappear is a much more human one.
Yes, if you constantly update your installation, which is the exact opposite of what this blog post is about. Otherwise you run a pretty good risk of your installation being hijacked, overtaken by spam bots or similar after a few years.
Wordpress can be configured to receive automatic updates as soon as they're available. Plugins are a different story...
Re: Blog with Markdown and Git, and degrade gracefully through time
#68There is a problem in the CMS industry. Everyone wants to build a headless CMS to power Jamstack sites—only the content itself lives in databases and the CMS is usually a proprietary SaaS. Doesn't leverage Git for content in any way. This is deeply problematic. We should have dozens, if not hundreds of contenders for "the next WordPress" that leverage Git as a foundational aspect of content management. Instead we hav…
One explanation comes from just looking from the content creator's point of view: they kinda don't care what previous iterations of the work really look like (draft-final-v5-oct27-FINAL.doc anyone?) The things a content creator might be more interested in aren't really core git strengths: SEO, publishing schedules, editorial back-and-forth, social media, etc.
"SEO, publishing schedules, editorial back-and-forth, social media"
Hmm, not really core PostgreSQL strengths either. What am I missing?
Re: Blog with Markdown and Git, and degrade gracefully through time
#69Earlier quoted context omitted.
Yes, if you constantly update your installation, which is the exact opposite of what this blog post is about. Otherwise you run a pretty good risk of your installation being hijacked, overtaken by spam bots or similar after a few years.
Wordpress can be configured to receive automatic updates as soon as they're available. Plugins are a different story...
WordPress core yes, and it's pretty safe, but if you use many plugins (which most people do) that gets a lot riskier. Premium plugs are pretty safe but still I've had stuff break.
Re: Blog with Markdown and Git, and degrade gracefully through time
#70I'm using pandoc for my site (https://www.dharmab.com). It's a bio/profile, not a blog, but I think it's OK (other than I'm lazy and haven't auto-generated smaller resolution images for mobile).