#100days 65 - Doing some catch up with multiple updates today. I fixed the where page on my new site as well as updating some of the styles.
I think it's more or less ready to go now, so it might be time to launch it after a couple more little tweaks.
#100days 64 - Updated the 404 code from yesterday to use my own custom component instead of the default Next.js one.
I'm also heading off for a little holiday tomorrow, hopefully I'll be able to keep up this challenge, but I'm not too bothered if I miss a few days.
#100days 63 - updated my next js site to better handle fallbacks and dynamic routes, so valid post urls that 404 will actually 404 and posts that are dynamically loaded will show a loading indicator.
#100days 62 - Made a little update to my new site to fix the navigation sizing on large screens.
#100days 61 - Fixed a few styles on my new site so that previews of articles on my archive pages look more similar to the rest of the posts.
#100days 60 - Made a small but long overdue change to my site, so that it only sends me notifications about new webmentions. My notifications were filling up with duplicate mentions because of people sending them every time they build their site (which is totally fine)
#100days 59 - Made a decent amount of progress on the PostrChild extension as my IndieWebCamp project, but still not very near ready for release 😣
What I did manage to do was: make the autocompletion system for emoji, blocks and contacts much more reliable, fix the button to easily reply to any page and some updates to inserting and uploading images.
I still have a lot left to do but I am really hoping I now have the biggest hurdles out of the way and future development will go more smoothly.
#100days 57 - Updated some more styles on the next version of my site and made pretty much all images lazyloaded. So my pages of photos should be a bit more performant 😃
#100days 56 - Also been working on my updated site as well. Managed to completely remove styled components from it now and converted everything to more plain sass.
I'm sure there are little things that have broken or can be improved but I definitely prefer this setup to styled components - I can see the appeal but I find them to be limiting or hard to use when you hit edge cases that don't really fit in the "component" mold.
#100days 55 - So my failure with the PostrChild extension yesterday was not so much of a failure as I thought.
Turns out that web extensions don't support having both a "browser action" and a "page action" in one extension. But it's no so bad, it was just providing a one click alternative to a 2 click flow.