My first (of 3 or 4) article on the process of building #tootahead is out! In this entry, I focus on the inspiration and the tech stack I chose to build with.
This project lost steam, but I'm reviving it FULLY in public this time. Also opted to use @sveltejs and @tailwindcss since I really need something new to jog my brain. It ain't pretty yet, but it'll get there! #buildinpublic
Was a bit quiet since this last one, but got the following done:
✅ Home page now includes an accordion-style sidebar to match the modal ✅ Can now add custom categories ✅ Other misc UI improvements (scrolling, better responsiveness, etc)
Learned a neat trick with #MySQL yesterday, using a script like this lets you perform more of an `upsert` operation, creating a record if it exists, or updating an existing one if it doesn't!
Context: building a GitHub Projects/Issues Calendar tool
Day 4/14: I’m building (yet another) tweet scheduler!
➡️ 75% of the new thread UI is done. Lower options in the dialog are placeholders, also need to implement adding images. ✅ UI properly saves to the @planetscaledata DB using @Netlify functions
✅ Auth is done ✅ Was able to successfully send data to the DB from the front end 🎉
All the piping is just about done, now I get to focus on building out the product. I’ll open source this at some point, gotta clean some stuff out the repo tho #buildinpublictwitter.com/brianmmdev/sta…
Bittersweet that the last v2 subclass is being sunset next week. I put a decent amount of work into getting this component in @guardianforge to render dynamically based off the API data.
Gonna throw together a write up on how I did it as a farewell. 🥲 #buildinpublic
Bittersweet that the last v2 subclass is being sunset next week. I put a decent amount of work into getting this component in @guardianforge to render dynamically based off the API data.
Gonna throw together a write up on how I did it as a farewell. 🥲 #buildinpublic
Did some light work on my scheduler this morning. I wanted better logging and a more consistent structure so I wrote a custom struct to wrap my jobs in. #buildinpublic#golang#OpenSource
Tryin to get better at the #buildinpublic thing again, so here's my entry for today!
If you read my previous entry (RT'd) I found one glaring issue when I was working the process late last week: keeping tasks between projects & content items in sync
Finally taking the time to rebuild my website and bring it more in line with my other branding images, as well as being it over to @GatsbyJS & @Netlify
Also started using the public repo again (check the thread if you’re interested 👇) #buildinpublic