Category: 100days page 9

#100days 21 - Basically no progress on the PostrChild extension, I think (but don't know for sure) that is an issue with the react portal system. Calling a function defined outside a portal from inside a portal and the state variables are always their initial value. I tried using custom js events to get around it as well as setting up some better global state management.

#100days 20 - small step forward and a smaller step back. I tried adding a ctrl+enter shortcut to publish with the PostrChild extension. The actual shortcut works and runs the publish function, but for some reason when it is run via the shortcut it doesn't pick up the content. Something to try and figure out tomorrow!

#100days 19 - Small but good progress today on the PostrChild extension, the new post from anywhere button works like a charm. I hit that and it opens my website and loads the editor really quickly.

But I didn't manage to get the reply button working just yet. It requires passing some data into the newly created page, which I haven't quite fully figure out yet. Hopefully tomorrow though πŸ˜ƒ

#100days 18 - Just a small one. I setup the PostrChild extension to automatically save the new post url, which means that the extension can launch a new post editor from any page. Although I seem to have issues with the popup being really slow now (I think a bad react hook), so it's not fully tested yet.

#100days 17 - The next.js migration continues! I'm actually feeling quite close to having something working now, I fixed a lot of things that were just straight up broken today like watch posts and seo titles.

There is still quite a lot that is missing - but not actually broken, so I am tempted to start building and deploying some of this to a test site. I am slightly worried that statically generating everything will make the build process excessively slow, even though I have tried to do some caching now, but luckily I can configure all of that - perhaps statically generating the most recent 50 posts and dynamically generating the rest makes sense.

#100days 16 - More website migration work! Pretty happy with the separation of frontend and backend now, I think it should work well :)

Today I did a lot of work on the admin functionality and tidying up a lot of code and transferring old custom functionality like my pay page.

#100days 15 - Made a lot of progress porting my site to Next.js. It's been quite a pleasant experience so far. The static generation abilities are really powerful now and I managed to make a first - totally unoptimized - static export of my previously fully dynamic site, it might have taken 17 full minutes to run, but it did successfully generate thousands of static pages.

Lots more work to go on it but it's definitely a good start and I am very much looking forward to the upcoming Next.js features.

#100days 14 - decided to work a bit on my custom watch face for fun. So now the background rotates throughout the day and various items are clickable to open up specific apps

#100days 13 - Did some work on integrating my bathroom scale into my home automation.

It's sort of wildly over-engineered but I love it.

I have a raspberry pi near my bedroom with a script running that can read results from the scale via Bluetooth, it then sends the data over mqtt to my home assistant box at the other side of the apartment and that stores the information and runs an automation.

The automation gets the new data compares it to the last weight and then speaks it on the nearby Google home.

The result is I step on the scale, it shows my weight, then the Google home tells me the change since last time, my bmi and my fat.

I am 100% reporting my fat wrong, it's either - it is reporting "visceral fat" which is not the same as body fat percentage, so I need to change something somewhere. But all the data is there it's just a case of doing some simple calculations or changing what the speaker tells me.

Bonus video: https://grant.codes/media/2020/05/13/1589409504701.mp4

#100days 12 - Figured out the issue I was having yesterday with inserting replacing the editor element instead of inserting it as a child.

It was fairly involved meaning removing sibling elements and adding them again later on. But so far it appears to be working great for me.

This is pretty important in an editor that can handle alignment - which the PostrChild extension does. It means there is no extra effort needed to style the content when it is in the editor vs when it is live on the site.

Still lots of work to go, especially around the suggestion functionality but I feel there is a bit more progress again and I am using PostrChild more to write these updates