Can't Imagine Why

Can't Imagine Why (cantimaginewhy.com) is the website I made to showcase my art. The name has no particular meaning, other than I needed a name and it was available.

This blog is about my process of building it. I have some help on the design, but so far the coding is all me. Hopefully writing about it will at least help me get out of my own way and think more clearly, even if no one else ever reads it.

I got the idea from one of my classmates at General Assembly, Chuck Curtiss. He started a blog to document the process of building a coding project. It seemed like such a good idea, I decided to copy it. That was about 2 months ago; I'm finally getting around to doing it.

Here's an overview of my project. It's a site to display artwork, specifically mine. Additionally, it will allow users to purchase prints and other derived products, as well as original pieces.
At this point, it's not so much an app as a site. The difference is that my users are visitors, and they don't need to be able to create, update, or delete any items; only to retrieve them. Maybe in the future, I can create a full app that allows someone other than me to manage their own artwork, but that's not part of the MVP.

Because my least favorite part of building a site is the design part, I talked some UXDI graduates into doing that part for me. As of this writing, that process is still ongoing, so I've been working on the site's functionality with minimal thought to how things look. As long as I follow basic standards of separating style from code, I should be able to apply the semi-professional designs as soon as they are available.

Comments

Post a Comment

Popular posts from this blog

Basically done! (at least on full-screen. except for some issues.)

Image
The full-screen version of my site is essentially complete! Mostly. Except for the Map component, which I don't quite have yet; instead there's just a button that opens the location in Google Maps, in a new tab. Also, I had wanted to use URLs for all navigation, including within the Artwork page; but it turned out to involve a lot of changes, so I put that on pause for now. The mobile version is a different story. Prior to this week, opening the site on a screen less than about 600px would just break the site - totally useless navigation, overlapping elements, etc. I managed to fix that, mainly by just changing all my CSS unit values to vh/vw and %, instead of px or em. But there are still some serious aesthetic issues on mobile devices. Which I'm going to discuss in my next post. So, here is a screenshot from the site, basically as it was when my team and I presented it at GA, as a "post grad" project: And here it is now: Besides looking better, all
Read more

Getting back to it, again

Image
Got a little distracted - apparently there's something going around. OK, so, I put a lot of work into making the site mobile-friendly, which reminded me again why mobile-first is a good design strategy. But not the way I did it, so not really worth crying over now. I started this post a month ago, and then didn't publish it. So now I'm getting back to it again. My default work style is to obsess over one project until I hit an insurmountable challenge or run out of things to try, and then avoid it for a couple weeks. For whatever reason, writing this blog counts as its own project, distinct from actually developing the website. So my blog updates often happen only when the coding has reached a pause. Current Status : site is live and functional, though more could be done.   All the available controls do what they are supposed to do. However, there are some fairly obvious gaps in functionality, such as the ability to buy things directly from my site. That's on account
Read more

Mobile Issues

Image
So, a couple things don't work and/or look bad on small screens. Despite the fact that I finally stopped setting styles using pixels. Which is a remarkably bad practice, but still for some reason a tough habit for me to break. Anyway, here are some persistent bugs with the mobile version of my site: The menu , which now collapses to a toggle button below Bootstrap's medium screen size (which I believe is 768px). However, when you click the hamburger icon (aka the 3 horizontal bars that are the universal symbol for an expandable menu), the menu items are ugly, and also they push the rest of the content down the page. Should instead become a dropdown menu that floats above the page content. So, here's the homepage on my laptop screen: And here it is on mobile (Galaxy S8) - with menu expanded: The Lightbox feature . This used to handled by a complex function in App.js, which got passed as a property to every page so that any image could by magnified. Howeve
Read more