Some of my favourite "digital garden" websites: - http://100r.co/ - https://wiki.xxiivv.com/site/home.html Made by the same people, but the second is more technical. I can't deny that there is a certain sense of visiting someone's home (in this case someone's sailboat ) that is completely absent in the modern, sterile and utilitarian blog format. It is a pleasure to get lost following interesting links, chancing upon…
How the blog broke the web (2017)
91–100 of 120 posts
Re: How the blog broke the web (2017)
#92Earlier quoted context omitted.
I do this, too. My site https://benovermyer.com has a blog, but the more interesting stuff is all the _other_ pages. The most frequently updated page is the list of books I've read. Do you have a "digital garden" site?
Not yet, but I've been hacking on Kirby to create a regular blog-style personal website and I just want to throw everything out and have a way to host pure Markdown. Someone recommended PicoCMS elsewhere. That's my weekend sorted. You are one step away from a garden. Move those links out of "KB" and collect them in the home page. RSS is a bit harder to do on that type of websites. Here's my crappy definition of a dig…
Re: How the blog broke the web (2017)
#93Some of my favourite "digital garden" websites: - http://100r.co/ - https://wiki.xxiivv.com/site/home.html Made by the same people, but the second is more technical. I can't deny that there is a certain sense of visiting someone's home (in this case someone's sailboat ) that is completely absent in the modern, sterile and utilitarian blog format. It is a pleasure to get lost following interesting links, chancing upon…
I do this, too. My site https://benovermyer.com has a blog, but the more interesting stuff is all the _other_ pages. The most frequently updated page is the list of books I've read. Do you have a "digital garden" site?
Re: How the blog broke the web (2017)
#94There are many suspects in the "who killed the web" mystery but blogs are low down on that list. The real problem is that building a web page is much, much harder today than it was 25 years ago. Back then you could slap together some HTML, add a picture and an under-construction GIF and call it a day. Everyone with their huge 800x600 monitors would see the same thing. Today you have to take into account not just moni…
Re: How the blog broke the web (2017)
#95Earlier quoted context omitted.
> I still see personal websites that are almost unreadable on small phones, for instance. My personal website is like that and I’ve made no effort to improve the phone experience. I really don’t care if phone users have access or not, on every other device it looks fine. It’s a personal website, if it looks good on my machine that’s enough for me.
That was my opinion for a while as well. It depends on your audience but about 50% of hits to my site come from one mobile device or another and in the end I felt I had to put the effort in to support them.
Re: How the blog broke the web (2017)
#96There are many suspects in the "who killed the web" mystery but blogs are low down on that list. The real problem is that building a web page is much, much harder today than it was 25 years ago. Back then you could slap together some HTML, add a picture and an under-construction GIF and call it a day. Everyone with their huge 800x600 monitors would see the same thing. Today you have to take into account not just moni…
> I still see personal websites that are almost unreadable on small phones, for instance. My personal website is like that and I’ve made no effort to improve the phone experience. I really don’t care if phone users have access or not, on every other device it looks fine. It’s a personal website, if it looks good on my machine that’s enough for me.
If the content is too small on a phone, you can always just zoom in and scroll horizontally as well as vertically. Unless the creator of the site decides to "helpfully" create a phone version of their site in which case you have to go find a computer to use the site or download some app. A great example of this is Reddit which goes out of its way to make their "mobile site" unusable to force people to download the Reddit app so they can more easily spy on you.
I do think web sites should scale properly to different window sizes which means not using certain formatting misfeatures that force certain elements to always appear on the screen or that make your menu unusable on a touch screen. That isn't hard to do because you have to make a deliberate bad design choice to make your site unusable on smaller resolutions. A well-designed web site will also work perfectly well on Lynx or a screen reader without any additional work.
Re: How the blog broke the web (2017)
#97Earlier quoted context omitted.
I do this, too. My site https://benovermyer.com has a blog, but the more interesting stuff is all the _other_ pages. The most frequently updated page is the list of books I've read. Do you have a "digital garden" site?
Not yet, but I've been hacking on Kirby to create a regular blog-style personal website and I just want to throw everything out and have a way to host pure Markdown. Someone recommended PicoCMS elsewhere. That's my weekend sorted. You are one step away from a garden. Move those links out of "KB" and collect them in the home page. RSS is a bit harder to do on that type of websites. Here's my crappy definition of a dig…
https://joeldare.com/how-i-use-github-as-my-blogging-platfor...
Re: How the blog broke the web (2017)
#98I too lament how much more difficult it is to build something completely independently than it was then, while rejoicing at how much more accessible building something is for more people, even if it means leaning on existing infrastructure.
Re: How the blog broke the web (2017)
#99That sounds weirdly gatekeepy. How dare those new peasants not slave away in HTML mines before they can get their content shown!
Re: How the blog broke the web (2017)
#100Earlier quoted context omitted.
> I still see personal websites that are almost unreadable on small phones, for instance. My personal website is like that and I’ve made no effort to improve the phone experience. I really don’t care if phone users have access or not, on every other device it looks fine. It’s a personal website, if it looks good on my machine that’s enough for me.
I do a good bit of my web browsing on my phone and I hate those web sites that are "optimized for phones" and thus typically lacking content and features. You can sometimes disable them with desktop mode but usually those sites ignore that and force the "mobile site" version. If the content is too small on a phone, you can always just zoom in and scroll horizontally as well as vertically. Unless the creator of the si…
So there's always a mobile-only, a screen-only, a mobile-first, a screen-first and only rarely a general media web. It will depend on the author and the intended audiences.