Since I started working at this auto dealer vendor I’ve been thinking a lot about creating a CMS for independent car dealer websites. Just getting started is kind of a big deal because the platform to work on needs to be identified.
I figured with my new found love of Bootstrap it was time to give these sites some new life. Just playing around with some very basic coding I redesigned an information page about Scion cars.
Creating a custom coupon page for the VinSolutions dealer websites platform was easy using the new w3schools w3.css. This DIY basic guide will walk you through the steps needed to create nice looking coupons that work on desktop and mobile.
After several months of attempting to make coupon pages look good on our dealership VinSolutions websites there now seems to be an easy solution! thanks to w3schools new css code our coupon pages look great on desktop and mobile.
A new wrinkle arose trying to use bootstrap on the VinSolutions auto dealership website platform. The resulting workaround solution was not optimal but has other benefits.
Today I had either an ah ha or a duh moment. Why not use Bootstrap? Then if/when there is a change in the future everything will just copy and paste over nicely. And (hopefully) when they finally release their 360 platform, the code should be responsive and just work.
In my previous post about custom forms on VinSolutions websites I mentioned requesting a global css change that should fix the forms created by VinSolutions. Problem is – VinSolutions offers several forms templates. Fortunately each of these 6 templates are css driven. With the previous update in place the forms with layout 3 & 4 are not lining up nicely. Now the form shows between “Secondary Content” and “Footer” content. There is an easy fix for this. Because a browser reads a pages markup/code from top to bottom we need to put some css information before the form section of the page code. In my…
Just over a month ago the company I work for switched a few of our websites to VinSolutions. As with any CMS there is a learning curve. I downloaded their CSS files and attempted to figure out if they were using any kind of standard. There were a bunch of css files and they all appeared to be randomly coded with very little commenting. I figured a good place to start was a custom page they had (kind of) copied from our old website. It was a form page with custom css so I figured this would give me some…
Changing from one automotive website CMS provider to another proves to be a serious pain in the ass. But it shouldn’t have to be this way.
After many hours and months of reading through forums and wiki’s the answer for writing Spamassassin rules now seems way to obvious. I guess engineers can’t write stuff in plain english.