Back
Similar todos
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
Switched my user and video-related API routes to use Flask_RESTX because it helps keep the API organized. #rhymecraft
Switched my Song routes to use flask_restx, and I now have all my routes using flask_restx. #rhymecraft
Work on API routes for templates synchronization 
#jomo
On my local version of the app, have the default route be to the Vuetify app rather than the existing app. #rhymecraft
Refactor VueJS code to better handle API calls
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.
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
Move two song-related routes from api/__init__.py to api/songs.py (actually did this yesterday) #rhymecraft
move all api calls to vuex actions 
#gitwriter
Migrate api docs pages to use vuejs 
#apercite
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
Spent some more time switching the API to using flask_restx. #rhymecraft
new api route config for 
#audiogest
Made progress on my Flask/Vuetify template that I want to try to sell.
