View the Project:
Compare it to the Original
Deciding what to build to showoff my front-end skills
When I first decided to build something
for the Digital Ocean Hackathon to show off my front-end webdev skills, I asked myself "What would be useful for a real business?"
The answer I came to is recreating the website of a real business, a business whose website is so important to them that it serves as a foundation of how they do business and serve their customers.
The first criteria I had was obvious to me: the business whose website I chose to recreate had to be huge, or at least hugely valuable.
The second criteria was less obvious: the business' website had to not depend on the use of outside assets and graphics to make it look nice. Pretty assets don't show off my front-end skills and don't show off how I can best help businesses.
So I wanted to recreate an existing successful business' website that uses a variety of CSS skills: flexbox, grid, and a variety of styles for images, text, and a lot of data that needed to be managed in a robust way.
After all, part of the reason I decided to recreate a serious internet business' homepage, is that I wanted to improve my front-end webdev process and this offered me the perfect challenge: totally doable, yet more complicated than any page I've created before.
I looked at a few sites before I chose one:
First I looked at Nike because I like their branding, but after looking at their website, I realized most of my work recreating it would just be copying their media assets.
Sure, I could recreate their navigation menus using flexbox and product displays using grid, but most of my work wouldn't show through.
Second, I looked at Stripe. Stripe's website is beautiful, but boy is it complicated and, secondly, it has the same problem as Nike: recreating Stripe's website depends on using a lot of outside assets, except it's worse! Stripe's website uses assets that are harder to access and implement.
Still, Stripe's website uses some pretty cool layout designs I could recreate using grid. Maybe this is something I'll revisit later.
Lastly, I looked at Notion. Notion's website, like their application, is beautiful, friendly, and accessible. It uses a bunch of assets, but, unlike Stripe and Nike's websites, doesn't rely on them. It uses modern CSS skills like flexbox and grid and a lot of text data that's managed best dynamically using components.
Notion's homepage was the clear and obvious winner.
One thing I decided early on was that I wasn't going to look at the original webpage's code. If someone wants to hire me to create a website for them, I don't have any starting code to work with so I'm not going to use that here either. They'll simply hand me off some wireframes from Figma or Sketch with the assets I need and/or a validated product spec.
I recreated all the page's designs and layout by sight.
No inspecting code, no copying code. All translating what I see into what write.
For me, there's only one good solution for this "what you see is what you code" sort of webdev framework and that's Tailwind CSS.
Tailwind is great because it removes the layer of abstraction and lock-in that makes global CSS so unmanageable.
Next, there's data. All the data serious internet business websites use is managed dynamically using components.
You alter design and data using two separate processes which keep both safe from accidental changes to each other.
Components let you update how data's displayed across your website without updating individual pages one by one.
Avoiding code duplication helps you avoid making errors that make your website harder to manage, less friendly to use, and less focused on satisfying your users.
I manage the webpage's data using Vue JS. Its fast modern framework makes managing data easy and reliable.
But there's one problem with Vue JS and that's SEO.
Vue JS, like React and Angular, render a webpage's content dynamically, so they're not good for SEO.
To solve this problem, my next steps are rebuilding this site using NUXT JS, which builds static HTML pages to get all the benefits of dynamic rendering and offers component organization from Vue JS with all the SEO benefits of static HTML.
CSS Properties I Learned
Makes images non-draggable
CSS Properties I knew, but hadn't used before
Useful for conditionally reversing the orientation of your footer elements on mobile, such as when you want to show a copyright notice on the left in your footer on desktop, but below everything else on mobile.