farispalayi / order-summary-component

An order summary component page compatible with IE10 and IE11 with blur-up loading

Frontend Mentor - Order summary card solution

This is a solution to the Order summary card challenge on Frontend Mentor. Frontend Mentor challenges help you improve your coding skills by building realistic projects.

Table of contents

• Frontend Mentor - Order summary card solution
  • Table of contents
  • Overview
    • The challenge 🎯
    • Screenshot 📸
    • Features ✨
    • Supported Browsers 🌐
    • Project File Structure 📂
    • Links 🔗
  • My process
    • Built with 🛠
      • Deployed on:
    • Site Architecture 🏗
    • What I learned 📖
    • How it's done 🤔
      • Blur-up image loading 🖼️
    • Continued development 🌊
    • Useful resources 🔗
  • Project setup 💻
    • Clone the repository locally
    • Move to the desired directory
    • Install dependencies
    • frontend/ directory local setup
    • server/ directory local setup
  • Author 🤓

Overview

The challenge 🎯

• Users should be able to see hover states for interactive elements
• Make the site compatible with IE10 and IE11.
• Do not use any pollyfills or tools like typescript or babel to achieve that.

Screenshot 📸

• On desktop (1440px width & 900px height)

• On mobile (375px width & 709px height)

Features ✨

• Stripe payment
• Blur-up image loading
• Button ripple effect
• IE10, IE11 compatible
• Fluidly responsive
• Conventional loading spinner on button
• Error snackbar on request failure
• Change subscription plan dropdown
• disable buttons until javascript is loaded
• Fully keyboard accessible

Supported Browsers 🌐

• Chrome
• Firefox
• Edge
• Brave
• Opera
• IE11
• IE10

If you are a mac user, I'd appreciate it if you could check it on Safari and let me know if it works on it or not. feel free to make a pull request or issue.

Project File Structure 📂

.
├── .vscode/
│   ├── extensions.json
│   ├── settings.json
├── frontend/
│   ├── design/
│   └── images/
│   └── sass/
│   └── scripts/
│   └── index.html
│   └── .gitignore
│   └── package.json
│   └── snowpack.config.js
├── server/
│   ├── server.ts
│   └── .env
│   └── Procfile
│   └── .gitignore
│   └── package.json
│   └── tsconfig.json
├── .prettierrc.json
└── README.md

Links 🔗

• Solution URL
• Live Site URL

My process

Built with 🛠

• Semantic HTML5 markup
• CSS custom properties
• Flexbox
• Mobile-first workflow
• Sass
• Snowpack
• ExpressJs
• Typescript
• Ts-node
• Stripe

Deployed on:

• Netlify
• Heroku

Site Architecture 🏗

• I split my files into two folders, frontend and backend. Mainly because I wanted to deploy the frontend on Netlify and backend on Heroku.

• I used this buildpack for automated heroku deployment from the subfolder "/server". This buildpack makes it possible to set a subdirectory as the project root by specifying it in an environment variable (config vars in Heroku).

• I used a simple format/method when writing commit messages. By prefixing certain keywords like chore, build, and feat to commit messages, I made sure that the commit messages are more organized and readable. (I got this method from the VueJs github repository)

  • chore: if it is a small task/change
  • feat: when added new feature
  • build: build, deployment related changes
  • refactor: when rewriting or making changes to existing code(refactoring)

• Elements that will be used in javascript will have a js- prefixed class.

• I used snowpack as the build tool for the frontend/ directory.

• Used ts-node to compile and run typescript code for development in the server/ directory.

What I learned 📖

I learned a lot of stuff while doing this project.

• Firstly, I learned how to use Stripe to make basic payments. Although, I have a long way to go before I understand all of its APIs and how it actually works.

• Since I wrote javascript code that needed to be compatible with IE, I got an overview of which js features works with IE and which does not. Some things that IE does not support:

  • In CSS

    • CSS Custom Properties (CSS Variables)
    • Full support of Flexbox
    • Full support of CSS Grid
    • min(), max() and clamp()
    • CSS logical properties. Eg: inset
    • fit-content, min-content, max-content

  • In Javascript

    • Arrow functions
    • Promises
    • JS Modules
    • Fetch API (since it's a promise)
    • Async await
    • Destructuring
    • Spread, rest syntax
    • Template literals
    • Default function parameter
    • let and const (IE10 and below)
    • addEventListener() (IE8 and below)
    • Array methods like forEach(), reduce(), map() (IE8 and below)
    • event.key (use event.keyCode instead)

• Got to know a built-in Sass function math.is-unitless(). Which checks if the passed argument has a unit or not, and returns a boolean based on that. I used it in the toRem() function to avoid accidentally passing values that has units.

• Learned how to use a base64 encoded image in an SVG.

<!-- unrelated attributes and stuff are omitted for brevity -->
<svg>
  <image xlink:href="data:image/png;base64,iVBORw0KG..." /> <!-- 👈 base64 image goes here -->
</svg>

• I didn't really know that there was a difference between .addEventListener() and .onclick, which is, while .addEventListener() can be used as many times as we want, the .onclick can only be used once. Which makes sense when thinking about it, because when using .onclick, we are just directly changing a method. So:

// while here the func and func2 is called
btn.addEventListener("click", func);
btn.addEventListener("click", func2);

// here, only the func2 is called
btn.onclick = func;
btn.onclick = func2;

• Also, learned how to make an XMLHttpRequest(xhr). This was what used to make requests in js before the Fetch API.

• Usually I set my root font-size value in px, and use rem for font-size everywhere else. Because, that way I can change the font sizes relatively throughout the site pretty easily by only changing the root font-size. But, turned out, It will affect accessibility badly. Because, when a user sets a larger/smaller font on their browser, it won't take effect since the font size is set using px, it will overwrite it. So, I used rem unit on the root instead. So that it will always be relative to the user's preferred font size. Big thanks to @grace-snow and @AlexKMarshall for helping me out on it.

• Learned how to get a recommended vscode extension notification using the .vscode/extensions.json file. By adding an extension's identifier as the value of recommendations in the extensions.json file in the .vscode directory. For example: vscode .env syntax highlighter extension's identifier is "irongeek.vscode-env". To show that as a recommended extension, add

  // .vscode/extensions.json
  {
    "recommendations": ["irongeek.vscode-env"]
  }

  

  Identifier can be found in the extension's page.

  

  Get the identifier of a vscode extension

• I learned a few new git commands as well:

  • git add -p : It can be used to stage only the desired changes to git. i.e. it'll make it possible to stage/add chunks/hunks of changes rather than all the changes.
  • git reflog - Kinda like git log, but gives more info. It can be used to undo even a hard reset.
  • git bisect - To find the commit that is responsible for a bug. Finding this is possible to do in git has helped me a lot in this project. Especially when something unexpectedly broke in IE.
  • git merge --abort - To abort a merge and go back. Useful when there are a lot of merge conflicts and you simply wanna go back to the previous state.
  • git reset --merge - to reset a merge. Like resetting(going back to) a commit, but for merges.

How it's done 🤔

High level overview of how some features are implemented.

Blur-up image loading 🖼️

Popular apps like whatsapp, facebook, and sites like medium uses the blur-up technique to load images on their site/app. Where, a blurred version of the image is shown until the image has loaded.

I followed this article from CSS-Tricks to create the effect. Though, I have done a few things slightly differently.

steps:

1. Take the image and create a smaller version of that. It should be around 40 pixels height and width (but keep the aspect-ratio).
2. Convert it to base64. (I used this site for that).
3. Put that into a Gausean Blur applied svg's image tag.

<svg
  xmlns="http://www.w3.org/2000/svg"
  xmlns:xlink="http://www.w3.org/1999/xlink"
  width="1500"
  height="823"
  viewBox="0 0 1500 823"
>
  <filter
    id="blur"
    filterUnits="userSpaceOnUse"
    color-interpolation-filters="sRGB"
  >
    <feGaussianBlur stdDeviation="20 20" edgeMode="duplicate" />
    <feComponentTransfer>
      <feFuncA type="discrete" tableValues="1 1" />
    </feComponentTransfer>
  </filter>
  <image
    filter="url(#blur)"
    xlink:href="data:image/png;base64,iVBORw0KG..." <!-- add the base64 image here -->
    x="0"
    y="0"
    height="100%"
    width="100%"
  />
</svg>

1. Now, convert that svg to base64.
2. show that as the image until the actual image is loaded.
3. Show the actual image when it's loaded using javascript.

Blur up loading

Continued development 🌊

This project will be my last project where I focus on making the site cross-compatible with the Internet Explorer Browser. Coding for IE is a nightmare and fortunately (and finally), Microsoft has officially declared its retirement. IE is no longer available in the newest Windows 11 as well.

Being that said, my next focus will be on learning web architectures and best practices; especially in Js and CSS - or frontend code. Because, I still have no idea how to structure the code and how to architect its parts and how to effectively communicate from one part to another. Currently, I make those decisions solely based on my preferences and gut feelings.

So, I'm currently looking for resources to learn that. If you happen to know any good ones, I'd be grateful if you can point me to the right direction.

Also, I'll be learning NuxtJS little by little.

Useful resources 🔗

• The “Blur Up” Technique for Loading Background Images - CSS Tricks
• How to Recreate the Ripple Effect of Material Design Buttons
• Disabled Buttons in User Interface
• Is it ok to ‘grey out’ disabled buttons?
• caniuse - Useful tool for quickly visualizing which frontend technologies are compatible with which browsers.
• Automated heroku deploy from subfolder - Stack Overflow

Project setup 💻

Clone the repository locally

  git clone https://github.com/FarisPalayi/Order-summary-component.git

Move to the desired directory

  cd frontend/

or

  cd server/

Install dependencies

  npm install

frontend/ directory local setup

• Compiles and hot-reloads for development

    npm run dev
  

• Compiles and minifies for production

    npm run build
  

server/ directory local setup

• Run the server locally and auto server restart on save

    npm run start:live
  

• Compiles the server code for production

    npm run build
  

Author 🤓

• Frontend Mentor - @farispalayi
• Twitter - @farispalayi
• LinkedIn - @farispalayi

PS: I'm aware of the fact that there are a bunch of grammar mistakes in this document. I'm learning English as well, so I guess it's normal. Though, I do hope that things I wrote here are all understandable. If you wanna point out to me any mistakes in this document (technical, grammar, anything) please feel free to do so.