Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Blog with Markdown and Git, and degrade gracefully through time

brandur.org

Post reply on HN
Print view View original

51–60 of 182 posts

Re: Blog with Markdown and Git, and degrade gracefully through time

#51

Post by wazanator »

vitorfs wrote: post #12

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…

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.

Re: Blog with Markdown and Git, and degrade gracefully through time

#52

Post by jaredcwhite »

There 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 have a bunch of Contentful clones (no disrespect to Contentful) with REST and/or GraphQL APIs.

It's bananas that if you search for Git-based CMSes you have NetlifyCMS, and…wait what? Is that all??? Forestry gets mentioned a lot because it's Git-based but that's also a proprietary SaaS. I just don't understand it. Is this a VC problem or a real blind spot for CMS entrepreneurs?

Re: Blog with Markdown and Git, and degrade gracefully through time

#53

Post by pjfin123 »

If you want something to live on the web long after you've lost interest in it static HTML/GitHub pages seems like the way to go. The chess board I built in high school to learn JavaScript is still going strong: https://github.com/PJ-Finlay/JavaScript-Chess-Board

Re: Blog with Markdown and Git, and degrade gracefully through time

#54

Post by calessian »

I run my blog using perhaps the most boring option - Wordpress, with close-but-not-quite the default theme (different fonts mostly). Outside of adding a cover image on every post and occasional footnotes, I don’t really need much.

However, that’s pretty lightweight on decisions I had to actually make to publish, and all the alternatives seem to be more involved. I wouldn’t mind migrating off WordPress, but just on the theming side that has a decent chance of involving a non-free theme, making the idea of hosting it on a public repo somewhat of a non starter...

Re: Blog with Markdown and Git, and degrade gracefully through time

#56

Post by vitorfs »

Lammy wrote: post #22
vitorfs wrote: post #12

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…

Is it slow to regenerate a single post even with Jekyll’s ‘—incremental’ mode?

yes because of a bad design decision I made to create a custom "related posts", which is a code that searches all my markdowns to pick the best pages and add to the current page. so even with `--incremental` it take quite some time to regenerate

Re: Blog with Markdown and Git, and degrade gracefully through time

#57

Post by CameronNemo »

hinkley wrote: post #46
vitorfs wrote: post #12

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…

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?

Re: Blog with Markdown and Git, and degrade gracefully through time

#58

Post by vitorfs »

dopeboy wrote: post #21
vitorfs wrote: post #12

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…

Side note - big fan of your blog. You're killing it at SEO.

hey, thanks! :D

Re: Blog with Markdown and Git, and degrade gracefully through time

#59

Post by CameronNemo »

dfinr wrote: post #55

MkDocs plus Material theme on GitHub pages is pretty sweet. Automatic dark mode, useful plugins. I migrated from WordPress, no looking back.

I cut my teeth on Hugo and mdbook, and mkdocs was a breath of fresh air. No crazy templating, no pseudo-markdown index files, and lots of flexibility in the site and page structure.

Re: Blog with Markdown and Git, and degrade gracefully through time

#60

Post by lhorie »

jaredcwhite wrote: post #52

There 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.

Post reply on HN