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

Show HN: Simple-blogger – blog generated from GitHub project READMEs

github.com

Post reply on HN
Print view View original

11–20 of 20 posts

Re: Show HN: Simple-blogger – blog generated from GitHub project READMEs

#11

Post by speedgoose »

pcr910303 wrote: post #6

This is... at best not favorable for a lot of static blogs. For people who didn't understand what this is doing - it's using client-side JS to load the markdown files from GitHub, compiling it to HTML and displaying it on the browser. Looks like the advantage of this is that it's a one-time setup - you don't need to build the files every time you commit, you can add your markdown files on GitHub and it automatically…

Are non-js users a thing? I feel like no non technical user disables javascript and the few who do can enable it again if required.

Re: Show HN: Simple-blogger – blog generated from GitHub project READMEs

#12

Post by maelito »

speedgoose wrote: post #11
pcr910303 wrote: post #6

This is... at best not favorable for a lot of static blogs. For people who didn't understand what this is doing - it's using client-side JS to load the markdown files from GitHub, compiling it to HTML and displaying it on the browser. Looks like the advantage of this is that it's a one-time setup - you don't need to build the files every time you commit, you can add your markdown files on GitHub and it automatically…

Are non-js users a thing? I feel like no non technical user disables javascript and the few who do can enable it again if required.

Non-js users can read the content in GitHub

Re: Show HN: Simple-blogger – blog generated from GitHub project READMEs

#13

Post by bArray »

speedgoose wrote: post #11
pcr910303 wrote: post #6

This is... at best not favorable for a lot of static blogs. For people who didn't understand what this is doing - it's using client-side JS to load the markdown files from GitHub, compiling it to HTML and displaying it on the browser. Looks like the advantage of this is that it's a one-time setup - you don't need to build the files every time you commit, you can add your markdown files on GitHub and it automatically…

Are non-js users a thing? I feel like no non technical user disables javascript and the few who do can enable it again if required.

> Are non-js users a thing?

We exist! Speaking for myself, it's a speed and privacy thing.

> I feel like no non technical user disables javascript and

> the few who do can enable it again if required.

Generally I'm not going to enable JS just to use your blog, especially as doing so usually allows a tonne of tracking scripts to run.

Also there is something extremely backwards about forcing every user to translate your content rather than you doing this and serving it statically. Think about the collective energy wastage if every website did this.

Re: Show HN: Simple-blogger – blog generated from GitHub project READMEs

#15

Post by nindalf »

johnonolan wrote: post #10
nindalf wrote: post #9

Earlier quoted context omitted.

> you don’t need to build the files every time you commit. Is this a big advantage? I write an article in markdown and push to my server. The server’s post-commit hook automatically runs a static site generator. It takes less than a second to run each time. It took me half an hour to set this up[1], https included. Importantly, since it’s a static site with no client side JS, it’s faster and better for SEO. Anecdotal…

Whether you choose to use clientside JS isn't related to any platform. Lots of people conflate this. They build ostensibly a totally empty scaffold site with an SSG and say "look how fast it is" - but the truth is if you built that same site with really any platform in the world, it would be just as fast. Ghost doesnt require any clientside JS of any kind, it's totally user choice if/when they want to have that. Yest…

The speed comparison between my blog on Ghost and my blog on Hugo (an SSG) indicated that it is faster on Hugo. Note that I’m comparing time taken to serve the website, not time taken to generate files.

The same content with the same URLs is ranked higher by Google after the switch, suggesting that Google prefers this.

Re: Show HN: Simple-blogger – blog generated from GitHub project READMEs

#16

Post by speedgoose »

bArray wrote: post #13
speedgoose wrote: post #11

Earlier quoted context omitted.

Are non-js users a thing? I feel like no non technical user disables javascript and the few who do can enable it again if required.

> Are non-js users a thing? We exist! Speaking for myself, it's a speed and privacy thing. > I feel like no non technical user disables javascript and > the few who do can enable it again if required. Generally I'm not going to enable JS just to use your blog, especially as doing so usually allows a tonne of tracking scripts to run. Also there is something extremely backwards about forcing every user to translate you…

Yes I know you do. I also disable JavaScript by default on my mobile. But we are on Hacker News, we don't represent the average user.

Re: Show HN: Simple-blogger – blog generated from GitHub project READMEs

#17

Post by bArray »

speedgoose wrote: post #16
bArray wrote: post #13

Earlier quoted context omitted.

> Are non-js users a thing? We exist! Speaking for myself, it's a speed and privacy thing. > I feel like no non technical user disables javascript and > the few who do can enable it again if required. Generally I'm not going to enable JS just to use your blog, especially as doing so usually allows a tonne of tracking scripts to run. Also there is something extremely backwards about forcing every user to translate you…

Yes I know you do. I also disable JavaScript by default on my mobile. But we are on Hacker News, we don't represent the average user.

Well, also remember that a tonne of internet is using a very low-bandwidth connection (sometimes much less than dial-up speeds). I imagine that without no-script installed a bunch of the web simply can't be used.

Re: Show HN: Simple-blogger – blog generated from GitHub project READMEs

#18

Post by ulisesrmzroche »

speedgoose wrote: post #16
bArray wrote: post #13

Earlier quoted context omitted.

> Are non-js users a thing? We exist! Speaking for myself, it's a speed and privacy thing. > I feel like no non technical user disables javascript and > the few who do can enable it again if required. Generally I'm not going to enable JS just to use your blog, especially as doing so usually allows a tonne of tracking scripts to run. Also there is something extremely backwards about forcing every user to translate you…

Yes I know you do. I also disable JavaScript by default on my mobile. But we are on Hacker News, we don't represent the average user.

Even within HN, yall are a very small faction.

Truth is people actually like JS, without it, I bet they wouldn’t even use computers

Re: Show HN: Simple-blogger – blog generated from GitHub project READMEs

#19

Post by captn3m0 »

I do this for automatically generating pages on my personal website for various projects via Jekyll.

So https://captnemo.in/ideas/ loads the README from https://github.com/captn3m0/ideas.

If you'd like to replicate, use this layout[0], and create a post with just a few bits of frontmatter[1]

The obvious advantage is that I can now serve READMEs for various projects within my website, without having to worry about updating it in any way. The READMEs stay in their respective projects. Its all done client side though, so not recommended if you'd like to use the page on your website as the primary. The one issue is that internal links in markdown don't work easily.

[0]: https://github.com/captn3m0/captn3m0.github.com/blob/master/...

[1]: https://github.com/captn3m0/captn3m0.github.com/blob/master/...

Re: Show HN: Simple-blogger – blog generated from GitHub project READMEs

#20

Post by depthfirst »

nindalf wrote: post #9
pcr910303 wrote: post #6

This is... at best not favorable for a lot of static blogs. For people who didn't understand what this is doing - it's using client-side JS to load the markdown files from GitHub, compiling it to HTML and displaying it on the browser. Looks like the advantage of this is that it's a one-time setup - you don't need to build the files every time you commit, you can add your markdown files on GitHub and it automatically…

> you don’t need to build the files every time you commit. Is this a big advantage? I write an article in markdown and push to my server. The server’s post-commit hook automatically runs a static site generator. It takes less than a second to run each time. It took me half an hour to set this up[1], https included. Importantly, since it’s a static site with no client side JS, it’s faster and better for SEO. Anecdotal…

Thanks for pointing out SEO use case; I hadn't thought of it.

To reiterate my use case:

- no maintenance: the site is served from github, so dont have to maintain/pay for a server

- deduplication of work: dont have to write/sync a blog post and a project README for a given project.

Regarding SEO, since all content in on github, a search engine might index github content and make it discoverable that way.

Post reply on HN