Koos Looijesteijn
@kooslooijesteijn.net
Design, Berlin, climate action, web development
I made one and found that the CSS gets quite complicated if:
- You have separate HTML for the horizontal and hamburger styled situation
- Have submenus in the nav
It worked out in the end, but I hope there are ways to do a simpler implementation than I did:
- You have separate HTML for the horizontal and hamburger styled situation
- Have submenus in the nav
It worked out in the end, but I hope there are ways to do a simpler implementation than I did:
September 11, 2025 at 10:56 AM
I made one and found that the CSS gets quite complicated if:
- You have separate HTML for the horizontal and hamburger styled situation
- Have submenus in the nav
It worked out in the end, but I hope there are ways to do a simpler implementation than I did:
- You have separate HTML for the horizontal and hamburger styled situation
- Have submenus in the nav
It worked out in the end, but I hope there are ways to do a simpler implementation than I did:
That save the environment by archiving your e-mails kerfuffle reminded me that ForTomorrow has a post on the climate impact of e-mail. I've updated it to make clear that your effort is better spent elsewhere.
www.fortomorrow.eu/en/blog/carb...
www.fortomorrow.eu/en/blog/carb...
August 19, 2025 at 12:04 PM
That save the environment by archiving your e-mails kerfuffle reminded me that ForTomorrow has a post on the climate impact of e-mail. I've updated it to make clear that your effort is better spent elsewhere.
www.fortomorrow.eu/en/blog/carb...
www.fortomorrow.eu/en/blog/carb...
So apparently Codeberg is not the place to move my personal website's repo to.
August 13, 2025 at 3:15 PM
So apparently Codeberg is not the place to move my personal website's repo to.
Hey people with websites:
I noticed that the URL inspector of the Google Search Console rather consistently claims a 'URL is not on Google', while anyone can actually find it using Google Search.
Why?!
#seo #google #webadmin #webmaster
I noticed that the URL inspector of the Google Search Console rather consistently claims a 'URL is not on Google', while anyone can actually find it using Google Search.
Why?!
#seo #google #webadmin #webmaster
July 25, 2025 at 1:09 PM
Hey people with websites:
I noticed that the URL inspector of the Google Search Console rather consistently claims a 'URL is not on Google', while anyone can actually find it using Google Search.
Why?!
#seo #google #webadmin #webmaster
I noticed that the URL inspector of the Google Search Console rather consistently claims a 'URL is not on Google', while anyone can actually find it using Google Search.
Why?!
#seo #google #webadmin #webmaster
Google Zero seems to be real. Google is still the biggest referrer to my blog, but it seems to do its best to become less relevant.
I understand that many people feel it's convenient to see answers to their questions as an AI-generated summary above the search results.
#seo #google
I understand that many people feel it's convenient to see answers to their questions as an AI-generated summary above the search results.
#seo #google
June 2, 2025 at 9:41 AM
Be careful if you're still using VS Code. The latest update changed the settings for Copilot, so if you disabled Copilot Autocomplete before, it will be turned on again.
It 'autocompleted' a change in a CSS class list by duplicating a bunch of lines that followed it. I almost deployed the mistake
It 'autocompleted' a change in a CSS class list by duplicating a bunch of lines that followed it. I almost deployed the mistake
May 9, 2025 at 7:24 AM
Be careful if you're still using VS Code. The latest update changed the settings for Copilot, so if you disabled Copilot Autocomplete before, it will be turned on again.
It 'autocompleted' a change in a CSS class list by duplicating a bunch of lines that followed it. I almost deployed the mistake
It 'autocompleted' a change in a CSS class list by duplicating a bunch of lines that followed it. I almost deployed the mistake
USP number 1: "Design responsively with breakpoints"
But I thought we were all doing flex and grid layouts now?
Media queries a.k.a. breakpoints are a last resort every designer and developer should avoid.
Web design is fluid. Always has been. Even before 'responsive' was a thing.
But I thought we were all doing flex and grid layouts now?
Media queries a.k.a. breakpoints are a last resort every designer and developer should avoid.
Web design is fluid. Always has been. Even before 'responsive' was a thing.
May 8, 2025 at 9:26 AM
USP number 1: "Design responsively with breakpoints"
But I thought we were all doing flex and grid layouts now?
Media queries a.k.a. breakpoints are a last resort every designer and developer should avoid.
Web design is fluid. Always has been. Even before 'responsive' was a thing.
But I thought we were all doing flex and grid layouts now?
Media queries a.k.a. breakpoints are a last resort every designer and developer should avoid.
Web design is fluid. Always has been. Even before 'responsive' was a thing.
If you're using adplist.org for mentoring sessions and care about your #privacy, I recommend you do the calls via another platform. They've rolled out a note-taking system that records everything said in your sessions.
May 2, 2025 at 3:51 PM
If you're using adplist.org for mentoring sessions and care about your #privacy, I recommend you do the calls via another platform. They've rolled out a note-taking system that records everything said in your sessions.
I'm trying to style a <meter> (that's a progress bar, kind of).
It requires the non-standard, browser-specific selector mess you probably know from <input type="range">. So I'm thinking, maybe I should just make the <meter> hidden but accessible and recreate the thing with two <div>s.
It requires the non-standard, browser-specific selector mess you probably know from <input type="range">. So I'm thinking, maybe I should just make the <meter> hidden but accessible and recreate the thing with two <div>s.
April 24, 2025 at 7:06 AM
I'm trying to style a <meter> (that's a progress bar, kind of).
It requires the non-standard, browser-specific selector mess you probably know from <input type="range">. So I'm thinking, maybe I should just make the <meter> hidden but accessible and recreate the thing with two <div>s.
It requires the non-standard, browser-specific selector mess you probably know from <input type="range">. So I'm thinking, maybe I should just make the <meter> hidden but accessible and recreate the thing with two <div>s.
It's a shame I'm not employed by Google, because every time I do a remote user testing session, I discover new usability issues with Google Meet.
#usertesting #usability #googlemeet #teams
#usertesting #usability #googlemeet #teams
December 13, 2024 at 2:14 PM
It's a shame I'm not employed by Google, because every time I do a remote user testing session, I discover new usability issues with Google Meet.
#usertesting #usability #googlemeet #teams
#usertesting #usability #googlemeet #teams