Back
Similar todos
Create a branch where I'm going to try getting the app looking nice with Vuetify because the #1 source of stuff taking a long time is that styling the app takes forever, and the projects I'm working on for my Upwork clients move way faster because I'm using Vuetify (at the expense of not looking as nice as a DAW or IDE desktop application). 
#rhymecraft
Removed Vuetify because 1) it was messing with my existing styling, 2) I think I may try to style everything myself, and 3) it's easy to add back later now that I have the commit. #rhymecraft
On my local version of the app, have the default route be to the Vuetify app rather than the existing app. #rhymecraft
Switch my API calls to be in a single backend.js file as I think that'll keep things organized as things get complicated and it's working nicely in the Vuetify app I'm building for an Upwork client of mine. #rhymecraft
Got the app working where the Vuetify interface can exist at a different endpoint than the existing UI as a way of hopefully avoiding needing to fix all the CSS problems right now. #rhymecraft
Tried having the the app use a Vuetify app bar and navigation bar and confirmed it caused some issues with the styling, but I should be able to fix those issues without too much trouble (hopefully), and it'll be worth it to have my app more-easily optimized for mobile. #rhymecraft
Got Vuetify working. #cleanexam
Created a custom navbar for my jobs view...switched to storing the resumes in the db instead of the filesystem so they don't get deleted every time I push to the dokku server and the container gets rebuilt...spent a while trying to figure out why my v-data-table wasn't working until I realized I needed to update to a later version of vuetify...
Loaded the app with Vuetify installed and everything looks the same, which wasn't the case the last time I tried installing Vuetify. So it may be easier to do the switch than I was expecting. #rhymecraft
Lots have changed in Rails / Webpack in the last year, so decided to ditch Webpack completely and go with Vite instead ⚡️ 
#tijdwerk
Move all the nonvuetify app components into a subfolder to not get them confused with the vuetify app components. #rhymecraft
Cloned my Flask/Vuetify template repo to start work on my "Let's Play" idea
Started work on a Go+Vuetify+Digital Ocean template, copied over the parts of my README for my Flask+Vuetify+Digital Ocean template that should also apply here. Feeling good about making forward progress towards making Go apps instead of staying stuck in tutorial hell.
Work on 
#buildstreak again, rip out ChakraUI and replace with Tailwind. It feels so much more sane to write HTML/template style instead of React's everything is a component in a component imported from a component styled with props. I don't want mental friction, I want to ship stuff. Should've just went with PHP 😛
Moved my API routes into a 'resources' folder to keep things a little more organized and since that's the pattern in the Flask-Vuetify template I like. #rhymecraft
👨💻 learning vue | i have to re-write some code from react to vue
refactor 
#colourhunt code and cleanup to new nuxt structure
Added Vuetify! #rhymecraft
Deploy big refactor of 
#wip codebase using Tailwind CSS and ViewComponent wip.co/posts/switched-to-tail…
