31–40 of 90 posts
The page has some weird horizontal scrolling going on. I think it's because the body style has both `width: 100%` and a nonzero margin. You should probably set margin and padding to zero on the body tag if you need width, or just remove the `width: 100%` (which I don't think you need?)
Original article title: “Why I Created Banner Blog”. But I honestly don’t think it explains why. You establish the problem , but don’t remark on a couple of existing alternatives that might satisfy your requirements, and more importantly, you don’t explain why you’re making it a platform , rather than just something for yourself. Because honestly, if you want to blog, running a platform for everyone and their dog… we…
Is that still true with HTTP/2 (or newer)?
Original article title: “Why I Created Banner Blog”. But I honestly don’t think it explains why. You establish the problem , but don’t remark on a couple of existing alternatives that might satisfy your requirements, and more importantly, you don’t explain why you’re making it a platform , rather than just something for yourself. Because honestly, if you want to blog, running a platform for everyone and their dog… we…
It helps with Google SEO which makes sense, as schema.org is essentially stewarded by Google.
> In theory it’s neat, sure, but in practice does anything actually use it and wouldn’t use the traditional meta tags if it weren’t there?
Yeah, for basic things like the website metadata it's redundant with meta tags. It becomes more useful when it comes to more rich types like e.g. a recipe.
But I don’t think Wordpress sucks at all. It’s great in that it’s open source, runs everywhere, is easy to use, and super extensible.
I still recommend it to people who want to blog and it works out well. It’s especially nice as it doesn’t lock you into a saas like wix or square space or lots of other $10+/month services.
Personally, I just like markdown and jekyll as it’s easy enough but git is a bit too much for normies while Wordpress works fine.
Earlier quoted context omitted.
I suggest hugo: https://gohugo.io/ Generates a completely static website from MD (and other formats) files; also handles themes (including a lot of them rendering well on mobile), and different types of content - posts, articles, etc. - depending on the theme. You can edit posts with any editor you care to for wysiwyg features. It's open source and, being completely static, cheap as fuck to self host.
I've taken a look at Hugo multiple times, and... it more complicated than I'd like. For me it really does way to much and customizing themes is way more work than I care for. Maybe it's time to see if I can make SSG ( https://romanzolotarev.com/ssg.html ) run on my Mac again, for some reason it won't render anything.
Original article title: “Why I Created Banner Blog”. But I honestly don’t think it explains why. You establish the problem , but don’t remark on a couple of existing alternatives that might satisfy your requirements, and more importantly, you don’t explain why you’re making it a platform , rather than just something for yourself. Because honestly, if you want to blog, running a platform for everyone and their dog… we…
> Well done on inlining the stylesheets. Having zero subresources has a way bigger effect on page load time than people tend to expect. Is that still true with HTTP/2 (or newer)?
But when I say “having zero subresources”, I actively mean having zero subresources. The bit that really startles people is how much faster a page with inlined scripts and styles is (up to a point, but that point is typically over a hundred kilobytes of each) than a page with subresources present in a warm cache where the browser doesn’t even need to revalidate. Letting the browser just tear through it all rather than having to mess around with caches has, as I say, a bigger effect than people normally expect.
My two thoughts going into fixing it were:
- wow, this Wordpress install kind of sucks
- imagine how much worse it would suck if it wasn't Wordpress
Because it's Wordpress, Google will help me fix all the problems. Update all the plugins and themes; disable the obsolete or broken ones. Sort out the disk space issue. Tweak a few cache settings. And she's back in business.
We (HN) can all build a blog engine. We all seem to have different ideas on how to build a blog engine. And that's fine; we can all have our own little gardens and toy systems to play with. The rest of the world is more concerned with what the actual text of the blog is, if at all. Just as "obsolete iPhone with cracked screen" is the world's most widespread phone by actual use, "slightly broken wordpress" is the world's most popular blogging engine by a long way.
Meanwhile over the horizon, the question of whether any humans will read blogs at all in an AI content / search engine world looms.