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

151–160 of 182 posts

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

#151

Post by NetOpWibby »

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…

I feel your pain.

I’d make a simple static blog generator but then grow tired of some shortcomings, which then led to abandonment.

My current blog has an HTML rendered homepage but all the posts are text files. https://blog.webb.page

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

#152

Post by afarrell »

SPBS wrote: post #149

I feel like the author makes a good point, but it does not solve the original problem he was describing. The only reason why those websites disappeared is because the owner was no longer interested in maintaining it. It's a human factor, not a technological one. Even if they had written their files in markdown and git, the website would have disappeared anyway if they stopped paying the domain/hosting fees. Now if yo…

> a human factor, not a technological one

I think the author's point is to highlight the relationship between technological and human factors. Git+markdown has a better user experience if your user is a developer who uses git every day.

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

#153

Post by FrontAid »

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…

Maybe FrontAid CMS might be interesting to you, even though it is also proprietary. FrontAid CMS is similar to Forestry, but stores all your content in JSON instead of Markdown. It is therefore better applicable to (web) applications in addition to simple blogs. https://frontaid.io/

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

#155

Post by estaseuropano »

AmericanChopper wrote: post #150
estaseuropano wrote: post #145

I disagree with the core tenet of the article. Does everything really have to live forever? Most blogs are probably not worth preserving, just like most speeches in history are not worth preserving. Most books are never reprinted. Time is a great filter. Yes important stuff gets lost but not each thought or word is worth preserving and not every moment in life needs to be captured and kept for posterity. I would pref…

Ancient Roman graffiti is seen as being valuable enough that significant time and resource has been spent on studying it. The anthropological value of it seems obvious to me. Perhaps low effort thought-leadership or social media drivel has little contemporary value, but it could be a fantastic historical resource. The selection bias of history that was chosen to be preserved (and the people who were doing the choosin…

Absolutely agree. At the same time, this roman graffiti is valuable because there's not that much of it and not much other records of the time. We have more from Rome than most other times and places in history, but overall no much. There are probably more words of Linkedin 'thought leaders' publisher per hour than all the the text that has reached us from Rome.

I would still argue that we live in a time where many things are needlessly preserved (not to mention the privacy implications...).

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

#156

Post by httpsterio »

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…

Some static generators like eleventy and Gatsby offer partial builds, only building the new posts etc. which should be considerably faster. Another thing would be to run an empty version of your site with only the text you're working on and when it's done, moving it to the proper site and building it then

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

#157

Post by eracle1 »

staysaasy wrote: post #110
yhoiseth wrote: post #89

Earlier quoted context omitted.

Love your blog!

Thanks for reading! Really appreciate it. It's been quite a journey and I honestly credit the tech stack with making it so easy to write.

What's your tech stack?

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

#158

Post by eracle1 »

MrPowers wrote: post #132
grandvoye wrote: post #27

IMO the biggest barrier to blogging (and the cause of most blogs dying) is inconvenience, and minimizing that if the biggest advantage of Markdown + Git. If there's any inconvenience at all, it naturally drags on the process of writing, and writing takes enough time and focus that if there's any friction it's too easy to push things off to the next day. My co-author and I use Markdown and Git as the author suggests,…

Any suggestions for static site generators / where to host? I'm thinking about starting a new blog with Hugo / Digital Ocean. I have a popular Spark blog on Wordpress ( https://mungingdata.com/ ) and can relate to your sentiment that any inconvenience can hold up the writing process. Your post is motivating me to streamline my publishing process.

What's your tech stack?

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

#160

Post by rapnie »

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…

> if you search for Git-based CMSes you have NetlifyCMS, and…wait what? Is that all???

There are some more. I know of Grav which I intend to use migrating from NetlifyCMS. It has flat-file storage and Git connectivity. I think it can be installed on my shared hosting provider by just unpacking the thing (I don't have Composer / shell access).

https://getgrav.org/features

Post reply on HN