Decide to create a branch where I abandon almost all my existing styling and totally switch to Vuetify because I think the custom styling and complexity of having everything as one route is what's causing me to procrastinate. #rhymecraft

Added Vuetify! #rhymecraft

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

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

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

update vuetify and check/fix affected elements #abcgamers

Got Vuetify working. #cleanexam

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

Added another dropdown menu to the Vuetify version of the app from the older version of the app as another warm-up task. #rhymecraft

Added a link to the old (non-Vuetify) version of the app in the navbar so people visiting the site can still use the old version, and also just to get myself to start making changes to the site. #rhymecraft

Fixed/rewrote timeline diagram plugin to just use plain HTML and CSS, cos Vuetify conflicts with Carrd - timelinediagram.carrd.co/ #pluginsforcarrd

fix showing non-styled elements on web refresh (vuetify / webpack) #abcgamers

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

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...

Move all the nonvuetify app components into a subfolder to not get them confused with the vuetify app components. #rhymecraft

integrate Vuetify, Vuex, Makerwidget for TodoMoji

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 😛

Toyed with daisyUI, Tailwind, found a really awesome Nuxt 3 template (Nuxtwind Daisy) but still unsure. In the end, gravitated towards just plain CSS for now #listskit

Switched to styled-components

On my local version of the app, have the default route be to the Vuetify app rather than the existing app. #rhymecraft