Super Bonjour
I chose to build this site in Svelte, in part for the faster load and build times. Portfolio sites can be very heavy in content, so I wanted a solution that could perform well with massive amounts of photo and video data. Also knowing that later updates to the site may mean even more content will be added.
I spent a considerable amount of time finding the best solutions for optimization. That’s when Cloudinary came in. I wanted to reduce the load time as much as possible. Amazon AWS could have also been an option. But Cloudinary felt easier to use, simpler — when it comes to ease of use, when products consider new devs with empathy, I’m always down.
While the design appears simple, the complexity in the code was real! Svelte does a great job to efficiently handle data reactivity and properties. Vertical parallax (on desktop) and carousel combo, the two way binding (thankyou SVELTE for doing this automatically!!), dynamic index on the way finding, and the layers of fixed modules, etc. Just a few of things that contributed to challenges at hand!
And of course the CSS, the styling. Combining different font treatments between the modals, the wayfinding and the copy slides, the varying layouts within each slide, and not to mention the differences for mobile. Working with the designers to understand their intentions was really key to guide my understanding of the design, how to make it responsive and the way I structured my code.
Understanding the content (creative work) and the people I built this site for (creatives) was crucial: in this case, it meant doing a lot of work to maintain the integrity of the framing and ratios of each image, regardless of weight, size, browser and device. This condition was foundational in the decision I had to make. For mobile, particularly, this meant an entire new approach: we built it on Javascript to maintain the ratios and allow for navigation on a rotated device.
Ansa Akyea
This is a porfolio site for a professional actor/theater built usng JS, CSS, HTML. Vite was used to serve code locally during development and bundle and assets for production. Using Vite for all the frontend tooling, with lightning fast HMR and optimized build was preferable to other build tools.
I spent a considerable amount of time finding the best solutions for optimization. That’s when Cloudinary came in. I wanted to reduce the load time as much as possible. Amazon AWS could have also been an option. But Cloudinary felt easier to use, simpler — when it comes to ease of use, when products consider new devs with empathy, I’m always down.
I spent a considerable amount of time finding the best solutions for optimization. That’s when Cloudinary came in. I wanted to reduce the load time as much as possible. Amazon AWS could have also been an option. But Cloudinary felt easier to use, simpler — when it comes to ease of use, when products consider new devs with empathy, I’m always down.
Vesper
This web app was done with Ruby on Rails. Final project for the Le Wagon 8 weeks intensive bootcamp. Ruby, rails, SCSS, Cloudinary, Heroku are some of the tools used. For this group project I focused on the backend, I'm usually more frontend. PostgresSQl, Active Records, Cloudinary, and heroku were used for the backend.
I spent a considerable amount of time finding the best solutions for optimization. That’s when Cloudinary came in. I wanted to reduce the load time as much as possible. Amazon AWS could have also been an option. But Cloudinary felt easier to use, simpler — when it comes to ease of use, when products consider new devs with empathy, I’m always down.
I spent a considerable amount of time finding the best solutions for optimization. That’s when Cloudinary came in. I wanted to reduce the load time as much as possible. Amazon AWS could have also been an option. But Cloudinary felt easier to use, simpler — when it comes to ease of use, when products consider new devs with empathy, I’m always down.