One question I do have for those who love UI/UX.
If the user is logging in, and they click on the "Sign in" button. Should I change the text to "Signing you in" with a spinning logo to represent something happening, or should I stick with a generic spinning logo?
I've finally created my first npm package - whelk-ui. A vuejs shell component library that will be used for both NearBeach and another project in the near future.
I wanted to create something that I can use in multiple places, but at the same time I can shape easily into the brand of that product
Ok. This is not my fault this time. Please don't blame me
I am currently working on the new UI/UX for NearBeach. Currently looking for any constructive feedback :)
robotichead.azurewebsites.net
So far I have only implemented the Navbar and header.
Ok, I am looking for some feedback on the next iteration of design for NearBeach.
Ignore the pink space
Quick thirst trap
Starting doing a draft/mock up design for NearBeach. What are you honest opinions? What can be improved? What can add some umph?
Also this experiment gave me the ability to finally play around with @vitest.dev
. I can quickly experiment with these test components, and setup a standard before starting the refactoring of the UI/UX for NearBeach
I am seeing if I can replace any components that I import from external libraries. There are about 5 to replace.
Just playing around with creating my own little components. My first test example has gone really well.
Airlines could implement forced cardio with late gate transfers 🤣
Flight 209 now arriving at gate 8. Gate 9. Gate 10. Gate 11. Gate 12. Gate 13. Gate 14... 15. 16. 17 18 19 20
Sadly I could not remember the Airplane! Quote exactly
Socks is too, almost ready to shed as the weather slowly warms up
Out of curiosity, how would you improve something like this?
OOoohhhhhhh..... yeah it feels weird, and that is me saying that. Like there is an icon that is missing
Maybe documentation. As I am terrible at documentation
Here are the items that are required to be completed before we wrap up the 0.31 branch. Getting there. I think the biggest hurdle is the GDPR
2 of my users helped shape NearBeach's kanban board with small ideas/features. These ideas/features made using the kanban board a lot easier.
Honestly I don't know. Would be interesting to look at especially broke down into Country/Month.
Sadly any analytics I have on my social media accounts are always low 🫣
Some of the hardware in my shoulder. Minus the skater
Tonight, I want to fix a lot more bugs in NearBeach. Come alone and hang out as we fix things up
twitch.tv/robotichead
#buildinpublic #python #vuejs
Lets fix some more issues within NearBeach. Got to fix all those bugs
twitch.tv/robotichead
#buildinpublic #vuejs #python #fixingbugs
Lots to do - lots to fix. Come join me on stream :D We'll try and fix all the things
twitch.tv/robotichead
#buildinpublic #python #vuejs
I am totally not prepared for tonight's stream. :O :O :O
twitch.tv/robotichead
#Buildinpublic #python #vuejs
Ok, I am going to try and fix a few more bugs today :) Lets see how I go.
twitch.tv/rbotichead
#buildinpublic #python #vue #bugs
Alright - lets GOOO! Lets get some docker testing done, and fix some bugs.
twitch.tv/robotichead
#buildinpublic #docker #python #vuejs
I've got a few things to do tonight. Some bug fixes, some quick doc fix ups etc. So why not come along and hang out for a big whilst I program.
twitch.tv/robotichead
#buildinpublic #python #vuejs #programming
I've got to start researching how to make better UI/UX. Does anyone have any good resources I should look into?
Meow...
Ok - I am going to try streaming tonight :) Lets play around with seeding NearBeach full of data. I want to create a fixture that I can test the GDPR wizard on
twitch.tv/robotichead
#buildinpublic #testinpublic #python #unittesting
We've just published our retrospective for July 2025 on Patreon - www.patreon.com/posts/july-2...
