Kevin Ludlow is a 45-year-old accomplished software developer, business manager, writer, musician, photographer, world traveler, and serial entrepreneur from Austin, Texas. He is also a former candidate for the Texas House of Representatives.
Please take a moment to view his complete resume for more information.
Note: the entirety of this website was architected and developed from the ground up exclusively by Kevin Ludlow.
This is actually called a Julio Verde and as far as I know was first made at Juiceland in Austin, TX. But this is my own version of it. It's delicious and it's called the Don Julio.
My mom has been making smoothies lately. I vowed to her that I would share my recipe for this one. I have fulfilled my vow.
I've probably had hundreds of people over the years request a mobile version of this site. I suspect the reason it's not already mobile-friendly is just one of those things that non-technical people can't fully understand. Given my actual website contains so much content and given that I'm the sole person who maintains it (and who has coded all of it), modifying the overall format is actually a pretty mammoth task.
There are generally two ways one can approach this problem:
1) The entire base website can be rebuilt into a responsive design fashion so that everything adjusts accordingly regardless of the interface accessing it (mobile, tablet, desktop, etc). This is a wonderful design option, but would require an enormous overhaul of the existing layouts. I'd have to go back through every single page and build the page entities to work in a responsive format. In short, this would be a rather significant amount of work, namely as it would require me ensuring that the desktop maintained its design elements too. This is further exacerbated by the reality that I'm a developer and not actually a designer (despite the fact that I do my own design too).
2) The second option is to build a brand new mobile version of the site that runs alongside of the desktop version. The downside is that I'll have two separate sites to maintain, but the upside being that changing one of them doesn't requiring the maintenance of two of them.
For various technical reasons, I've opted to go with option number 2. The bulk of my website is based upon complicated backend code that handles all of the requests from the database. The front-end is generally pretty straightforward and indeed works well on a desktop. It just doesn't work well on a mobile device. Incidentally, the reason it works well on a mobile phone is because the entirety of the site is built exactly to HTML 5 specifications. This is what allows the site to properly "shrink down" when viewed on a mobile device. The downside is that it becomes nearly impossible to read and navigate.
So essentially what will happen is that a new website will exist for mobile users. The site will incorporate the standard mobile-based navigation options, typically known as the "hamburger" dropdown. The backend code will remain in place and will be used to drive the new front-end design. Some backend changes will need to be added, but the majority of it will already be in place. On the other hand, the secondary design elements will need to all be created.
I've been working on this on and off for some time now . It's finally gotten close enough to being finished that I thought it was time to mention it.
As a quick side note, I've spent the entirety of 2022 completing a dozen pretty huge goals that I'd set out for myself. I only started working on them in March and yet, I should be on track to finish every one of them. Some of these goals include significantly elevating my work life, rebuilding part of my house, finishing my camper van, recording an album, rolling out several new software platforms, rolling out a new version of kevinludlow.com, and indeed rolling out the mobile version of kevinludlow.com.
I'm extremely confident at this point that the new site will be available soon enough!
